# Why workerfuse ignores Cloudflare's included usage · workerfuse

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:

1.  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.
2.  A fast runaway can blow through the allowance in hours. Pricing from zero just means the pause comes a bit earlier.
3.  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.

## Pause the runaway Worker. Keep the rest running.

workerfuse checks your Cloudflare spend every five minutes and pauses any Worker over its limit.

[Start free trial](/signup)

## Keep reading

[

Spend limitsNovember 13, 2026

### Cloudflare spending limits vs pausing one Worker

Cloudflare now has spending limits for Workers and Durable Objects. They're account-wide and block the whole product. Here's how that compares to pausing only the runaway Worker.

](/blog/cloudflare-spending-limit)[

Case studiesNovember 13, 2026

### Cloudflare billing horror stories: four runaway bills from 2026

A $34,895 alarm loop, a $10,811 bill from an abandoned side project, a ~$36,000 queue loop, and $4,586 of D1 writes. What broke, how long it ran, and what Cloudflare did about it.

](/blog/cloudflare-billing-horror-stories)[

Durable ObjectsNovember 13, 2026

### How a Durable Objects alarm loop runs up your Cloudflare bill

A Durable Object alarm that keeps rescheduling itself racks up requests, storage writes and duration. What that costs at list price, and how to stop it.

](/blog/durable-objects-alarm-loop)
