# Cloudflare adds spending limits that pause Workers and Durable Objects when a budget is reached

> Spend Management, in Beta for pay-as-you-go accounts, lets developers set per-product caps and email alerts from the dashboard, the API or the cf CLI. Enforcement is asynchronous, so spend can overshoot a limit.

Source: Promptea — https://www.promptea.me/en/blog/cloudflare-spend-management-workers-durable-objects · Language: English · Last updated: 2026-11-14

Published: 2026-11-14 · Event date: 2026-11-13 · Category: cloud · Author: Promptea Editorial

**Summary:** Cloudflare launched Spend Management in Beta on November 13: opt-in spending limits and email alerts for Workers and Durable Objects, configurable in the dashboard, REST API and cf CLI. When a limit is hit, billable operations pause until the limit changes or the billing period ends. More products are promised but not named.

Cloudflare introduced Spend Management on November 13, 2026: opt-in spending limits and email alerts for its developer platform, starting with Workers and Durable Objects. The company announced it on its blog and in its developer changelog, and published documentation the same day. It is in Beta and, according to Cloudflare, available to any pay-as-you-go (PayGo) customer. All three sources cited here are Cloudflare's own; there is no independent coverage yet.

Cloudflare says spend controls have been among the most requested features on its developer platform. Until now, paid plans had usage notifications and budget alerts, which inform but do not stop usage. In the blog post's words, "informing is not the same as controlling."

## What changes for people who build with it

Each product gets its own controls: a spending limit, a notification email and one or more alert thresholds. Limits apply across the account for the current subscription billing period, which Cloudflare notes starts when the paid subscription began, not on the first day of a calendar month. When a blocking limit is reached, Cloudflare pauses the product's supported operations; alerts alone notify without stopping anything.

- Configuration is available in the dashboard (Billing > Spend limits), through the REST API, where a limit or alert is called a spend policy, and through the cf CLI with commands such as cf billing spend-policies create.
- Amounts are set in US cents: in Cloudflare's documentation example, --threshold-cents 5000 sets a $50 limit, with --action usage_block to enforce it.
- In Workers, a cap pauses billable customer-code invocations, including Cron Triggers and Queue consumer invocations, while static assets keep being served, according to the blog post.
- Service resumes when the limit is raised above the current spend, the policy is disabled or deleted, or the next billing period starts.
- The dashboard shows current-cycle costs per product in what Cloudflare describes as near real time (under 10 minutes), plus an audit log of who changed a limit and when.

Cloudflare positions the feature alongside AI Gateway spend limits, which already support per-user and per-model budgets for Workers AI and other AI providers on requests routed through a gateway. Together they cover compute and inference costs, but they remain separate controls.

## What is not covered yet

Enforcement is not instantaneous. The changelog says usage reporting and blocking take time, so recorded spend can exceed a limit. The blog explains that caps are computed outside the request path and propagated asynchronously to Cloudflare's network, and says the company hopes to shorten the gap to under a minute over time.

Only Workers and Durable Objects are covered. Cloudflare says other products will follow "soon" without naming them or giving dates. It also describes plans, not yet shipped, for budgets per application and per agent task, using tags that would carry spend attribution across products. The company has not said when Spend Management will leave Beta.

## Key takeaways

- Spend Management is in Beta for PayGo customers, covering Workers and Durable Objects only.
- Limits are per product and per billing period, set in US cents, with optional email alert thresholds.
- Cloudflare says recorded spend can exceed a limit because reporting and blocking take time; dashboard costs update in under 10 minutes.

## Why this matters

- Runaway usage from a bug or an AI agent stuck in a loop can now be stopped by the platform on Workers and Durable Objects, instead of only triggering an email.
- Combined with AI Gateway spend limits, teams can put ceilings on both inference and compute costs on Cloudflare, though the controls are configured separately.
- Because limits are a spend policy in the API and the cf CLI, they can be set from scripts, infrastructure code or a coding agent rather than only by hand.

## Sources

- [Introducing Spend Management: Spending limits and alerts for Cloudflare](https://blog.cloudflare.com/spend-management/) — Cloudflare (primary source), accessed 2026-11-13
- [Set spending limits for Workers and Durable Objects (Changelog)](https://developers.cloudflare.com/changelog/post/2026-11-13-spend-management/) — Cloudflare (primary source), accessed 2026-11-13
- [Spend management (Billing documentation)](https://developers.cloudflare.com/billing/manage/spend-management/) — Cloudflare (primary source), accessed 2026-11-13

*Researched with AI assistance and verified against primary sources before publishing. Every claim links to where it came from.*
