If you're shipping a static site or Astro/Next.js project from Australia in 2026, you'll land on the same question: Netlify, Vercel, or Cloudflare Pages? Every cloud that markets to developers has one now. The answer used to be clear — Netlify had the best DX and the most generous free tier. That's still mostly true, but Vercel has closed the gap and Cloudflare Pages has become genuinely competitive at scale. Time to separate hype from reality.
Here's the frame: these three dominate Jamstack hosting because they nail the core contract. Push to GitHub, auto-deploy to a preview URL, merge, ship to production. No VPS fiddling, no container orchestration, no DevOps tax. You write code, they run it. All three have AU data centres (or near-equivalents), generous free tiers, and feature parity on the essentials. So the decision is usually: which DX feels best, and which billing model hurts least at scale?
Feature Parity — You're Not Leaving Anything Critical Behind
Every host does the same thing competently: GitHub integration, branch previews, automatic SSL, CDN caching, environment variables per-context (production vs preview), and basic log access. If you're comparing on "can I deploy my Astro site here?", the answer is yes for all three. The differences are in the edges.
Netlify: Built for front-end teams. Best-in-class branch preview workflow. Edge functions (thin layer of server logic near the user). Blobs storage (hot-takes: don't use this for your database — it's file storage, not a data store). Generous free tier: 300 build minutes/month, unlimited deployments. If you're using Claude Code to edit your site with AI-assisted edits and need visual sign-off before merging, Netlify's preview experience is still the gold standard.
Vercel: Next.js first, but treats other frameworks as first-class citizens. Serverless functions baked in (more powerful than edge functions, but slower — 500ms cold start vs 50ms for edge). Draft Mode for on-demand ISR. Analytics built in (Netlify charges for this). Free tier: 100 hours of serverless compute/month. Better for teams that need runtime logic; worse for static-only sites because compute is the bottleneck.
Cloudflare Pages: Cheapest at scale. Edge functions on the Cloudflare Workers runtime (fastest cold starts: 1-5ms). KV storage (key-value, better than Blobs for lightweight caching). Workers Analytics. Free tier: unlimited deployments, limited Workers usage. Billing model shifts at 100k requests/month (flat $20/month includes 50M requests). The pitch: "You'll never pay more than Vercel."
AU Latency — Where It Matters
CDN latency to Australian users is real and measurable. A 200ms delay vs 50ms is the difference between snappy and noticeably slow.
Netlify: Sydney CDN edge (operator: Fastly or equivalent). ~40-60ms from Sydney/Melbourne. Smart routing, cache hits 95%+ on static assets. If your site is mostly static (Astro, Hugo, eleventy), Netlify caching is aggressive and latency is sub-60ms consistently.
Vercel: No dedicated AU edge node in the core regions. SG/JP/Sydney edge runners exist, but not as primary. Latency to AU: ~100-150ms average. That said, Vercel's ISR cache (Incremental Static Regeneration) is powerful — you can cache at Vercel edge for 24h without rebuilding, which masks the latency for repeat views. Fresh content on first hit, cached content thereafter. Better than it sounds, but slower initial visit.
Cloudflare Pages: Cloudflare has 300+ edge locations globally, including Sydney. Latency to AU: ~30-50ms, often better than Netlify because Cloudflare's network is absurdly dense. The catch: cold function invocations can be slow (Workers spin up across the edge, not always locally). For static sites, Cloudflare is fastest. For dynamic sites, the Workers latency story is murkier.
Cost at Scale
This is where the three split. Assume 100K pageviews/month and 10M pageviews/month (typical growth trajectory for a scaling business).
Netlify — 100K pv: Free tier covers it. Build minutes are pooled at 300/month; each build takes 1-5 minutes, so you're fine. Storage is billed on bandwidth overages (rare). Realistic cost: $0.
Netlify — 10M pv: Free tier breaks. You'll hit the Pro plan ($19/month) or Enterprise ($99+). Pro includes 1000 build minutes/month and 200 GB bandwidth/month. 10M pageviews on cached assets is ~1-2 TB bandwidth, so you'll pay overages (~$0.20/GB): ~$400/month total. Plus functions if you use them (~$2.50 per 1M invocations).
Vercel — 100K pv: Free tier works. But compute-heavy logic (serverless functions) gets billed after the free allowance. Static sites: $0. Dynamic sites: $10-50/month depending on function calls.
Vercel — 10M pv: If it's a static site, free tier still covers bandwidth. If it's dynamic, you're at Pro ($20/month) + function costs (~$400+/month for heavy compute). Worst case: $500+/month. Vercel is expensive for function-heavy workloads.
Cloudflare — 100K pv: Free tier. Unlimited deployments, 100K requests/month on Workers, no bandwidth charge. Cost: $0.
Cloudflare — 10M pv: Hits the $20/month tier (includes 50M requests on Workers). Total: $20. If you need KV storage, add $0.50 per 1M read requests (~$5-10/month for typical usage). Realistic total: $25-30/month. Yes, really. Cloudflare is brutal on costs at scale.
Decision Rules
Pick Netlify if: You're shipping an Astro/static site, you use Claude Code for AI edits and want the best branch preview DX, you're on free tier and don't expect to scale past 10M pv soon, or you care about the cleanest onboarding experience. Default choice for 70% of custom websites in AU.
Pick Vercel if: You're running Next.js with ISR, you need SSR rendering on every request, or you want analytics + functions bundled in. Avoid if you're cost-sensitive at scale or shipping a mostly-static site.
Pick Cloudflare if: You're shipping a static Astro site and you know you'll scale past 5M pv (cost advantage kicks in), you want the fastest AU edge latency, or you're already in the Cloudflare ecosystem (DNS, WAF, etc.). The DX is rougher (CLI is less polished than Netlify), but the price-to-performance is unbeatable.
6 FAQs
Can I switch hosts without pain?
Yes. All three read from GitHub and deploy static builds identically. Export your Netlify config to netlify.toml, run one Vercel/Cloudflare CLI command to connect, and deploy. Downtime: zero if you're switching DNS after the first deploy is live.
Which has the best AU CDN?
Cloudflare > Netlify > Vercel, in latency. But Netlify's caching is smarter for static content. In practice, you won't feel the difference unless you're serving 100K+ users/day.
Are preview deploys free?
All three: yes. Unlimited preview builds/deployments on free tiers. This is the standard that everyone expects now — and rightfully so.
Can I use branch previews with Claude Code?
Yes. See `/blog/netlify-branch-previews-ai-workflow` for the pattern. All three support it; Netlify's PR comments are seamless.
What if I need a database?
None of these are your database host. Use Supabase, Postgres, MongoDB, or whatever. Your static host connects via environment variables. The debate doesn't change.
Which should I teach Elijah?
If he's learning Astro and you're both at Rebuild Relief, start him on Netlify. The DX is gentlest and the free tier never bites. If he's working on Next.js with server logic, Vercel is the obvious path. But honestly, he should understand all three — the switching cost is zero.
The Bottom Line
In 2026, the hosting question is rarely "Can I deploy here?" — all three say yes. It's "Which DX feels like home, and which bill hurts least?" For AU custom websites, Netlify is the default because it nails both. Vercel wins if you're Next.js-heavy. Cloudflare wins if you're at scale and want to optimize for cost. Pick one, push to GitHub, ship. The real work is the code, not the hosting.
If you're using `/pricing` to shop for a host, note that you're probably overthinking it. Pick the one your friends use. Deploy. Come back to this if your bill starts stinging at 10M pageviews — that's when the economics actually matter.