Faundr
DocsPTSign in
Hosting

Cloudflare vs Vercel vs Netlify

Cloudflare, Vercel, Netlify side by side: price, free tier, who each one fits and when to skip it.
Item
Cloudflare
Vercel
Netlify
What it doesRuns your site and serverless back end on Cloudflare's global network, deployed from GitHub.Hosting from the makers of Next.js, with a preview deploy for every pull request.Hosts sites and front ends with serverless functions, forms and deploys from Git.
Best forA small SaaS that wants a fast front end plus API on the edge and a bill that stays near $5 a month while it grows.A founder building the SaaS in Next.js who wants to push to GitHub and get a live preview link without touching any config.A landing page or front-end SaaS that wants built-in forms and a cheap $9 plan for a solo founder.
Skip it ifYour back end needs long-running processes, native Node libraries or a regular server, since Workers run in a restricted runtime.You are about to charge customers on the free plan, which is for non-commercial use only, or you fear an uncapped usage bill in dollars.You deploy many times a day on the free plan, since each production deploy eats 15 of your 300 monthly credits.
SetupA little code. An afternoon for a static site; a day or two if your back end needs changes to fit the Workers runtime.A little code. About 15 minutes for a Next.js app already on GitHub.A little code. About 15 minutes for a static site or front end already on GitHub.
PriceWorkers Paid from $5/month (10M requests included)Pro at $20/month per developer seat, with $20 of usage creditPersonal $9/month, Pro $20/month with unlimited members
What it costs in practiceA SaaS with 3 million API requests a month at about 5 ms of CPU each uses 15 million CPU ms. Workers Paid includes 10 million requests and 30 million CPU ms, so the bill is the $5 minimum. Doubling traffic still fits. Estimate.A Next.js SaaS with one developer, 200 GB of traffic and light API use: Pro is $20/month with $20 of usage credit, and Flat Rate CDN covers up to 1 TB of transfer, so it usually stays at $20. A second developer adds $20. Estimate.Personal plan, $9/month with 1,000 credits: 30 production deploys (450) + 15 GB of traffic (300) + 500,000 requests (100) + 5 GB-hours of functions (50) = 900 credits. It fits, with little room left. Estimate.
Free plan100,000 Worker requests a day, 500 Pages builds a month and up to 100 Pages projects.Hobby plan: 100 GB of transfer and 1M function invocations a month, for personal non-commercial use only.300 credits a month; a production deploy costs 15 and each GB of bandwidth costs 20.
Free tier100k requests/day, 500 builds/month100 GB transfer, 1M functions/mo (non-commercial)300 credits/month
First paid plan$5/month (10M requests)Pro: $20/month per seatPersonal: $9/month
Best forStatic sites, Astro, Next.js, edge APIsNext.js and React front endsStatic sites, Astro, Jamstack
Open sourceNo: noNo: noNo: no
Before you build
  • On the free plan each request gets only 10 ms of CPU time. Code that works on your laptop can fail once it does real work, like hashing passwords or parsing a big file. Paid raises it to 30 seconds by default.
  • The free plan stops at 100,000 requests a day (reset at midnight UTC). Past that, visitors get Error 1027 until the next day.
  • Workers is not full Node.js. Modules like child_process, worker_threads and vm are empty stubs: they import fine but don't work, so some npm packages break only in production.
  • Each Worker has 128 MB of memory, on free and paid. Loading a big file or image into memory crashes it with Error 1102.
  • Free builds run one at a time and stop after 20 minutes, with 3,000 build minutes a month.
  • Hobby is for non-commercial personal use only. Taking payments, advertising a product, showing ads or being paid to build the site all count as commercial and require Pro.
  • If you pass a Hobby limit, in most cases you wait 30 days before that feature works again. There is no way to pay for extra on the free plan.
  • On Pro, usage past the $20 credit is billed automatically. New teams only get an email alert at $200 by default; your sites keep running and billing unless you turn on Pause Production Deployments.
  • The spend pause is checked every few minutes, not instantly, and when it fires every production site on the team goes offline with a 503 until you resume each one by hand.
  • A function runs for at most 5 minutes on Hobby and Pro by default (800 seconds when configured on Pro), so long background jobs need another service.
  • The free plan has a hard limit of 300 credits. When they run out, every project on the account is paused and visitors see 'Site not available' until next month. You can't buy more on Free.
  • On paid plans auto recharge is off by default. To keep sites up past the monthly credits, a team owner has to turn it on; then each top-up is $5 for 500 credits (Personal) or $10 for 1,500 (Pro).
  • Functions run in Ohio (US) by default. Moving them closer to users in Europe or Asia to cut latency is only available on Pro.
  • A normal function stops at 60 seconds and you can't raise it. Longer work has to go to Background Functions, capped at 15 minutes.
Price checked

Checked on Oct 28, 2026 · official pricing

Checked on Oct 28, 2026 · official pricing

Checked on Oct 28, 2026 · official pricing

Prices are read from each official pricing page on the date shown and can change. Always confirm before signing up.

Popular comparisons

Faundr

Picked your tools? Build it with AI, safely.

Faundr keeps your project’s memory, blocks what can’t be undone and tells you if it’s safe to launch, inside Claude Code and Codex.

Get started free