Table of Contents
By Khimananda Oli | Last reviewed: August 2026
Choosing between Cloudflare Pages vs Netlify vs Vercel for static sites determines your long-term operational costs, global latency, and vendor lock-in risk far more than any feature checklist suggests. In production environments across Nepal and international markets, I have seen teams migrate away from platforms that initially seemed free but became prohibitively expensive at scale or lacked true edge caching. This guide cuts through marketing claims to compare these three platforms based on actual infrastructure behavior, billing models, and architectural constraints you will face when traffic grows.
Before committing to a platform, ensure your foundation is solid. A well-structured CI/CD pipeline with GitLab CI or GitHub Actions can be adapted to any of these providers, but migrating a poorly automated workflow amplifies technical debt regardless of which host you choose. The right platform should complement your existing automation, not force you to rebuild it.
How does Cloudflare Pages vs Netlify vs Vercel for static sites compare on performance and edge architecture?
Performance differences stem from architecture, not just benchmark numbers. Cloudflare Pages deploys your entire static site to over 300 data centers worldwide. When a user in Kathmandu requests your site, they are served directly from the Tribhuvan International Airport-adjacent PoP with no origin server involved. This is fundamentally different from platforms that maintain regional caches backed by centralized origins.
Vercel’s Edge Network also uses Cloudflare’s infrastructure under the hood for many regions, but its primary optimization targets Next.js server components and API routes. For pure static HTML/CSS/JS, you may not see meaningful gains over Cloudflare Pages, yet you inherit Vercel’s routing complexity. Netlify’s High-Performance Edge network has improved significantly since 2024, but independent testing still shows higher TTFB variance in South Asian and African regions compared to Cloudflare’s dense PoP coverage.
Measuring what matters
- LCP (Largest Contentful Paint): Test from multiple geographies using WebPageTest, not just your local machine. A site loading in 800ms from Frankfurt may take 2.4s from Dhaka due to cache topology.
- Cache hit ratio: Monitor via platform analytics after 7 days. Cloudflare Pages typically achieves >99% for immutable assets; others vary based on invalidation patterns.
- Cold start penalty: Deploy a new version and measure first-request latency from three continents. True edge platforms show consistent sub-100ms responses; origin-dependent CDNs spike to 500ms+.
What are the real free tier limits and hidden costs for each platform?
Free tiers attract teams, but production budgets break on overages. Understanding the actual constraints prevents costly mid-project migrations. If you are already managing cloud spend, apply the same scrutiny here as you would when working to reduce your AWS bill with proven cost optimization tactics.
| Feature | Cloudflare Pages | Netlify | Vercel |
|---|---|---|---|
| Bandwidth | Unlimited | 100 GB/month | 100 GB/month |
| Build minutes | 500/month (free), unlimited paid | 300/month | 6,000/month (fair use) |
| Serverless function invocations | 100K/day (Workers Free) | 125K/month | 100 GB-hours execution |
| Custom domains | Unlimited | Unlimited | Unlimited |
| Team members (free) | Up to 5 | Up to 5 | Hobby only (no team) |
| Overage pricing model | $5/mo for Workers Paid (unlimited) | $19/mo Pro + usage-based | $20/mo Pro + usage-based |
The critical distinction is bandwidth. Cloudflare’s unlimited policy means a viral post or DDoS attempt won’t trigger surprise invoices. Netlify and Vercel charge $0.15–$0.20 per GB over the limit. I’ve seen Nepali e-commerce sites hit 300GB during Dashain sales and face $40+ overages on platforms with caps. For high-traffic editorial or commerce, this single factor often decides the evaluation.
Build minute limits matter less for optimized pipelines but bite during monorepo migrations or framework upgrades. Vercel’s generous allowance accommodates heavy CI workloads, while Netlify’s 300-minute cap requires external CI for large projects. Cloudflare’s 500-minute free tier suffices for most teams, and their paid plan removes the constraint entirely without per-minute surcharges.
How do build systems and framework support differ in practice?
Framework compatibility determines developer velocity. Each platform has made strategic bets that create friction outside their sweet spot.
Vercel: Next.js native advantage
Vercel maintains Next.js, so features like Image Optimization, Middleware, and Incremental Static Regeneration work without configuration. Other platforms support Next.js but lag 2–4 weeks on new releases and require adapter packages that occasionally break. If your team lives in the Next.js ecosystem, this integration saves measurable debugging time.
Cloudflare Pages: Framework agnostic strength
Cloudflare treats all frameworks equally. Astro, SvelteKit, Remix, Hugo, and plain HTML receive identical optimization. Their wrangler CLI enables local development parity that matches production exactly. For teams running multiple frameworks across projects or avoiding React dependency, this neutrality prevents platform-induced rewrites.
Netlify: Mature tooling beyond builds
Netlify Forms, Identity, and Blobs provide backend capabilities without separate services. For marketing sites needing lead capture or gated content, this reduces integration overhead. However, these features create lock-in; extracting form submissions or user data later requires migration effort. Evaluate whether you need platform-native solutions or prefer portable alternatives like Supabase or Formspree.
When should you choose each platform based on real-world constraints?
Theoretical comparisons fail when organizational context intervenes. These patterns emerge from actual deployments across startups, agencies, and enterprises.
- Choose Cloudflare Pages when: Bandwidth predictability matters, your audience spans emerging markets with variable connectivity, you run non-React frameworks, or you already use Cloudflare for DNS/WAF. The unified dashboard simplifies security posture management alongside hosting.
- Choose Vercel when: Your product is a Next.js application with heavy server component usage, your team values preview deployments and comment integrations for design review, or you need instant rollbacks tied to Git commits. Accept the premium as a productivity tax.
- Choose Netlify when: Enterprise compliance requirements demand SOC 2 Type II reports available upfront, your marketing team needs self-service form management without engineering tickets, or you require split testing and personalization at the edge without custom code.
For teams in Nepal specifically, Cloudflare’s local PoP provides tangible latency benefits over platforms routing through Singapore or Mumbai. Combined with unlimited bandwidth, this makes it the pragmatic default unless framework-specific needs override geographic advantages. Always validate with real-user monitoring after deployment rather than relying solely on synthetic tests.
How do you migrate safely between platforms without downtime?
Migrations fail when teams treat them as cutover events rather than parallel validation periods. Follow this sequence regardless of source or destination:
- Dual-deploy for 7 days: Push to both platforms simultaneously via CI. Use a staging domain on the new provider to validate build output, asset paths, and environment variables against production.
- Audit redirect rules: Export existing redirects and verify syntax translation. Netlify’s
_redirectsdiffers from Cloudflare’s_routes.jsonand Vercel’svercel.json. Missing redirects destroy SEO equity. - Validate SSL provisioning: Confirm certificate issuance completes before DNS switch. Cloudflare issues certs in seconds; others may take minutes to hours depending on DNS propagation state.
- Switch DNS with low TTL: Reduce TTL to 60 seconds 24 hours before migration. After switching, monitor error rates and latency for 48 hours before decommissioning the old platform.
- Preserve build cache: Export any cached dependencies or artifacts if your new platform doesn’t share cache layers. Cold builds post-migration can mask configuration issues.
This discipline applies whether you are moving from shared hosting or between Jamstack providers. The principles mirror those used when migrating a website from shared hosting to the cloud: validate in parallel, cut over deliberately, and monitor obsessively during transition.
Making the final call for your static site hosting
The evaluation of Cloudflare Pages vs Netlify vs Vercel for static sites ultimately hinges on your specific constraints rather than generic superiority. Cloudflare Pages wins on cost predictability and global edge density for pure static workloads. Vercel justifies its premium for Next.js-centric product teams. Netlify serves organizations valuing integrated backend primitives and enterprise compliance documentation.
Run a two-week proof of concept with your actual codebase and traffic patterns before committing. Synthetic benchmarks lie; your users’ experience tells the truth. If you need help designing an evaluation framework or auditing your current hosting spend against real usage patterns, reach out to discuss your infrastructure. The right choice now prevents expensive corrections later.
