Cloudflare Pages

What Cloudflare Pages actually is

Cloudflare Pages is a git-connected hosting platform for websites: push to GitHub or GitLab, and Pages builds your project and deploys it to Cloudflare's network, with a preview URL for every commit and production deploys on merge. Static assets are served straight from the edge, and dynamic behavior is added through Pages Functions, which run on the Workers runtime next to your content. Announced on December 17, 2020, it arrived as a direct answer to Netlify and Vercel, and in our view its strongest card is still the same one: the free tier hosts real projects without metering the things that hurt, namely bandwidth and requests.

The product's shape is simple on purpose. A Pages project watches a Git branch, runs your build command, and uploads the output as static assets. There is no server to provision, no Dockerfile to maintain, no build container to size. Framework detection covers the usual static generators and front-end frameworks — Hugo, Astro, Next.js in static-export mode, React, Vue and others — and when detection works you genuinely configure nothing. When it does not, you set a build command and an output directory and you are done. The whole loop from first connect to live site is minutes.

Pages Functions deserve specific attention because they define how far the platform goes. Functions live in a functions/ directory, are written as request handlers on the Workers runtime, and can bind to Workers KV, Durable Objects, D1 and R2. Requests to Functions count against your Workers plan quota rather than a separate Pages meter. This is where Pages stops being static hosting and becomes a small full-stack platform — but it is a small one. If your application needs long-running processes, arbitrary binaries, or non-Workers runtimes, Pages is not the right shape, and we would rather say that early than let you discover it at migration time.

Pricing: what you really pay

Pages is included in Cloudflare's application plans, and the plan ladder is what governs it. Free costs $0 and includes unlimited sites, unlimited seats, unlimited requests and unlimited bandwidth. Pro is $20 per month billed annually ($240 per year) or $25 billed monthly. Business is $200 per month billed annually ($2,400 per year) or $250 billed monthly. Enterprise terms are custom. The free tier is the remarkable part: there is no bandwidth cap to model and no per-seat charge for your team, which is exactly where comparable platforms grow their invoices.

What the paid tiers actually buy you is build capacity, not delivery. On the Free plan you get 500 builds per month with one build running at a time. Pro raises that to 5,000 builds per month and five concurrent builds; Business goes to 20,000 builds and twenty concurrent. Builds time out after twenty minutes on every plan. Custom domains scale from 100 per project on Free to 250 on Pro and 500 on Business. Sites on the Free plan can contain up to 20,000 files, raised to 100,000 on paid plans, with a 25 MiB per-file ceiling everywhere. Accounts are limited to 100 projects.

Read that list twice before paying. A documentation site with an active team can hit 500 builds a month — CI churn is the real free-tier limiter. But a popular site with heavy traffic pays nothing extra no matter what it serves. That is the inversion of the usual hosting pricing model, and it is why we rate the value highly. Dynamic logic is metered separately through Workers: the Workers Free plan allows 100,000 requests per day at 10 ms of CPU per invocation, and Workers Paid starts at $5 per month with 10 million requests and 30 million CPU milliseconds included, then $0.30 per million requests and $0.02 per million CPU milliseconds. Static asset requests are free and unlimited.

Performance & infrastructure

Deploys land on the same 330-plus city network that fronts Cloudflare's CDN, so your files are served from a facility close to most visitors with no CDN configuration of your own. TLS certificates are issued and renewed automatically, custom domains take a CNAME or nameserver setup, and IPv6 and HTTP/3 come with the platform. Preview deployments are unlimited even on Free, which we consider one of Pages' best workflow features: every pull request gets a shareable URL, and reviewers click a link instead of pulling a branch.

Build performance is the weak variable. Builds run on Cloudflare's shared build infrastructure, and during busy periods large projects can queue behind other people's builds. The concurrency numbers in the pricing section exist because of this — five concurrent builds on Pro is not a luxury, it is what a team with an active merge queue needs. If your build takes close to twenty minutes, you are already at the timeout ceiling and should consider trimming the pipeline rather than paying for concurrency.

