Static site with a Worker: about $6.80 a month on Workers Paid
A month that looks like the numbers below comes to roughly $6.80, base fee included. The meter that runs out first is Workers requests, at 150% of its included usage. Prices are the public list as of 2026-09-15; the real invoice is the only truth.
Adjust the numbers → ← Usage Guard
Estimated bill
Total per month $6.80
Workers Paid base fee $5.00
Meter closest to (or past) its included usage: Workers requests — 15M / 10M (150%)
Overages
- Workers requests: 5M → $1.50
- Workers CPU time (ms): 15M → $0.30
Usage assumed for the month
- Workers requests: 15M
- Workers CPU time (ms): 45M
- KV keys read: 8M
What this setup looks like
A docs or marketing site on Workers Static Assets, with one Worker rendering a handful of dynamic routes on the server. Requests for static files are free and never appear on this page. What bills is every request that reaches the Worker, plus the CPU time it burns. I assumed 15 million Worker requests at 3 ms each and a KV read on about half of them.
Why Workers requests runs out first
Workers Paid includes 10M requests a month. This site is at 150% of that, and CPU time sits at exactly the same multiple of its own allowance, so requests only win because they come first on the invoice. Either way the overage is a couple of dollars. On a site like this the base fee is most of the bill, and that is the boring, correct outcome.
What to watch in GraphQL Analytics
Query workersInvocationsAdaptive grouped by script name and day. If requests double while CPU stays flat, a crawler found a route without a cache header. If CPU climbs on its own, one route got slower. The collector I run compares each day against its trailing 7-day baseline, not against yesterday.
Prices and included usage copied from Cloudflare's public pricing pages on 2026-09-15. Approximate: some meters round up to the next unit, Workers AI and bandwidth are not included, and the real invoice is the only truth.
Other typical bills
Also exploring
Paying for Workers and wary of a surprise invoice? See Usage Guard — per-metric spike alerts and an optional stop switch.
Routing support@ through Cloudflare and reading it in Gmail? See Routed Inbox — a small shared inbox on Email Routing, no seat pricing.
Managing Cloudflare for many clients? See Zone Audit — config drift and baseline checks across accounts.