Cloudflare adds spending limits that pause Workers at a cap
Cloudflare has launched Spend Management in beta for pay-as-you-go customers. You set a spending limit and Cloudflare pauses the product once it is reached, starting with Workers and Durable Objects.
By JetherVerse News

Cloudflare has released Spend Management in beta for pay-as-you-go customers. You set a spending limit on a product, and Cloudflare pauses the product once the limit is reached. The first products covered are Workers and Durable Objects.
Cloudflare says spend controls sit at the top of the requests it hears from developers, and it now counts more than 10 million developers on the platform. Budget alerts already existed on paid plans, but an alert only informs you. The new controls act. In the dashboard, under Manage Account, Billing and then Spend limits, you pick a product, set a limit, add an email address for notices and add one or more alert thresholds. When spend reaches the limit, new invocations of the product are rejected. Cloudflare pauses only the customer code invocations with a cost. Current costs for each product show in near real time, in under 10 minutes, and an audit log records who changed a limit and when a cap was hit. The same policies are open through the REST API and the cf command line tool. One detail to note is the billing cycle. It starts on the day your paid subscription began, so it does not follow the calendar month. Cloudflare also points to AI Gateway spend limits, which set per-user and per-model budgets for AI inference traffic.
A runaway loop, a traffic spike or a leaked API token used to produce a surprise bill before anyone noticed. A hard cap trades uptime for a ceiling on cost, so you choose the limit with care. Set it above your normal peak and below the level of spend your business cannot absorb, then place the alert thresholds lower so you hear about trouble first.
For Nigerian developers and small agencies paying in dollars while the naira moves against them, a predictable ceiling on a cloud bill is a practical feature. A client project hosted on Workers no longer needs someone watching usage graphs over a weekend.
If you run client projects on usage-based platforms, a spending cap is worth setting before you need it.
Source: Cloudflare Blog
Get the news in your inbox
The tech stories that matter from JetherVerse News, with the source on every one.

