Cloudflare vs Netlify
Of the 3,549 makers' products we know the hosting of, 385 chose Cloudflare (11%) and 265 Netlify (7%); 8 use both. Among the 860 launched in 2026, Cloudflare is in 20% and Netlify in 4%, against 8% and 7% of those launched in 2024 or earlier. They're different kinds of tool, edge platform and frontend cloud, so the counts don't measure the same choice. Netlify is the more common pick among Astro products (24 vs 21). At our calculator's default usage, Cloudflare comes to $12 a month and Netlify $30, at list prices. On GitHub, 15 public pull requests moved projects from Cloudflare to Netlify, and 125 the other way.
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 | 385 makers' products · 232 open-source projects | 265 makers' products · 62 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 | $30/mo Pro 3,000 credits |
| Moved to it on GitHubpull requests since Oct 2024 | 125 from Netlify | 15 from Cloudflare |
| Downloads | 21.3M/wk3.1× vs npm | 375.2k/wk−47% 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 | 48+ (5 major) | 15 (4 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for hosting.
| Framework | |||
|---|---|---|---|
| 102 | 58 | All 1312 Next.js products' picks → | |
| 21 | 24 | All 112 Astro products' picks → | |
| 21 | 9 | All 147 React products' picks → | |
| 2 | 4 | All 14 Nuxt products' picks → | |
| 4 | 0 | All 31 Laravel products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the hosting decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2022 or earlier | 8% 10 | 13% 15 | 118 |
| 2023 | 13% 12 | 3% 3 | 89 |
| 2024 | 7% 41 | 6% 36 | 582 |
| 2025 | 10% 65 | 6% 35 | 629 |
| 2026 | 20% 176 | 4% 32 | 860 |
Cost as you grow
At 100k requests Cloudflare costs less ($0 vs $9.00); and still does at 500M requests ($871 vs $2,662). 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 | $9.00 Personal |
| 0.5 | $5.12 Workers Paid | $9.00 Personal |
| 1 | $5.84 Workers Paid | $12 Personal |
| 5 | $12 Workers Paid | $30 Pro 3,000 credits |
| 10 | $19 Workers Paid | $56 Pro 5,000 credits |
| 50 | $88 Workers Paid | $262 Pro 20,000 credits |
| 100 | $175 Workers Paid | $529 Pro 20,000 credits |
| 500 | $871 Workers Paid | $2,662 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.
Everything runs on Workers, D1 and R2. The big one for me is that R2 doesn't charge for egress. This app serves a lot of audio files and I would not survive normal bandwidth pricing.
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.
Our front end runs on Netlify, as do most of our examples where serverless functions are used. It's so easy to get started, and so powerful once you start pushing harder.
Upwork - hiring contractors Netlify - hosting the front end What have been the most influential books, podcasts, or other resources? Paul Graham’s blog.
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
Who uses each
What makers pair each with
Neither quite right?
See the whole hosting decision →Questions
Cloudflare or Netlify: which do makers choose?
Of the 3,549 makers' products we know the hosting of, 385 chose Cloudflare (11%) and 265 Netlify (7%); 8 use both. Among the 860 launched in 2026, Cloudflare is in 20% and Netlify in 4%, against 8% and 7% of those launched in 2024 or earlier. They're different kinds of tool, edge platform and frontend cloud, so the counts don't measure the same choice. Netlify is the more common pick among Astro products (24 vs 21). At our calculator's default usage, Cloudflare comes to $12 a month and Netlify $30, at list prices. On GitHub, 15 public pull requests moved projects from Cloudflare to Netlify, and 125 the other way. Choose Cloudflare if your app is a static site or docs and should cost nothing to host; choose Netlify if you built a Next.js or other frontend-heavy app and want preview URLs on every pull request.
Can you use Cloudflare and Netlify together?
8 makers' products we track use both, often one replacing the other or each for a different part of the product: BurnLink, Hey Noah, DEV Community, Prisma, Random Song Generator and others.
When should I pick Cloudflare over Netlify?
Pick Cloudflare if: Your app is a static site or docs and should cost nothing to host.
When should I pick Netlify over Cloudflare?
Pick Netlify if: You built a Next.js or other frontend-heavy app and want preview URLs on every pull request.
Which is cheaper, Cloudflare or Netlify?
At requests 5 million requests, data transfer out 100 GB, serverless function compute 100 GB-hours: Cloudflare $12/mo (Workers Paid), Netlify $30/mo (Pro 3,000 credits), at list prices.
How do Cloudflare and Netlify compare in cost as you grow?
At 100k requests Cloudflare costs less ($0 vs $9.00); and still does at 500M requests ($871 vs $2,662). Cheapest usable plan at each scale, at list prices.
Are people switching from Cloudflare to Netlify?
Public GitHub pull requests since 2024-10-02: 15 from Cloudflare to Netlify, 125 from Netlify to Cloudflare.

