Hosting an Astro site is not the same decision as hosting a WordPress site. The platforms are different, the cost structures are different, and the tradeoffs matter more than most agencies explain. Here’s what you’re actually choosing between.
Why Astro Hosting Is Different from WordPress Hosting
WordPress needs a server. It runs PHP, connects to a MySQL database, and generates HTML on every request. Your host is running a computer that processes PHP code every time someone visits your site. That’s why shared WordPress hosting costs $5–30/month for a basic setup and can cost $100+/month on managed platforms like WP Engine or Kinsta.
An Astro static site is files. Pre-built HTML, CSS, images. When someone visits your site, the host serves a file — no processing, no database query, no PHP execution. File delivery is what CDNs (content delivery networks) were built for. It’s faster and dramatically cheaper.
This is why the three main Astro hosts — Vercel, Netlify, and Cloudflare Pages — all offer free tiers that are genuinely usable for production sites, not just toy projects. The cost structure shifts to compute-on-demand (serverless functions) only when your site has dynamic components that run server-side logic.
Vercel
Vercel is the hosting platform built by the team behind Next.js. It has excellent Astro support — Astro deploys to Vercel cleanly, and the platform is mature, well-documented, and widely used.
What it does well. Deploy from Git is seamless: push to GitHub, site rebuilds and deploys in 20–60 seconds. Preview deployments for every branch — before merging a change, you get a URL where you can see the change live. The dashboard is clear, performance analytics are built in, and the Edge Network covers 100+ regions globally.
Free tier. Vercel’s Hobby plan is free and includes 100GB bandwidth/month, unlimited deployments, and serverless functions. For a business site under 50,000 visits/month, you will likely never pay a cent for static hosting.
Paid tier. The Pro plan is $20/month per team member. For a developer managing client sites, that’s $20/month for the developer — the client’s site itself doesn’t have its own cost unless you exceed bandwidth limits or use compute-heavy serverless features.
The tradeoff. Vercel’s free tier has a commercial use restriction — technically, the Hobby plan is for personal projects. Using it for a client or business site requires the Pro plan ($20/month). In practice, this is enforced through terms of service, not technical limits. Many small business sites run on Vercel Hobby for years without issue. If you want to be compliant, budget $20/month.
Client management. Vercel’s dashboard is reasonably non-technical for viewing deployments and analytics. Triggering a rebuild (e.g., after updating content in a CMS) is typically automated via webhook — the CMS pings Vercel, Vercel rebuilds. Content editors don’t interact with Vercel at all in a well-configured setup.
Netlify
Netlify is the other major Astro host. It has been in this space longer than Vercel and has a broader feature set in some areas.
What it does well. Netlify’s form handling is a standout feature — you can add a simple attribute to an HTML form and Netlify handles submission, spam filtering, and notification emails without any backend. For sites with contact forms, this removes a dependency on third-party form services. Netlify also has a mature branch deploy and preview system, solid CDN coverage, and good documentation for Astro specifically.
Free tier. The Starter plan is free with 100GB bandwidth/month, 300 build minutes/month, and 125K serverless function invocations/month. Commercial use is explicitly allowed on the free tier — this is a meaningful difference from Vercel. For a small business site, Netlify free is legitimately production-ready without terms concerns.
Paid tier. $19/month for the Pro plan, which increases build minutes, bandwidth, and adds team features. For a single-developer/single-client setup, free is usually sufficient.
The tradeoff. Netlify’s interface is slightly less polished than Vercel’s. The build system can be slower on cold starts. Netlify Functions (serverless) are not as capable as Vercel’s Edge Functions for latency-sensitive use cases. For a static site with minimal serverless needs, this doesn’t matter.
Client management. Netlify has a dedicated CMS product (Netlify CMS, now Decap CMS) that can provide a basic editorial interface for Markdown-based Astro sites. If you have a simple content model and don’t want to pay for Sanity or Contentful, this is a workable option. Rebuilds can be triggered manually from the Netlify dashboard — a non-technical client can push a “Deploy site” button after making CMS changes.
Cloudflare Pages
Cloudflare Pages is the newest of the three and runs on Cloudflare’s global network — the same infrastructure that powers 20% of the internet.
What it does well. Cloudflare’s network is the most globally distributed of the three — 300+ edge locations vs Vercel’s 100+. For audiences spread internationally, this means lower TTFB from more regions. The free tier is also the most genuinely unlimited: unlimited bandwidth (not 100GB), unlimited requests, and unlimited sites. Cloudflare doesn’t cap bandwidth on the free tier at all.
Cloudflare Workers (their serverless platform) are among the fastest in the industry — Workers run at the edge, not in a centralized data center. For serverless functions, Cloudflare’s latency profile is best-in-class.
Free tier. Unlimited bandwidth, 500 build minutes/month, 1 build at a time, unlimited sites. Commercial use allowed. The bandwidth limit removal is significant: a site that gets 500,000 visits/month with large images doesn’t accidentally incur overage fees.
Paid tier. $20/month for Pages Pro, which adds concurrent builds, higher function invocation limits, and faster builds. For most sites, free is sufficient.
The tradeoff. Cloudflare Pages is newer and the developer tooling is less mature than Vercel or Netlify. Preview deployments exist but the branch deploy workflow is slightly less polished. The Cloudflare dashboard can be intimidating — the Pages product lives inside a larger platform with many unrelated products. Client-facing URL for previews is less clean.
Cloudflare’s serverless ecosystem (Workers, D1 database, R2 storage) is powerful if you want to build more complex functionality, but it’s a different mental model than Vercel or Netlify’s function setup. For developers comfortable with Cloudflare’s ecosystem, this is a strong choice. For developers who just want to deploy an Astro site, Vercel or Netlify have less friction.
Client management. Same pattern as the others — content editors use the CMS, Cloudflare Pages rebuilds via webhook. The Pages dashboard is usable for developers but not designed for non-technical client interaction.
Direct Comparison: What Actually Matters
| Vercel | Netlify | Cloudflare Pages | |
|---|---|---|---|
| Free bandwidth | 100GB/month | 100GB/month | Unlimited |
| Commercial use free | No | Yes | Yes |
| Build minutes free | 6,000/month | 300/month | 500/month |
| Global edge locations | 100+ | 100+ | 300+ |
| Serverless performance | Excellent | Good | Best-in-class |
| Developer experience | Best | Very good | Good |
| Built-in forms | No | Yes | No |
| Paid tier | $20/month | $19/month | $20/month |
For a standard Astro marketing site with a CMS, all three platforms produce pages that score 95–100 on Lighthouse. The CDN performance difference between them is typically under 30ms TTFB on most audience geographies. That difference won’t affect your Core Web Vitals scores or Google rankings.
The practical differentiators are the free tier bandwidth limits (Cloudflare wins), the commercial use terms (Netlify and Cloudflare allow it free), and developer ergonomics (Vercel’s DX is the best).
What Non-Developer Clients Can Actually Manage
The short answer: none of these platforms are designed for client self-management. They’re developer infrastructure tools.
In a well-built Astro setup, a non-technical client doesn’t need to interact with the hosting platform at all. Their workflow is:
- Log in to the CMS (Sanity, Contentful, or similar)
- Edit or publish content
- Click “Publish” — the CMS sends a webhook to the host
- The site rebuilds and deploys in 30–90 seconds
- The new content is live
The client never sees a Vercel or Netlify dashboard. The hosting layer is invisible to them, which is the right design.
Where this breaks down is when a non-technical client is managing the hosting relationship directly — paying the bill, having account access, potentially needing to trigger manual rebuilds or check deployment status. Netlify’s dashboard is the most approachable for non-developers. Vercel is close. Cloudflare’s interface is the most complex for someone unfamiliar with DNS and web infrastructure.
If a client needs to own and manage the hosting account without developer involvement, Netlify is the pragmatic recommendation.
Astro SSR Hosting (Dynamic Routes)
If your Astro site uses SSR (server-side rendering) for any routes — user authentication, dynamic search, personalized content — the hosting picture changes.
Static file serving is the same on all three platforms. But server-side rendering requires a serverless function that runs on every request. That function invocation model has different cost structures.
Vercel and Netlify price serverless function invocations above free tier limits. Cloudflare Workers are priced per 10 million requests and are typically cheaper at scale. For a site that makes heavy use of SSR, Cloudflare’s function pricing model is often more cost-effective.
For sites that are primarily or fully static — which describes most business marketing sites — this distinction doesn’t matter. Static file delivery is free or near-free on all three platforms.
Self-Hosted Astro
You can self-host Astro on a VPS (DigitalOcean, Linode, Hetzner). For a static site, this means copying your build output to a server and serving it with Nginx. It works. The cost is $5–10/month for a basic VPS.
The tradeoff: you lose the CDN global edge network, which means TTFB for international visitors is slower. You also take on server maintenance — security patches, uptime monitoring, backups. For most clients, paying nothing for Cloudflare Pages or Netlify’s free tier with global CDN is a better deal than self-managing a VPS for $5–10/month.
Self-hosting makes sense when there are specific compliance requirements (data residency in a particular country), when a client’s existing infrastructure already has CDN and server management in place, or when a site has very specific server-side requirements that don’t map to serverless functions.
The Recommendation
For most Astro business sites:
Use Cloudflare Pages if international audience distribution matters, bandwidth overages are a concern, or you want the best free tier terms (commercial use allowed, unlimited bandwidth).
Use Netlify if you want built-in form handling, a mature platform with a non-technical client can occasionally need access, or you’re using Decap CMS for content management.
Use Vercel if developer experience and deployment ergonomics are the priority, you’re already in the Vercel/Next.js ecosystem, and the $20/month Pro plan is in budget.
All three are production-grade. The performance differences are marginal for most sites. Choose based on the operational factors that affect your specific setup.
For a complete picture of what a custom Astro build involves — CMS selection, hosting configuration, deployment pipeline, structured data, performance optimization — see our custom WordPress development service page for comparison, or review the framework choice in when to choose Astro over WordPress. All Designodin Astro builds include hosting configuration and deployment pipeline setup as part of the project scope.
FAQ
Can I switch Astro hosts after launch? Yes, and it’s relatively easy. Astro’s static output is platform-agnostic — it’s HTML, CSS, and JS files. The build artifacts don’t care where they’re deployed. You’d reconfigure your CI/CD pipeline to point to the new host and update your DNS. This typically takes an hour for a developer.
What happens if my Astro site exceeds the free tier bandwidth limit on Vercel or Netlify? Vercel throttles or pauses the site until the billing period resets unless you upgrade to Pro. Netlify charges overage fees at $0.55 per additional GB. Cloudflare Pages has no bandwidth limit, so this situation doesn’t arise there.
Do I need a custom domain, or can I use the hosting platform’s subdomain? All three platforms give you a free subdomain (yoursite.vercel.app, yoursite.netlify.app, yoursite.pages.dev). For a business site, a custom domain is a basic professional requirement. Custom domain setup is free on all three platforms and takes 10–15 minutes if your DNS is accessible.
Can Vercel, Netlify, or Cloudflare Pages handle an Astro site with 100,000 monthly visitors? Yes, comfortably. CDN file delivery is built for this. A 100,000-visit/month site with average 2MB page weight uses roughly 200GB of bandwidth per month. That exceeds Vercel and Netlify’s free tiers (100GB each) and would cost approximately $55/month in Netlify overages. On Cloudflare Pages, it’s free.
Does the hosting platform affect my Google Lighthouse score? For static sites, slightly. The primary variable is TTFB (Time to First Byte), which varies by CDN edge network density. The difference between Vercel, Netlify, and Cloudflare Pages for a US/EU audience is typically 10–40ms TTFB. That difference does not affect Core Web Vitals scores meaningfully — all three platforms serve pages fast enough that TTFB is not the LCP bottleneck. The bigger LCP variables are image optimization and JavaScript loading strategy, which are in the Astro build itself.
Is there a hosting platform specifically recommended for Astro? Astro’s own documentation lists Vercel, Netlify, and Cloudflare Pages as primary deployment targets with first-party integration support. All three have official Astro adapters. There’s no single “official” host — the choice depends on your project’s requirements. If you’re having a site built by an agency, ask which platform they deploy to and why, and make sure you own the hosting account, not the agency.
If you want transparent pricing on an Astro build including hosting setup and CMS configuration, see our fixed-price packages — no retainer, no lock-in, full handoff.