A surprise traffic spike should not become a surprise cloud bill. Cloudflare introduced Spend Management in beta on November 13, 2026, letting eligible customers set spending caps that can actually pause billable workloads.
What changed?
Traditional budget alerts tell you when costs climb. Cloudflare’s new controls can also block further billable invocations once a configured limit is reached. The beta initially covers Workers and Durable Objects for pay-as-you-go customers.
- Set a spending cap for a supported product.
- Add email alerts at chosen thresholds.
- See current-cycle spending in the dashboard, generally with less than ten minutes of delay.
- Review an audit log of policy changes and limit events.
How to set a limit
Open the Cloudflare dashboard and go to Manage Account → Billing → Spend limits. Enable the relevant product, choose a cap, and optionally configure an alert recipient and thresholds.
For automation, Cloudflare also documents the cf CLI. This command lists existing spend policies; it is taken from Cloudflare’s announcement, not independently tested here:
cf billing spend-policies listThe REST API also supports creating and managing spend policies. For example, Cloudflare’s documented API uses threshold_cents and an usage_block action; a value of 10000 represents a $100 threshold in cents. Treat example amounts as configuration choices, not a universal recommended budget.
The important catch
A hard cap can interrupt your app. When enforcement kicks in, new billable product invocations are rejected. Workers Cron Triggers and Queue consumers can pause, while static assets can continue serving. That may protect your budget but break scheduled jobs or dynamic requests.
Cloudflare says you can resume by increasing the cap above current-cycle spending, disabling the blocking policy, or waiting for the next billing cycle. The billing cycle follows your paid subscription anniversary, not necessarily the first day of the month.
Practical takeaway: Start with alerts, understand which workloads would stop, and then enable blocking for services where predictable costs matter more than uninterrupted execution. This beta does not yet cover every Cloudflare product.