Workers usage
Track requests and CPU time for selected Worker scripts without changing their application code.
Cloudflare cost controls
Set limits before usage becomes a surprise.
Monitor the Workers and Durable Objects you select, then rehearse explicit traffic controls against stored evidence before automated containment is enabled.
Product
Coverage for the usage you choose to watch.
Durable Objects usage
Monitor selected namespaces across duration and supported storage operation signals.
Reports and coverage
Review observations, incident history, and whether available analytics fully cover each configured limit.
How it works
Control stays explicit at every step.
-
01
Connect
Authorize a Cloudflare account with the scopes needed for the coverage you choose.
-
02
Select
Choose the Worker scripts and Durable Object namespaces FlareBudget should monitor.
-
03
Set limits
Define usage or estimated-dollar thresholds and review available dataset coverage.
-
04
Review controls
Inspect the exact reversible traffic actions in dry-run; automated containment remains unavailable until the production canary passes.
Safety boundary
Traffic controls are not a hard spending cap
Automated containment is available for explicitly armed limits after successful production canary verification. Containment can reduce selected ingress, but alarms, active WebSockets and invocations, internal callers, and storage may continue. FlareBudget cannot guarantee that all Cloudflare charges stop.
Start with visibility