Cloudflare vs Netlify
Two sides of the hosting decision: edge platform and frontend cloud. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- Your app is a static site or docs and should cost nothing to host
Use it whenYou want the cheapest global hosting and can live with the Workers runtime.
Trade-offThe Workers runtime isn't full Node.js; some libraries need adapting.
- You built a Next.js or other frontend-heavy app and want preview URLs on every pull request
Use it whenYour site is static or JAMstack on a framework other than Next.js.
Trade-offServer-side features run as functions with time limits; long-running work needs another host.
At a glance
| Used by | 374 makers' products · 190 open-source projects | 239 makers' products · 54 open-source projects |
|---|---|---|
| Cost at default usagerequests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours | $12/mo Workers Paid | $27/mo Pro 3,000 credits |
| Moved to it on GitHubpull requests since Oct 2024 | 125 from Netlify | 15 from Cloudflare |
| Downloads | 18.6M/wk3.1× vs npm | 323.1k/wk−55% vs npm |
| Pricing | Generous free tier; usage-based paid plans. · paid from $5/mo (Workers Paid) | Free tier; paid plans from $9/month, billed by monthly credits. · paid from $9/mo |
| Free tier | Yes | Yes |
| Open source | No | No |
| Incidents, 90 daysfrom its status page | 50+ | 11 (4 major) |
Cost as you grow
Both cost $0 up to 100k requests; from 500k requests Cloudflare costs less ($5.12 vs $9.00); and still does at 500M requests ($871 vs $2,659). They're different kinds of tool — edge platform and frontend cloud — so the prices don't buy the same thing.
The numbers, plan by plan
| Requests per month | Cloudflare | Netlify |
|---|---|---|
| 0.1 | $0 Workers Free | $0 Free |
| 0.5 | $5.12 Workers Paid | $9.00 Personal |
| 1 | $5.84 Workers Paid | $9.00 Personal |
| 5 | $12 Workers Paid | $27 Pro 3,000 credits |
| 10 | $19 Workers Paid | $53 Pro 5,000 credits |
| 50 | $88 Workers Paid | $259 Pro 20,000 credits |
| 100 | $175 Workers Paid | $526 Pro 20,000 credits |
| 500 | $871 Workers Paid | $2,659 Pro 20,000 credits |
From each vendor's pricing page: Cloudflare, Netlify.
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Cloudflare to Netlify" or the reverse — real code changes, by developers in general rather than makers only.
- Move hosting from Netlify to a Cloudflare Workervz-12/chromebook-gamez · 2026-10-01
- Move hosting from Netlify to a Cloudflare Workervz-12/chromebook-gamez · 2026-10-01
- Migrate Cook & Flame from Netlify to Cloudflare + Supabaseseshydragon/cookryumyum · 2026-09-29
- Migrate the docs site from Netlify to Cloudflare Pageslukebennett88/luke-ui · 2026-09-27
- Cut over hosting docs from Netlify to Cloudflare Pagesskwritesstuff/musicblog · 2026-09-27
- Move hosting from Netlify to Cloudflare Pagesconnolmj/bigblindcap · 2026-09-25
- Migrate deploy target from Netlify to Cloudflare Workersmakdaf1rst/hadith-keeper-vault · 2026-09-18
- docs(plans): plan the Host deployment cutover from deleted Netlify to Cloudflare (relates #1467)endaye/lmdj · 2026-09-17
- Update footer hosting notice from Netlify to Cloudflaremoomdbe/legoutdevivre-site · 2026-09-16
- feat(docs): migrate hosting from Netlify to Cloudflare Workers Static…thedannywahl/pantoken · 2026-09-14
- Migrate hosting from Cloudflare Pages to Netlifyhinside-as/hinside-website · 2026-08-19
- Switch deployment target from Cloudflare Workers to Netlifysupakin-source/DocuMan · 2026-08-12
- Switch hosting target from Cloudflare Pages to Netlifymatdonaruno/Chillmeru · 2026-07-07
- Switch deploy config from Cloudflare Pages to Netlifyrkaponm/BuzzFam- · 2026-06-30
- feat(netlify): migrate from Cloudflare Workers + D1 to Netlify + Netlify DB (Neon/Postgres)smkdwiguna/dwiguna-info · 2026-06-05
- docs: switch README deploy section from Cloudflare Pages to Netlifyag-tech-group/hera-streamer-invitational-2026-web · 2026-05-23
- chore: migrate from Cloudflare to Netlify deploymentAisha-designed-it/aisha-designs-hub · 2026-05-06
- Migrate from Cloudflare to Netlify adapter + add middleware unit testsDillie-O/dillieo-site-v3b · 2026-04-30
- Migrate deployment from Cloudflare Pages to Netlifyapourchoux/oqoro_offmarket · 2026-04-21
- feat: cloudflare proxy scripts to netlify appsungyongcho/gomoku · 2026-02-14
What makers say
Makers on using it for hosting, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
Cloudflare handles everything for iVox — DNS, website hosting on Pages, R2 file storage for downloads, and Workers for the license backend. All of it, basically free at indie scale.
Cloudflare Workers and Pages let us deploy instantly at the network edge, delivering lightning-fast performance and reliability without the usual complexities of traditional hosting.
Snapset’s website, licensing backend, and email routing all run on Cloudflare. Pages, Workers, and D1 let me keep the infrastructure simple and manage almost everything in one place.
Hosts tidymacapp.com and serves the app itself. Deploying is dragging a folder onto a page. For a solo dev shipping a $9 utility, that's exactly the right amount of infrastructure.
Turn has been served from Netlify since v1 and it handles our global user base well. I also love being able to use the A/B testing function of Netlify to test new features.
Netlify is great for hosting next.js. I used to love Vercel, but decided to switch due to the recent updates. Overall it has been quick and easy to deploy and have so far not had any issues.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

