Skip to content
Brief Business Efficiency ·

Cloudflare adds spending caps that pause Workers and Durable Objects

The beta lets pay-as-you-go customers set limits and alerts, and pauses paid usage at the limit.

In brief
  • Cloudflare launched Spend Management in beta for pay-as-you-go customers. It starts with Workers and Durable Objects.
  • A cap is applied with a delay, because spend is measured first. Static assets keep loading when a Worker is capped.

Cloudflare said on November 13 that Spend Management is in beta for pay-as-you-go customers, starting with Workers and Durable Objects. Customers set a spending limit, alert levels and an email address for notices. At the limit, Cloudflare pauses the product. Settings work in the dashboard, the cf command-line tool or a REST API.

Cloudflare said usage is gathered in short windows, then priced after the plan's included allowance. A policy service then sends the cap to servers worldwide, which enforce it from local data, so requests never wait on billing. Costs show in the dashboard within 10 minutes. A capped Worker rejects new billable runs, including Cron Triggers and Queue consumers, but static assets still load. A billing cycle generally starts on the day the paid plan begins; an October 10 start ends November 10. Other products have no dates yet.

Cloudflare says AI Gateway already offers per-user and per-model budgets for AI requests routed through the gateway; it suggests using the two together. For budget owners, this is a delayed brake on two products, not a full guarantee. Ask which products stay uncapped and who is alerted when a service pauses.

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: Cloudflare.