When a developer tells you an Astro site “deploys to Vercel,” most business owners nod and move on. That’s worth not doing. Where your site lives determines what you pay, who you call when it’s down, and whether you can switch development teams without a migration project. Here’s what each deployment option means in plain terms.
How Astro Deployment Works — the Basic Model
Astro builds your site into static HTML, CSS, and JavaScript files. That build process runs on a server, takes 30 seconds to 5 minutes depending on site size, and produces a folder of files ready to be served to visitors.
Those files can go almost anywhere. Unlike WordPress, which requires a PHP server and a database running continuously, an Astro static build is just files. Your hosting options range from free CDN platforms to traditional web servers to object storage. The key difference between options is who manages the infrastructure, how quickly the files reach visitors around the world, and what you pay when traffic spikes.
There’s a second deployment mode — server-side rendering (SSR) — where Astro generates pages dynamically on each request instead of pre-building everything. This is relevant for specific use cases: personalized pages, authenticated content, frequently-changing data. Most marketing sites use the static mode. SSR requires a Node.js runtime or serverless functions, which changes the hosting requirements significantly.
Vercel — The Default Choice and Why
Vercel is where most Astro sites end up, and the reason is developer experience. Vercel integrates directly with GitHub: push a commit, the site rebuilds and deploys in 60–90 seconds. The developer experience is close to frictionless.
For a business owner, here’s what Vercel means practically:
Pricing: Free for hobby/small sites (100GB bandwidth, 100 serverless function invocations per day). Pro tier is $20/month per team member and covers most small business sites. Enterprise pricing is custom and significant.
Performance: Vercel’s CDN has 70+ global edge nodes. Your HTML files are cached close to your visitors. A visitor in Tokyo gets the file from a Tokyo node, not from a US server. This contributes to fast Time to First Byte — often under 50ms.
What happens when it breaks: Vercel has 99.99% uptime SLA on paid plans. When something does break, the incident is usually on Vercel’s infrastructure side (their CDN, their build system), not something your developer can fix. Vercel’s status page is transparent. Downtime is rare and short — historically under 2 hours per year across their major incidents.
Rollback: One click in the Vercel dashboard to revert to any previous deployment. If a code change breaks the site, recovery is fast. This is a real operational advantage.
Lock-in risk: If you leave Vercel, you need to re-setup deployment pipelines on a different platform. Astro’s output files are portable — they’ll run anywhere — but the deployment configuration (environment variables, redirects, serverless functions) is platform-specific. A migration takes a few hours, not days.
Vercel is the right default for most small-to-medium Astro sites. The free tier handles meaningful traffic; the Pro tier is affordable. The developer ecosystem is mature.
Netlify — The Competitive Alternative
Netlify was first to market with this deployment model and is still a serious option. The feature set is nearly identical to Vercel: GitHub integration, automatic builds, global CDN, one-click rollbacks.
Pricing: Free tier includes 100GB bandwidth and 300 build minutes per month. Pro is $19/month per team member. Enterprise is custom.
What Netlify does differently: Netlify’s form handling is native (no integration with a third-party service required for basic contact forms). Netlify Identity provides basic authentication without extra services. These built-in features can save integration setup time on simple projects.
Performance: Netlify’s CDN is comparable to Vercel’s — similar global coverage, similar Time to First Byte numbers. The performance difference between the two platforms on a static Astro site is under 10ms in most benchmarks. It’s not the deciding factor.
When to choose Netlify: If your site needs native form handling for a contact page, and you don’t want to set up a third-party form service, Netlify’s built-in forms save setup time. If your developer has more Netlify experience than Vercel experience, default to their expertise.
The honest comparison: Vercel and Netlify are near-equivalent for static Astro sites. Developer preference and specific feature needs (forms, auth) determine the choice, not performance.
Cloudflare Pages — The Performance and Cost Argument
Cloudflare Pages is the third major platform and makes a compelling case on two dimensions: cost and global speed.
Pricing: Free tier with unlimited bandwidth and 500 builds per month. Pro tier is $20/month for 5,000 builds per month. The unlimited bandwidth free tier is a genuine differentiator — Vercel and Netlify both cap free bandwidth at 100GB, which a moderately trafficked blog can hit.
Performance: Cloudflare operates 300+ edge nodes globally — significantly more than Vercel or Netlify. For a global audience, Cloudflare Pages consistently achieves the lowest Time to First Byte in third-party benchmarks. The difference is more meaningful for international traffic than for US-only sites.
What Cloudflare does differently: Cloudflare is infrastructure-first. Their DNS, DDoS protection, security features, and CDN are all part of the same network. If you already use Cloudflare for DNS (which is common), consolidating your site hosting there simplifies your infrastructure stack.
The tradeoff: Cloudflare Pages is slightly less developer-friendly than Vercel. The build UI is more spartan. Some advanced Astro features (SSR with Cloudflare Workers) require more configuration. For straightforward static builds, this doesn’t matter.
When to choose Cloudflare Pages: High-traffic sites where bandwidth costs could exceed free-tier limits on other platforms. International audiences where edge node density matters. Sites already using Cloudflare for DNS and security who want fewer vendors.
Traditional Web Hosting — When It Still Makes Sense
A static Astro site is just files. You can host it on any web server that serves files — including traditional cPanel hosting, a VPS, or even Amazon S3 with CloudFront.
Traditional cPanel hosting (SiteGround, Kinsta, WP Engine, Hostinger) wasn’t designed for this pattern, but it works. You upload the Astro build output to the public_html directory and the server serves the files. No PHP runtime, no database, no WordPress overhead.
Cost: Shared hosting starts at $3–$15/month. VPS starts at $10–$50/month. Cheaper than Vercel Pro but without automatic deployments or a global CDN.
What you give up: No automatic rebuild-on-push. To update the site, someone manually uploads new files or sets up a deployment script. No built-in rollbacks. Performance depends on your server’s location — one server in Dallas doesn’t serve Paris visitors as fast as a 300-node CDN.
When this makes sense: If you have existing server infrastructure and want to minimize vendors. If you’re hosting multiple properties on one server and the marginal cost of adding an Astro site is near zero. If your developer prefers the traditional model and your audience is geographically concentrated near the server location.
For most new Astro projects, the CDN platforms outperform traditional hosting on both developer experience and end-user speed. Traditional hosting is a valid fallback, not a first choice.
Self-Managed VPS — Full Control, Full Responsibility
Some teams run Astro on a VPS (Digital Ocean, Linode, AWS EC2, Hetzner) with Nginx or Caddy serving the static files. This is the highest-control, highest-maintenance option.
Cost: $5–$50/month for the VPS. No bandwidth caps at typical scales.
What you control: Everything. Your server, your configuration, your deployment pipeline, your SSL certificates, your monitoring.
What you’re responsible for: Everything. Security patches. Server uptime. SSL certificate renewals. Deployment automation. If the server goes down at 2am, your developer is the one who fixes it.
This option makes sense for large organizations with in-house DevOps, or developers who prefer infrastructure control for other reasons. For a small business website, the operational overhead is not worth the control.
SSR Deployments — A Different Model Entirely
If your Astro site uses server-side rendering — meaning some pages generate dynamically on each request rather than at build time — your deployment options narrow.
SSR requires a runtime: somewhere to execute server-side code. Vercel and Netlify both support this through serverless functions. Cloudflare Pages supports it through Cloudflare Workers (a different runtime with some quirks). A VPS with Node.js supports it with full control.
SSR deployments are more expensive than static deployments because you’re paying for compute on every request, not just bandwidth on cached files. At low traffic, the cost difference is negligible. At high traffic, it matters.
Most marketing sites don’t need SSR. If your developer is proposing SSR for a content-only marketing site, ask why. The answer might be justified (dynamic personalization, authenticated content, live data) or it might be developer preference overriding the simpler option.
What to Ask Before the Site Launches
Before your Astro site goes live, get clear answers to these questions:
Who owns the deployment account? Your Vercel, Netlify, or Cloudflare account should be in your name with your email address as the owner. The developer can have access, but you should be the account owner. If you ever switch developers, account ownership determines whether you can grant access to a new team without the old team’s cooperation.
Where are environment variables stored? API keys, CMS access tokens, and analytics IDs are stored as environment variables in the platform dashboard. These shouldn’t be in the codebase. Make sure you have access to the platform dashboard to manage them.
Is there a deployment preview? Vercel and Netlify both show a preview URL for every pull request — a live, working version of the site before changes are merged. This makes reviewing changes straightforward for non-developers. Confirm this is configured.
What’s the build time? Know your site’s build time — how long from a content update to live changes on the site. For most Astro marketing sites: 45–90 seconds. For large content libraries: 3–5 minutes. If you’re updating content frequently, this cadence matters.
Are redirects configured? Old URLs need to redirect to new ones for SEO continuity. In Astro, redirects live in platform configuration files (a vercel.json or netlify.toml file). Make sure these are set up before launch, not after you notice traffic drops.
FAQ
Do I need to pay for hosting if I use Astro? Not necessarily. Vercel, Netlify, and Cloudflare Pages all have free tiers that cover most small to medium marketing sites. If your site gets significant traffic (50,000+ monthly visits), a paid plan in the $20–$45/month range is typical. That’s substantially cheaper than managed WordPress hosting at comparable traffic levels.
Can I switch from Vercel to Netlify later? Yes, but it requires reconfiguring deployment pipelines and rebuilding any platform-specific features (Netlify forms, Vercel Edge Functions, etc.). The Astro site files are portable — they work on any platform. The deployment configuration is not. Budget 4–8 developer hours for a platform migration.
What’s the difference between static deployment and SSR? Static: Astro builds all pages at deploy time. Visitors get cached HTML files from a CDN. Fast, cheap, simple. SSR: Astro generates pages on every request. Required for personalized or authenticated content. Costs more in compute, adds infrastructure complexity. Most marketing sites should be static.
Does Cloudflare Pages work with Astro’s image optimization? Astro’s built-in image optimization works with static deployments. For Cloudflare Pages SSR mode, some image optimization features require Cloudflare Images (an add-on service). For a static build, image optimization runs at build time and works the same on all platforms.
Who manages SSL certificates on these platforms? All three major platforms (Vercel, Netlify, Cloudflare Pages) handle SSL automatically. You connect your custom domain, they provision and renew the certificate. You don’t manage it. This is a significant operational advantage over self-managed hosting where certificate renewal is a manual task.
What happens if Vercel goes down? Vercel’s historical uptime on static hosting is above 99.99%. In practice, a full outage affecting static file serving is extremely rare. If it does happen, the recovery options depend on your setup: if your site is static files on a CDN, the files are cached globally and a partial outage may not affect all visitors. A full rollover to Netlify or Cloudflare Pages is a few hours of work if needed.
Can I use a traditional domain with any of these platforms? Yes. You connect your existing domain by updating DNS records to point to the platform’s CDN. This takes 10–30 minutes and requires access to your domain registrar. Vercel, Netlify, and Cloudflare Pages all have step-by-step guides for this process.
Where your Astro site deploys is an infrastructure decision with long-term operational implications. For most business marketing sites, Vercel or Cloudflare Pages on a free or low-cost plan is the right answer. For sites with international audiences and high traffic, Cloudflare Pages’ edge network is worth the switch. Our custom WordPress development and Astro build services both include deployment setup as part of the build, not as an add-on. See our fixed-price packages to understand what’s included.