People search “Astro vs Vercel” a lot, but the two aren’t alternatives. Astro is a framework that builds your website. Vercel is a hosting platform that serves the site to visitors. You can run Astro on Vercel, or on Netlify, Cloudflare and many other hosts. So the real question is which host fits your Astro site.
We build Astro sites through our Astro web development service, and this site runs on Astro, hosted on Cloudflare, so weigh that. Every fact below was checked against each project’s own documentation in October 2026.
Short answer: Astro builds the site, and a host such as Vercel, Netlify or Cloudflare serves it. For a business site, check the free plan’s terms first: Vercel’s free Hobby plan is for personal, non-commercial use only. After that, the host matters less than whose name the account is in.
Astro vs Vercel: Framework vs Host
Astro is an open source framework for content-driven websites. It builds pages as HTML at build time and sends JavaScript only for the components that need it. With a server adapter installed, it can also render chosen routes on each request.
Vercel is a cloud platform that builds and hosts websites from a Git repository. It hosts many frameworks, and Astro runs there through the official @astrojs/vercel adapter (source). Vercel also makes Next.js.
So the choice isn’t Astro or Vercel. Usually it’s one of two other questions: Astro or Next.js, which is a framework choice, or Vercel or another host for an Astro site. Our Astro vs Next.js post covers the first question. This post covers the second.
Ownership is worth knowing too. Cloudflare acquired The Astro Technology Company on January 16, 2026. It said Astro stays MIT-licensed and that “You can deploy Astro to any platform or cloud” (source). The same announcement names Netlify and Webflow among the partners in the Astro Ecosystem Fund. Webflow Cloud now hosts Astro too, on Cloudflare’s network; see Astro vs Webflow hosting.
Astro Hosts at a Glance
As of October 2026, from each provider’s documentation:
| Vercel | Netlify | Cloudflare | |
|---|---|---|---|
| Official Astro adapter | @astrojs/vercel 11.0 | @astrojs/netlify 8.2 | @astrojs/cloudflare 14.3 |
| Adapter needed for a static site | No | No | No |
| On-demand routes run on | Vercel Functions | Netlify Functions | Cloudflare Workers |
| Free plan | Hobby | Free | Workers Free |
| Free plan limits | Personal, non-commercial use only; 100 GB data transfer a month | 300 credits a month, no auto recharge | 100,000 Worker requests a day; static asset requests unlimited |
| Paid entry | Pro, $20 per developer seat a month | Personal $9 or Pro $20 a month | Workers Paid, $5 a month minimum |
| How usage is counted | Allowances per resource | Credits for bandwidth, requests, deploys and compute | Worker requests; static asset requests are free |
Static Sites Need No Adapter
If every page is prerendered, Astro’s build output is plain HTML, CSS, JavaScript and images. Any static host can serve it. Astro’s adapter guides for Vercel, Netlify and Cloudflare all say a static site doesn’t need an adapter. You add one for on-demand routes, or for platform services such as Vercel Image Optimization or the Netlify Image CDN (source).
Astro’s deployment docs list guides for 28 hosts (source). They include static-only hosts like GitHub Pages and traditional web hosts like Hostinger. That’s why a static Astro site is easy to move: the files work anywhere. What you set up again is the deploy pipeline, the domain settings and any platform features you used.
Vercel
Vercel connects to a Git repository, builds the site on every push and gives changes a preview URL before they go live. Astro runs there through @astrojs/vercel, and on-demand routes run as Vercel Functions.
The free plan. Hobby is free and includes, each month, 100 GB of Fast Data Transfer, 1 million CDN requests and 1 million function invocations. If you go over, in most cases you wait until 30 days have passed before you can use that feature again (source).
The catch for businesses. Vercel’s docs say the Hobby plan “restricts users to non-commercial, personal use only” (same source). A client’s business site belongs on Pro. On Pro, developer seats cost $20 per user a month and viewer seats are free.
Best fit. Teams already on Vercel, sites that use Vercel services such as Web Analytics or Image Optimization, and Astro sites that sit next to a Next.js app on the same account.
Netlify
At the core, Netlify works the same way: Git-based builds, deploy previews and a global CDN. The @astrojs/netlify adapter runs on-demand routes on Netlify Functions. You can also set it to run Astro middleware on Netlify Edge Functions (source).
Credits, not allowances. Netlify plans are credit-based. Free includes 300 credits a month, Personal ($9 a month) includes 1,000 and Pro ($20 a month) includes 3,000 (source). Usage spends credits:
- 20 credits per GB of bandwidth
- 2 credits per 10,000 requests
- 15 credits per production deploy
- 10 credits per GB-hour of function compute
Deploy previews, branch deploys and form submissions don’t use credits. The Free plan has a hard limit with no auto recharge (source). To put 300 credits in context, that’s 15 GB of bandwidth or 20 production deploys if nothing else were used. A site that publishes often spends credits on deploys as well as traffic.
Built-in forms. Netlify Forms handles form submissions without a separate backend, and submissions don’t use credits. Netlify is also the original home of Decap CMS, formerly Netlify CMS. Our guide to CMS options for non-developers covers it.
Best fit. Sites that want forms without a separate form service, and teams that want a preview of every change before it goes live.
Cloudflare: Workers, Not Pages, for New Projects
Older guides recommend Cloudflare Pages for Astro, and so did the first version of this post. That advice has changed. Cloudflare’s Pages documentation now says “Start new projects with Workers” and links a guide for moving Pages projects over (source). Astro’s Cloudflare adapter goes further: it no longer supports deployment on Cloudflare Pages (source). A fully static Astro site needs no adapter, so Pages can still serve one, but new work belongs on Workers.
What it costs. On Workers, “Requests to static assets are free and unlimited” (source). Requests that run the Worker script, such as server-rendered pages, are billed on Workers pricing. The Free plan allows 100,000 requests a day. Workers Paid has a $5 a month minimum with 10 million requests included (source).
One setting to watch. A Worker can be set to run before static assets with run_worker_first. Requests that match it always run the Worker and count against its limits. On the Free plan, once the limit is reached, those requests get a 429 (Too Many Requests) error rather than the static file (source).
How this site runs. designodin.com runs Astro 6.3.5 in server output mode with the official Cloudflare adapter, deployed as a Worker with static assets. Content pages and API routes, such as our contact form, live in one codebase. The Worker runs first on every request so it can decide what to serve. Astro 7 is the current major release, and we haven’t moved to it yet.
Best fit. Sites that mix static pages with server routes, sites whose DNS is already on Cloudflare, and mostly static sites where free static requests keep costs flat.
On-Demand Rendering and API Routes
Astro prerenders every page by default. With a server adapter installed, a route marked export const prerender = false renders on each request, and endpoints can handle form posts or API calls. Astro’s Cloudflare adapter guide lists the features that need an adapter: on-demand routes, server islands, actions and sessions (source).
That’s when the host’s compute model starts to matter. Vercel and Netlify run those routes as functions, and Cloudflare runs them in the Worker. Our guide to static vs dynamic Astro sites covers when a page needs a server at all.
Self-Hosting with the Node Adapter
To run Astro on your own server, use the official @astrojs/node adapter (11.1 as of October 2026). It has two modes. Standalone mode builds a server that starts when you run the entry file. Middleware mode lets the output plug into another Node.js server such as Express or Fastify (source). A static site doesn’t need the adapter: copy the build folder to any web server.
The trade-off is the work you take on: server updates, security patches, uptime monitoring and backups, plus a CDN if visitors are spread around the world. Self-hosting makes sense when data has to stay in a specific country, or when your company already runs its own servers.
Who Should Own the Hosting Account
Whichever host you choose, put the account in the business’s name and invite the developer or agency as a member. In a well-built setup, editors never touch the hosting dashboard. They publish in the CMS, and the CMS triggers a rebuild. Our guide to Astro deployment options has questions to ask before launch.
When Vercel Is the Better Pick
- You already work on Vercel, with other projects, team members and billing there.
- The site sits next to a Next.js app on the same account.
- You want Vercel’s own services, such as Web Analytics or Image Optimization.
- The budget covers Pro for a business site, since Hobby is for personal use only.
When Cloudflare Is the Better Pick
- Most of the site is static, and static asset requests are free and unlimited.
- Some routes need a server, such as a form handler or an API, next to the static pages.
- Your domain’s DNS is already on Cloudflare.
- You’re starting a new project, and want the setup that both Astro’s adapter and Cloudflare’s docs now point to.
If that describes your project, our Astro web development service builds sites like this, and how we work as an Astro agency shows the setup in detail. Our post on what the Astro framework is covers the model from the start.
Related Comparisons
If you’re working out where an Astro site should live, these posts cover the decisions around it:
- Astro vs Next.js for marketing sites: if the real choice is Astro or the framework Vercel makes
- Astro vs Webflow: code-based framework or hosted visual builder, including Webflow Cloud
- Astro vs Vite: the build tool Astro runs on
- Astro deployment options: what to settle with your developer before launch
- Static vs dynamic Astro sites: when a page needs a server
- When to choose Astro over WordPress: the framework decision that comes before the hosting one
FAQ
Is Astro the same as Vercel?
No. Astro is a framework that builds websites, and Vercel is a platform that hosts them. You can build a site with Astro and host it on Vercel, Netlify, Cloudflare or your own server.
Can I host Astro on Vercel for free?
Yes, on the Hobby plan, which includes 100 GB of data transfer and 1 million function invocations a month. Hobby is for personal, non-commercial use only, so a business site needs Pro.
Can a business use Vercel’s Hobby plan?
No. Vercel’s docs restrict the Hobby plan to non-commercial, personal use. Business and client sites belong on Pro, at $20 per developer seat a month.
Is Cloudflare free for commercial Astro sites?
Cloudflare’s Workers pricing describes the Free plan by usage limits, not by type of use: 100,000 Worker requests a day. Requests for static assets are free and unlimited, so a mostly static Astro site uses little of that limit.
Which Astro adapter should I use?
The one for your host: @astrojs/vercel, @astrojs/netlify, @astrojs/cloudflare, or @astrojs/node for your own server. A fully static site doesn’t need an adapter, unless you use a platform service such as Vercel Image Optimization or the Netlify Image CDN.
Can I host Astro on Hostinger or shared hosting?
Yes. A static Astro build is plain files, so any web host can serve it, and Astro’s docs include a Hostinger deployment guide. Server-rendered routes need a host that can run Node.js, plus the Node adapter.
Should I use Cloudflare Pages or Workers for Astro?
Workers. Cloudflare’s docs tell new projects to start on Workers, and Astro’s Cloudflare adapter no longer supports Pages. A fully static site still works on Pages, but on Workers its static asset requests are free and unlimited too.