Astro Hosting — static or SSR, fixed price
Content sites are exactly what Astro is for — and exactly what shouldn't carry a metered bill. Your Astro site deploys by git push into its own UK container: static output served directly, or SSR via the Node adapter. From £9/mo, fixed.
Content sites deserve boring, predictable bills
An Astro site is mostly HTML and images — the cheapest thing on the internet to serve. It makes no sense for that to sit on metered bandwidth. The comparison below is about pricing models, not who has the nicer dashboard.
- Bandwidth quota — a popular post can push you into overages
- Build minutes metered — busy content teams hit the cap
- Per-seat fees on team plans
- Serverless functions billed per invocation
Model as of July 2026 — e.g. Vercel Pro at $20/user/mo + usage.
- Fixed £ price — traffic spikes never touch your bill
- Unmetered builds — push as often as your team writes
- Team roles included, no per-user pricing
- SSR runs in your container, not in metered functions
More detail: Netlify alternative · Vercel alternative · G7Cloud vs Vercel
Everything an Astro project needs
The same platform that runs our app hosting — one workflow whether your site is static, SSR or hybrid.
Static & SSR
Static output is served straight from your container; add @astrojs/node and SSR routes run in the same long-running process. No cold starts.
Git push to deploy
GitHub, GitLab or Bitbucket. Every push builds with the log streamed live; roll back by redeploying any commit.
PR previews (Pro+)
Review content and design changes on a real URL per pull request. Idle previews sleep, waking on request.
Pair with a headless CMS
Host Strapi, Payload, Directus or Ghost on the same subscription and point your Astro content loaders at it.
Databases when you need them
MariaDB per site as standard; managed PostgreSQL 15 and Redis 7 add-ons on Business and above.
Terminal, cron & env vars
In-browser shell into your container, scheduled tasks, and per-site environment variables injected at deploy.
Building with React instead? See Next.js hosting — or plain Node.js hosting for APIs and servers.
Plans that host Astro
One subscription covers your Astro site plus email, DNS, daily backups and the AI Website Builder. 30-day money-back guarantee on every paid plan.
Starter
One real site on your own domain — with email, DNS and backups.
- 1 hosted site
- Git deploys & free TLS
- Daily backups, restore-tested nightly
Business
Up to 3 sites plus full-stack AI apps — shop, bookings, CMS.
- 3 hosted sites
- Git deploys & free TLS
- Daily backups, restore-tested nightly
Annual billing saves 20%. Full comparison on the pricing page.
Astro hosting FAQ
Do you support Astro SSR or only static output?
Both. Static Astro builds are served directly from your container; for SSR, use the @astrojs/node adapter and your app runs as a long-running Node process — Node 18, 20 or 22, your choice. Hybrid rendering works too.
How do deploys work?
Git push to deploy. Connect GitHub, GitLab or Bitbucket, and every push to your chosen branch builds your Astro site with the log streamed live to the dashboard. Roll back by redeploying any previous commit.
Why not just use Netlify or Vercel’s free tier?
For a hobby site, honestly, their free tiers are fine. The difference appears when a site matters: usage-billed platforms meter bandwidth and functions and charge per seat, so growth and traffic spikes change your bill. As of July 2026, Vercel Pro is $20/user/mo plus usage. G7Cloud is a fixed £ price for a dedicated UK container — and the same subscription also covers email, DNS, backups and more sites.
Can my Astro site use a database or CMS?
Yes. Every site includes its own MariaDB database, Business plans and above can add managed PostgreSQL 15 and Redis 7, and we also host self-hosted CMSs — Strapi, Payload, Directus and Ghost — so your content API can live next to your Astro front end.
What about content collections and image optimisation?
They are build-time features of Astro itself, so they work unchanged — the build runs in your container with your chosen Node version, and nothing is metered per image or per build minute.