- A fully static Astro site needs no adapter and runs well on Vercel, Netlify and Cloudflare.
- Forms decide a lot: Netlify Forms works from your HTML, while Vercel and Cloudflare need a small function or Worker.
- On a static build, Astro's redirects are meta refresh pages, so put migration redirects in the host's own file.
- Vercel's terms limit the free Hobby plan to personal or non-commercial use, so a business site needs a paid plan.
- Cloudflare does not charge for requests to static assets, which suits high traffic static sites.
The short answer
All three hosts run a static Astro site well, so start from what your marketing team needs, not from a ranking. If the site is fully static, any of them works. If you want forms without writing a backend, Netlify Forms is the shortest path. If you expect a lot of traffic on a small budget, Cloudflare serves static files with no request charge. If your team lives in preview links and you have a long redirect list from a migration, Vercel handles both well, on a paid plan for a business site.
The rest of this post walks through the five things that decide it: static or server routes, forms, previews, redirects and domains.
First question: fully static or server routes?
Astro builds a static site by default. Each of Astro's deploy guides says the same: no adapter is needed for static output. You push to Git, the host runs astro build, and it serves the dist folder. See Astro's guides for Vercel, Netlify and Cloudflare.
You need an adapter only when a page or route has to run on request: a form endpoint, a personalised page, a search API. Then you add one with npx astro add vercel, netlify or cloudflare, and that route runs as a serverless function or a Worker.
Most marketing sites are static pages plus one or two small routes. That is the case worth planning for, because it means the free plans, limits and form options below matter more than raw speed.
Forms: where does the submit go?
A static page has no server, so a form needs somewhere to post. Each host answers this differently.
- Netlify. Netlify Forms reads your HTML at deploy time. You add
data-netlify="true"to the form tag and turn on form detection, with no extra JavaScript. One catch from Netlify's forms docs: a form drawn by JavaScript in the browser is not found by the build, so you add a matching hidden HTML form. - Vercel. No built-in form product for this. You write a small function that receives the post and sends it on, to your CRM, a sheet or an inbox.
- Cloudflare. The same idea with a Worker. Cloudflare's Workers pricing page lists 100,000 requests a day and 10 ms of CPU time per request on the free plan, which is plenty for a lead form.
If you write your own endpoint on any host, check every submission on the server. Our post on stopping form spam lists the server checks that apply to any site.
Preview links for every change
A preview deployment is a private copy of the site for one change, so marketing can check a page before it goes live. All three have them, with small differences.
- Vercel. Every push to a branch builds a preview deployment, and pushes to the production branch go live. The Hobby plan includes Vercel Authentication for previews.
- Netlify. Pushes trigger deploy previews and production deploys, and the pricing page lists unlimited deploy previews on the free plan.
- Cloudflare. Pages allows unlimited preview deployments on the free plan. On Workers, each new version can get its own Version URL. Cloudflare's docs say these are public once turned on, unless you protect them with Cloudflare Access or switch them off.
If unreleased pages must stay private, check how each host protects previews before you share links.
Redirects: the part that protects your rankings
If you are moving an existing site to Astro, redirects matter more than anything else on this list. One detail trips people up: on a static build, Astro's own redirects become HTML pages with a meta refresh tag. Astro's routing guide says the status code is not used by the server in that case. Supported adapters write the redirects into the host's config instead.
For a migration, put old URLs in the host's own redirect file so they answer with a real permanent redirect:
- Vercel:
vercel.json, up to 2,048 redirects, per Vercel's redirect docs. Bulk redirects from a CSV or JSON file cover larger lists. Vercel's permanent redirects use 308. - Netlify: a
_redirectsfile ornetlify.toml, where the status is 301 by default. Netlify notes that a very large rule set can fail a deploy, and suggests wildcards past 10,000 rules. - Cloudflare: a
_redirectsfile with 2,000 static and 100 dynamic rules, on both Pages and Workers.
Build the list with our redirect map tool, which exports vercel.json and _redirects, then test the live URLs with the redirect checker.
Custom domains
Every host connects your own domain with SSL on its free plan. The limits are far above what a marketing site needs: Vercel Hobby lists 50 domains per project, and Cloudflare Pages lists 100 custom domains per project on the free plan. Netlify's pricing page lists custom domains with SSL on its free plan.
One SEO detail from Vercel's docs applies to every host: if the host's own address (such as your-project.vercel.app) and your domain both serve the site, redirect the host address to your domain or set a canonical tag, so search engines pick the right one.
Free plans, as written today
We read each vendor's own page for this. Plans change, so check again before you choose.
| Host | What the free plan says | Watch for |
|---|---|---|
| Vercel Hobby | 100 GB fast data transfer, 1,000,000 function invocations, 100 deployments a day | The terms limit Hobby to personal or non-commercial use |
| Netlify Free | A 300 credit limit, unlimited deploy previews, custom domains with SSL | Bandwidth and requests spend credits |
| Cloudflare | Pages: 500 builds a month, 20,000 files, unlimited previews. Workers: 100,000 requests a day | Requests to static assets are free and unlimited |
The Vercel line is the one most teams miss. A company marketing site is commercial use, so plan for Vercel's paid plan from the start. The Hobby figures come from Vercel's Hobby plan page.
How to choose: match the host to the job
- Pick Cloudflare if the site is fully static or close to it, traffic is high or spiky, and you want a free plan you can use for a business. It also suits teams whose DNS is already on Cloudflare.
- Pick Netlify if forms are the main dynamic need and you would rather not write or maintain a form endpoint.
- Pick Vercel if your team reviews every change on preview links, you have a large redirect list from a migration, and a paid plan is fine. It is also a natural fit if your developers already run other projects there.
- Any of them if the site is static and none of the above stands out. Then choose the one your developer knows best, because support after launch matters more than small differences.
A static Astro build is a folder of files, so you are not locked in. Keep redirects and headers in one list you can rewrite for a new host, and a move later is mostly config.
What to do next
Write down three things: which routes need a server, where form leads should go, and how many old URLs need redirects. That list picks the host for you. Budget for hosting next to the build; our post on what an Astro site costs covers the rest of the sums.
We build marketing sites on Astro and Sanity and move sites with Webflow to Astro migrations, including the host setup, redirects and forms. Tell us about your site and we will suggest a host for it.



