Why workerfuse ignores Cloudflare's included usage
We use list prices and ignore included allowances so a runaway trips earlier. The estimate isn't your invoice, and here's why it's built that way.
We price the usage we can see high, on purpose. That doesn't make it a guaranteed upper bound (analytics can undercount, and we don't cover every charge), but it leans high wherever we get to choose.
Workers Paid includes a bunch of usage in the $5 base: requests, CPU time, DO duration, D1 rows, and so on. We ignore all of that and price from zero at list price (one known gap: R2 uses Standard rates, so Infrequent Access operations get underpriced). A few reasons:
- Allowances differ by product. Most are monthly and shared across the account, Workers AI's is daily. Either way, a guard looking at one script for one hour can't know how much is left.
- A fast runaway can blow through the allowance in hours. Pricing from zero just means the pause comes a bit earlier.
- Getting it wrong in the cheap direction costs you money. Getting it wrong in the expensive direction costs you a false pause, which isn't free either (consumed alarms, terminated Workflows). I'll still take that one.
Same idea in a few other spots. Shared resources charge their full cost to every bound script. Workflow steps count sleeps and waits. Pipelines prices every ingested byte as if it were transformed. It all leans high.
The tradeoff is a false pause now and then. That's why the default limits ($0.25/hour, $2/day) are set with some room, and why there's a dry-run mode to see what would be paused before you turn it on.