twimco.Let’s talk ↗︎
Menu
Field notes / Product & engineering

Cloudflare now lets you cap Workers and Durable Objects spend. A cap that works can also switch your site off

Bill shock on Cloudflare has a switch now. Press it on the wrong account and your checkout stops answering. Three questions decide whether you want a hard limit or just an email.

Editorial engraving of a grower with a clipboard beside a brass valve and gauge on a sunny rooftop farm while a colleague looks on and others water the beds.

On November 13, 2026, Cloudflare added spending limits and email alerts for Workers and Durable Objects. A limit applies to the whole product across the account, and when reached Cloudflare blocks new invocations until you raise it, turn it off or the billing period renews. It doesn't guarantee a maximum invoice. Alerts fire at 80 and 100 percent and don't stop anything. Cap experiments on their own account; alert on production.

What Cloudflare added

On November 13, 2026, Cloudflare announced spending limits for Workers and Durable Objects. You can set a dollar limit that blocks the product when spend reaches it, or a threshold that only sends an email while everything keeps running, or both. Cloudflare says support for more products is coming.

It's a response to something developers have asked for. Cloudflare's own blog post says informing isn't the same as controlling: the budget alerts it already had told you about a bill, and didn't stop one. The new feature, in beta for pay-as-you-go customers, is meant to stop it.

What a limit does, and one quiet trap

Three details in the documentation matter more than the headline.

First, the limit is across the whole product on the account. A Workers limit doesn't cover Durable Objects, Workers AI, Workers KV or R2, and Cloudflare says limits can't target one Worker, one namespace or one billing metric. If you set $50 for Workers, that's $50 for every Worker on the account together, counting requests and CPU time after included usage.

Second, when the limit is reached, Cloudflare blocks the product's supported operations. New Worker invocations are rejected, and its docs warn that an application depending on a paused Worker can fail. The blog adds that Cron Triggers and Queue consumers are paused while static assets keep being served.

Third, it isn't an invoice cap. Cloudflare says plainly that usage reporting and blocking take time, so spend can pass the limit, some charges continue during a pause, and stored data keeps costing money while Durable Objects are paused. Your invoice is the final record. The limit also doesn't cover your Workers Paid subscription fee.

Resuming is simple. Raise the limit above current spend, turn it off, or remove it, and it takes a few minutes to apply. Otherwise it expires when the next billing period starts, which follows your subscription date, not the first of the month. A subscription renewing on the 15th resets on the 15th.

Email alerts fire at 80 and 100 percent of the threshold. If spend jumps past both between checks, you may only get the 100 percent email. And limits created in the dashboard don't automatically have an email recipient. Cloudflare's docs say you must update the policy with a notification address to receive them, though its changelog describes choosing a notification email when you set one up. Whichever way you create it, open the policy afterwards and confirm there's an address on it. An alert nobody receives is worse than none, because it feels like coverage.

It also helps to know what the limit doesn't see. Cloudflare says estimated charges in the dashboard are what a limit counts, and your invoice is the final record. The overview shows each product's recorded spend, alert thresholds and pause status, but "Limit reached" doesn't confirm blocking has finished spreading, and "On" only means the policy is enabled, not that the product is running. Don't read those labels as proof that your application is up or down. Check the application.

How the work moves

What happens at a $50 Workers limit

  1. $40

    Near limit: 80 percent of $50; an email goes out if you set one.

  2. $50 or more

    Limit reached.

  3. Blocking spreads

    New invocations are rejected once the block reaches the network.

  4. Resume

    Raise or remove the limit, or wait for the next billing period.

Source: Cloudflare's own worked example, simplified; blocking is not instant, so spend can pass the limit.
A limit that works is also an off switch for your site.

Three questions

A limit that works is also an off switch for your site. Before you press anything, answer three questions.

What would stopping cost us? If the thing on Workers is a checkout, a booking form, or an API your mobile app calls, a block turns a surprise bill into an outage on your busiest day. If it's a prototype, a block costs nothing. Be honest about which one the account holds.

Who would notice, and how fast? An alert only helps if a person with authority reads it and can act within the hour. If that isn't true on weekends, a limit might be the only control that works at 3 a.m. Put a name on the email address, not a shared inbox that nobody opens.

Can we separate the two? Since a limit applies to the entire product across the account, the clean fix is structural. Keep experiments, side projects and test code on one account with a hard limit. Keep production on another with alerts and, at most, a very high limit. This is our suggestion, not Cloudflare's, but it follows from how the limits are scoped.

A reasonable setup

For a small business with production on Workers: set alerts at amounts that would surprise you, make sure the address is monitored, and write the one-line response down. Something like "if the alert fires, check the usage page, look for a loop or a bot, and call this person." Add a limit well above your worst expected month, as a last resort, and note in your runbook what that block will switch off.

For experiments: a low limit. The point is that a mistake in a test loop costs a few dollars and not a month's budget.

Then review it. Spend patterns change, and a limit set in January can quietly become a problem in November.

Decision guide

Limit or alert

ConsiderationSpending limitEmail alert
At the thresholdCloudflare blocks the product's supported operationsCloudflare emails you; everything keeps running
Best forExperiments, side projects, test accountsCheckout, forms, anything customers wait on
RiskYour application stops answeringNobody reads the email
GuaranteeNone on the invoice totalNone, and it doesn't claim one
Decision framework, our suggestion, based on what Cloudflare says each control does.

Setting it up without surprises

Whoever sets this up needs permission to edit billing settings, so decide who that is before an emergency. Cloudflare keeps an audit log of changes to your limits, with who changed what and when, so a limit that someone raised at midnight is visible later. You can also set limits from the cf command-line tool, and Cloudflare's example for a $50 Workers limit gives the amount in cents, so a mistyped zero is easy. Read the number back before you save it.

A newly saved limit counts usage already recorded in the current period. Cloudflare's own example says saving a $50 limit when the product has already accrued $60 can trigger a pause as soon as the policy is evaluated. So don't set a low limit on a live account in the middle of a billing cycle without checking the current spend first.

Where we come in

When we build applications on a platform like this, running cost is part of the design, with the alerts, the limits and the runbook agreed before launch, not after the first strange bill. That's part of our web applications work. If you've got something running on Workers and nobody's sure what it would cost on a bad day, talk to us.

Related work: Spin:Market

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Spin:Market ↗︎