Infrastructure · Hybrid · unit: thousands of requests
Cloudflare Workers pricing teardown: plan plus usage
Short answer
Workers Paid charges on request and CPU-time meters, while Workers Free has request limits; per-invocation CPU limits can stop runaway work.
Pricing mechanics
| Plan or rate | Position in ladder |
|---|---|
| Workers Free | Entry |
| Workers Paid | Top published step |
- What the docs describe
- Paid pricing has request and CPU meters; Free has request limits. Per-invocation CPU limits can control runaway work.
- Free or trial fence
- Workers Free has request limits.
- Overage or upgrade rule
- Workers Paid bills requests and CPU time above included amounts.
- Cap or spend control (usage cap)
- Per-invocation CPU limits act as a runaway-work control.
A feature or configuration fence (what a plan includes) is not the same as an abuse cap. We do not infer private costs, margins or unpublished limits.
Takeaway for founders
A per-request limit is a cost cap that never needs a billing decision. Model requests and CPU separately in production.
Load into simulator
Illustrative remix · amounts and costs are editable.
Fictional tiers inspired by the pattern above. It does not reproduce Cloudflare Workers's plans, invoices or margins. Fictional variable cost: $0.00012 per thousands of request. The remix uses a normalized request unit instead of separate request and CPU meters.
| Tier | Model | Price | Limit | Accounts |
|---|---|---|---|---|
| Sample entry | Flat / seat | $0 (free) | hard cap 100 thousands of requests | 200 |
| Sample growth | Hybrid | $6.00 base, 10,000 thousands of requests included, then $0.0004 each | hard cap 100,000 thousands of requests | 70 |
| Sample scale | Hybrid | $24.00 base, 50,000 thousands of requests included, then $0.0004 each | hard cap 500,000 thousands of requests | 15 |
Related guide: Hybrid vs. usage-based billing · All teardowns