Cloudflare spending caps pause work after asynchronous metering
Cloudflare’s Spend Management beta lets pay-as-you-go customers configure alerts and spending limits for Workers and Durable Objects. Once enforced, a cap rejects new billable invocations while static assets continue serving. Metering, pricing and global enforcement happen asynchronously, with a near-real-time pipeline described as under ten minutes, so this is not an exact per-request spending ceiling.
Cloudflare · Nov 13, 2026
Why it matters
Cost controls need an explicit decision about whether stopping customer work is preferable to continuing to accrue charges.
More context
Configure supported products through Billing → Spend limits, the CLI or REST API. Try a test workload and review how paused invocations recover. Limits follow the subscription’s billing cycle; resume by raising or disabling the cap, or waiting for the next cycle.
Keep in mind
Beta, initially limited to two products. Global propagation and metering introduce delay, so accumulated spend can exceed a threshold before blocking takes effect. Per-application budgets across products remain planned work.
Original read