On reliability, the platform inherits Cloudflare's operational track record and its concentration risk in equal measure. The asset layer is distributed and has no origin server to fail. The build and deploy control plane can have bad days, and when Cloudflare has a network incident your site is in it. The published uptime SLA follows the application plans: none on Free or Pro, 100 percent on Business with service credits, and Enterprise terms with 10x or 25x credits. As with the CDN, if the site is revenue-critical, the SLA starts at $200 per month billed annually.

Where it falls short

The platform boundary is the first limitation. Pages serves static files and Workers-runtime functions. There is no persistent server, no arbitrary background worker, no long-lived WebSocket server beyond what Durable Objects supports. Teams coming from a VPS or a container platform will find the mental model genuinely different, and porting an application means rewriting its dynamic parts against Workers APIs. That is not a flaw exactly — it is the trade that buys the zero-operations model — but it makes migration costs asymmetric. Moving to Pages is fast; moving off it involves reworking anything touching KV, D1 or Durable Objects.

Build limits bind before delivery limits do. Fifty builds a month is fine for a solo blog and nowhere near enough for a team of ten with CI. The 20,000-file cap on Free also bites image-heavy sites, and the 25 MiB per-file ceiling pushes large media toward R2 or another storage layer, which adds a second product to your bill and your mental model.

We would also call out observability. Pages analytics tell you about traffic; deep debugging of build failures or function behavior is thinner than what you get on platforms built around logs first. And Cloudflare's dashboard is a large surface — Pages, Workers, R2, Zero Trust — which is a mild tax on people who wanted a static host and got a connectivity platform.

Finally, framework lock-in deserves honesty. Next.js support is strong for static and increasingly for more via OpenNext-style adapters, but full server-side Next.js behavior is not identical to Vercel's. If your project leans hard on a framework's proprietary platform features, test the deployment before you promise stakeholders parity.

Who should pick this

Our pick in /category/managed-cloud for front-end teams, documentation sites, marketing sites and content projects that want global delivery without an operations budget. The free tier covers hobby projects completely and small production sites comfortably. Pro at $240 per year is the right call for teams that merge often; Business is for teams that need concurrency, higher build counts or a contractual SLA. If you are already using Cloudflare DNS or the CDN, the consolidation is real — one dashboard, one bill, one API.

We would not pick Pages for applications with heavy server-side compute, long-running jobs or non-JavaScript runtimes, and we would be cautious with framework features that depend on a specific vendor's platform. For object-heavy workloads, pair it with R2 and read our Cloudflare R2 review; for pure compute at the edge, our Cloudflare Workers review covers the runtime these Functions share.

Key takeaways

• Git-connected builds and deploys with unlimited preview URLs; static assets served from 330+ cities.
• Free tier: unlimited sites, seats, requests and bandwidth; 500 builds/month, one at a time, 20,000 files per site.
• Pro is $20 per month billed annually ($240/year) or $25 monthly (5,000 builds); Business $200 annually ($2,400/year) or $250 monthly (20,000 builds).
• Dynamic logic runs as Workers Functions, billed against Workers plans — Workers Paid starts at $5 per month.
• Build concurrency and the 20-minute build timeout are the real limits; bandwidth is not.
• Platform boundary is hard: no persistent servers or arbitrary runtimes, and moving off means reworking Workers-specific state.

Sources

• https://cloudflare.com/press/press-releases/2020/cloudflare-announces-cloudflare-pages
• https://developers.cloudflare.com/pages/platform/limits/
• https://www.cloudflare.com/plans/
• https://www.cloudflare.com/plans/faq/
• https://developers.cloudflare.com/workers/platform/pricing/
• https://www.cloudflare.com/network/
• https://www.cloudflare.com/en-gb/products/pages