Cloudflare Adds Spending Limits for Workers

On November 13, 2026, Cloudflare introduced Spend Management, a beta feature that lets you set a spending cap and alerts for Workers and Durable Objects. It is open to any pay-as-you-go customer. When spend hits the cap, Cloudflare stops that product until you raise the limit or a new billing cycle starts.

What we know

What it covers today: Workers and Durable Objects. Cloudflare says other products will follow "soon". AI Gateway keeps its own separate spend limits and budgets.
What happens at the cap: a blocking policy kicks in and new invocations of that product are rejected. On Workers, Cron Triggers and Queue consumers also pause, but static assets keep being served, per the company.
How to turn it back on: raise the limit above the cycle's accumulated spend, disable or delete the blocking policy, or wait for the next billing cycle.
The cycle isn't the calendar month: it generally starts on the day your paid subscription began. Cloudflare's example: a subscription that started October 10 runs from October 10 to November 10.
It isn't instant: the company says enforcement happens in near real time, under 10 minutes, and it hopes to bring that under a minute.
Where to find it: in the dashboard under Manage Account, Billing, Spend limits. It can also be set through the cf CLI and the REST API. The dashboard shows cycle spend and keeps an audit log of who changed each limit.
Who can use it: any pay-as-you-go (PayGo) customer, per the announcement. The post does not say whether Enterprise plans are included.

What changes and what doesn't

What changes: a site or API built on Workers can now have a hard ceiling on its bill. Budget alerts already existed on paid plans, but an alert is not a brake: a loop in your code, a bot spike or an AI agent calling nonstop kept adding up until the end of the cycle.

What doesn't: Workers pricing and plan allowances stay the same. There is no cap yet for other Cloudflare products, and budgets per application or per agent are something Cloudflare says it is exploring, with no date. And the cap is not exact: with up to 10 minutes of delay, spend can run a bit past the limit before the block lands.

How to tell if you're affected

Check whether you pay for Workers. If Cloudflare only handles your DNS or free CDN, this doesn't touch you. If you run Workers, Pages Functions or Durable Objects on pay-as-you-go, it does.
Split static from dynamic. At the cap, static pages and files keep loading, but forms, logins, your API or on-site search running on Workers will stop. List what would go dark.
Set alerts before the block. Add one or two notifications (say, at half and three-quarters of the cap) to an inbox someone actually reads. The block is the last safety net, not the warning.
Size the cap to your real cycle. Find the day your billing cycle starts and look at the last few months of spend. A cap that's too tight can take your site down during a campaign or a legitimate traffic spike.
Check who is calling your Worker. If spend rises while human visits don't, look at bot and AI agent traffic before raising the cap. Paying more doesn't fix a loop.
Know how to switch it back on. Note where the limit lives (Billing, Spend limits) and who has permission to change it. Every change is logged.

Because it's in beta, behavior may change; it's worth trying it first on a Worker that isn't critical.

Sources

Updates: if Cloudflare takes the feature out of beta or adds products, it will be added here with the link.