You can deploy an Astro site almost anywhere. By default Astro builds plain static files, which any static host can serve. If you need pages rendered per request, you add an adapter and choose a host that runs server code. The right choice depends on whether your pages change per visitor, not on which host is fashionable.
Start with the rendering question
Astro’s own documentation says it prerenders everything by default: pages, routes and endpoints are built as static pages at build time unless you change that. To render a page on demand you install an adapter, and you can opt a single page out of prerendering with export const prerender = false.
That gives you two practical paths:
- Fully static. Every page is HTML, CSS and assets in a folder. Nothing runs on a server when someone visits.
- Static plus on-demand. Most pages stay static, a few (a members area, a search endpoint, a form handler) render when requested.
Astro’s documentation recommends starting with the default static mode. Setting the whole site to server output does not add functionality, it only changes the default.
The main deployment targets
The Astro deployment guide tags each host as static, on-demand or both. Based on that page, at the time of writing (November 2026):
| Target type | Examples listed by Astro | Good fit when |
|---|---|---|
| Static-only hosts | GitHub Pages, GitLab Pages, Surge, Microsoft Azure | A brochure or content site with no per-request logic |
| Hosts supporting both | Netlify, Vercel, Cloudflare, AWS | Mostly static, with a few dynamic routes |
| Node server | Any machine running the Node adapter | You already operate servers or need full control |
Check the guide for the current list, because hosts change what they support.
What the build pipeline needs
Whatever the target, the pipeline is short. Per the deployment guide, git-connected hosts such as Netlify and Vercel watch your repository, build on each push and publish. The build command is astro build (or npm run build) and the publish directory is dist, unless you change outDir.
A sensible checklist before the first launch:
- Confirm the build runs from a clean checkout, not just on one laptop.
- Pin the Node version so local and host builds match.
- Store secrets as host environment variables, never in the repository.
- If you use on-demand pages, install the right adapter with
astro add, for examplenpx astro add netlify. - Preview the built output, not just the dev server, before pointing a domain at it.
- Set up redirects from old URLs if this is a rebuild (see how to redesign a website without losing SEO).
Choosing between them
Ask four questions in order.
Does any page need data that changes per visitor? If not, static hosting is the simplest option to operate. Fewer moving parts also means fewer things to patch.
Do you need only a little dynamic behaviour? Astro’s server islands, using the server:defer directive, let one component render separately while the rest of the page stays static and cacheable, according to the islands documentation. That can avoid moving the whole site to server rendering.
Who will maintain the hosting? A git-connected static host removes server maintenance. A Node server gives control but makes you responsible for uptime and updates.
How will you measure performance? Static output helps, but it does not guarantee good field results. See the Core Web Vitals guide for businesses.
Honest trade-offs
Static hosting cannot run logic per request, so forms, search and logins need either an on-demand route or a third-party service. Server rendering adds latency and a runtime to monitor. Each host also has its own adapter behaviour and limits, so test the exact feature you depend on rather than assuming parity. If you are weighing Astro against other platforms, the Astro vs WordPress comparison and Astro vs Next.js cover the platform decision itself.
Where Radiance Impact fits
Radiance Impact’s Technology division builds business websites and landing pages, and offers maintenance and care. If you want help choosing a deployment target for a new site or a rebuild, see /technology or get in touch.
Sources
- Deploy your Astro Site, Astro Docs
- On-demand rendering, Astro Docs
- Islands architecture, Astro Docs
