Cloudflare Workers + Pages review
Cloudflare Workers + Pages is a strong pick for static sites and request-driven apps whose execution needs fit the platform's limits. Watch the billing boundary: static asset requests are free, but functions consume Workers allowances and paid usage can exceed the starting charge.
How we make money: Links may become affiliate links, but the code that computes our scores never receives commission data.
Score breakdown
Scores come from one formula for every app platform host, explained on our methodology page.
Plans and the true 3-year price
| Plan | vCPU / RAM / Disk | Monthly | Renews at | 3-year cost |
|---|---|---|---|---|
| Workers Free | Usage-based | $0 | $0 | $0 |
| Workers Paid | Usage-based | $5 | $5 | $180 |
| Workers Enterprise | Usage-based | See site | See site | See site |
Providers change prices often, and we regularly verify prices against their own pricing pages, though small differences from current prices are possible. Prices checked 10 Oct 2026. Excluding tax.
Who it's for
Pick it if
- You serve static sites and want free, unlimited static asset requests
- Your app fits a managed runtime without root or SSH access
- You want API, CLI and Terraform support for deployment automation
- You want to avoid egress and bandwidth charges
Skip it if
- You need root or SSH access to operate your app
- Your workload cannot fit the platform's execution limits
- You require contractual uptime coverage without an enterprise agreement
Reliability, SLA and policies
Our take
The strongest reason to choose Cloudflare Workers + Pages is the fit between static delivery and request-driven application code. Pages static asset requests are free and unlimited, with no egress or bandwidth charges. That makes it attractive for sites where most traffic serves files and only selected requests need application logic. Keep that distinction clear when estimating costs: Pages Functions consume Workers allowances. A site with extensive dynamic behaviour has a different cost profile from a static site, even when the deployments look similar.
Workers Paid starts at $5 a month and renews at $5, so an introductory discount expiring is not the pricing concern here. Usage is. Included request and CPU time allowances can be exceeded, and additional build minutes can also add charges. Treat the starting price as a minimum rather than a forecast of your bill. Estimate how often your code runs, how much execution time it consumes and how frequently you build. Check charges for any attached services before treating the Workers price as your whole application budget.
The operational trade is less server administration in exchange for adapting to the platform. API, CLI and Terraform support give you useful automation options, but they do not remove runtime constraints or make provider-specific integrations portable. Check dependencies and execution requirements before committing, especially for agents that need shell access or sustained processing. Compare Vercel and Netlify when framework deployment workflow drives your choice. Include Render, Railway, Fly.io and Heroku when evaluating where an existing application fits, with dependency compatibility and the work required to move it as explicit decision criteria.
Reliability needs a separate judgement from network reach. The Workers uptime commitment applies to enterprise customers, and its wording describes a service level objective backed by commercially reasonable efforts. Do not assume Workers Paid carries the same contractual protection. The public status page helps you investigate incidents, but your own monitoring still needs to establish whether your application works. Community, ticket, chat and phone support are listed; confirm the support entitlement attached to your agreement if escalation speed affects your business. For a small team, that distinction matters more than the breadth of the channel list.
We put our own websites behind Cloudflare for DNS and proxying. That gives us direct experience with Cloudflare in the traffic path to our sites. This experience covers DNS and proxying; it should not be read as a claim that we have tested Workers application execution or Pages deployment behaviour in production.
FAQ
Is Cloudflare Pages free for a static website?
Pages static asset requests are free and unlimited, with no egress or bandwidth charges. Builds, files and projects still have limits, and Pages Functions count toward Workers allowances.
What will I actually pay for Cloudflare Workers?
Workers Paid starts at $5 a month and renews at $5. Your bill can rise when requests, CPU time or build minutes exceed the included allowances, so estimate those separately.
Can I run an AI agent on Cloudflare Workers?
Workers can suit request-driven agent endpoints and tools when their dependencies and execution needs fit the runtime. If your agent requires root or SSH access, this platform does not meet that requirement.
Does Workers Paid include an uptime SLA?
The Workers SLA applies to enterprise customers, so you should not assume Workers Paid includes it. The enterprise commitment is stated as a service level objective with commercially reasonable efforts, with credits tied to Workers fees.
Should I choose Cloudflare Pages, Vercel or Netlify?
Choose Cloudflare Pages when free static delivery and integration with Workers match your application. Compare Vercel and Netlify against your framework, build workflow and dynamic request requirements before deciding; static hosting costs alone do not settle the choice.