Head-to-head
Cloudflare Pages vs Vercel
Two hosts, side by side. Pricing, features, and the trade-offs that actually matter.
Cloudflare Pages from Free
Static + edge-functions hosting on the world's biggest CDN, free for almost everyone.
HQ US · founded 2009
Vercel from Free
The default home for Next.js, with a polished DX and a love-it-or-hate-it bill.
HQ US · founded 2015
Quick verdict
Cheapest: Vercel wins on entry price (Free vs Free).
More features: Vercel ships more first-party platform features out of the box.
Region: Cloudflare Pages is HQ'd in US; Vercel in US.
Cheapest plans, side by side
| Cloudflare Pages | Vercel | |
|---|---|---|
| Entry plan | Free | Hobby |
| Price | Free | Free |
| CPU | — | — |
| RAM | 0 GB | 0 GB |
| Disk | — GB | — GB |
| Bandwidth | unmetered | 100 GB |
Feature parity
| Cloudflare Pages | Vercel | |
|---|---|---|
| Managed Postgres | × | ✓ |
| Managed Redis | × | ✓ |
| Object storage | ✓ | ✓ |
| One-click apps | × | ✓ |
| Private network | × | × |
| IPv6 | ✓ | × |
| DDoS protection | ✓ | ✓ |
| Snapshots | × | × |
| Public API | ✓ | ✓ |
| Terraform | ✓ | × |
Cloudflare Pages pros
- +Unlimited bandwidth on the free tier — no caveats
- +Cloudflare's CDN is in 300+ cities; latency is near-optimal everywhere
- +Workers (edge functions) and KV/D1/R2 in the same dashboard
Cloudflare Pages cons
- −Build runners are shared and slower than Vercel/Netlify on cold cache
- −Workers have a different mental model than Lambda — porting Express apps is non-trivial
- −Logs and observability lag behind Vercel's polish
Vercel pros
- +Push to GitHub, get a preview URL — no other host has tightened this loop further
- +Image optimisation, ISR, edge functions all wired in by default
- +Generous free tier covers solo side projects
Vercel cons
- −Bandwidth and function execution beyond the free tier scale aggressively
- −Pro plan starts at $20/seat/month — expensive for a solo dev
- −Long-running functions are not the platform's strength (15-min cap, costly)