Cloudflare Spend Management beta: set limits and pause Workers

Cloudflare has introduced Spend Management in Beta for pay-as-you-go customers, starting with Workers and Durable Objects, so teams can set spending thresholds, receive alerts, and have Cloudflare pause billable activity when a limit is hit, according to the Cloudflare Blog. The feature pairs with existing AI Gateway budgets and is available from the dashboard, the cf CLI, or the REST API.

What Spend Management does and where to find it

According to the Cloudflare Blog, you enable Spend Management from the dashboard under Manage Account > Billing > Spend limits, and you can turn controls on for the products you want to manage. When you enable a control you define a spending limit, add one or more alert thresholds, and specify a recipient email for notifications. The dashboard shows per-product billing-cycle costs in near real time, described as updates under 10 minutes, and an overview panel that highlights which products have thresholds and limits set.

Cloudflare also exposes the capability as an API and in the cf CLI. The blog shows a curl example that posts a spend-policy, and lists cf commands such as cf billing spend-policies list, create, get, update, delete, and audit list. That makes it practical to automate policy creation or include spend checks in deployment workflows, Cloudflare says.

You can use Spend Management together with AI Gateway spend limits: Cloudflare notes AI Gateway already supports per-user and per-model budgets for Workers AI and other AI providers, applied to requests routed through the gateway.

How limits behave in practice

Cloudflare describes three important behaviors to expect. First, when an evaluated spend reaches a configured threshold, the system sends notification emails to the specified recipients. Second, when the hard limit is reached, a blocking policy is enforced: "Once a cap is enforced, new invocations of that product are rejected," according to the Cloudflare Blog. Third, the blocking applies only to customer-code invocations that incur costs. For Workers, Cloudflare says Cron Triggers and Queue consumer invocations are paused while static assets continue to be served.

The billing cycle used for limits follows the paid subscription start date, not the calendar month. The dashboard also provides an audit log so you can see who changed a limit and when, or when a cap was reached. To resume service after a block, Cloudflare lists three options: raise the limit above the current cycle's accumulated spend, disable or delete the blocking policy, or wait until the next billing cycle when the block expires.

Cloudflare spend management: how it works behind the scenes

Cloudflare explains that building spend controls at its scale required new systems and changes across teams. Usage is metered with a two-stage pipeline that aggregates events close to the source before feeding them to the pricing engines. The first stage combines raw events into roughly one-minute windows. A second stage merges those partial aggregates over about five-minute windows and archives consolidated aggregates for analytics and reconciliation.

Aggregated measurements then enter a Usage Engine that translates them into standardized usage records and maintains account-partitioned state so each account's usage and subscription information are processed together. Partitions keep local state and a durable write-ahead logging changelog to reduce cross-partition coordination, preserve consistency, support parallel processing, and enable recovery.

The Rating Engine is the component that turns usage into monetary value by combining usage records, subscription information, and pricing rules. Cloudflare describes handling cases where usage and subscription updates arrive out of order by retaining unpriced usage as pending until the required subscription data is available, rather than treating it as free.

What to do now (practical steps)

• Review which Cloudflare products you use that incur variable costs, starting with Workers and Durable Objects, and decide where caps would reduce risk.
• In the dashboard, go to Manage Account > Billing > Spend limits, enable the product, define a spending limit, add alert thresholds, and set a notification email, as described by Cloudflare.
• If you automate deployments or billing checks, use the API or cf CLI commands such as cf billing spend-policies create and cf billing spend-policies audit list to script policy management.
• Check the audit log after you configure policies so you can track changes and who made them.
• Plan how the system will behave when a cap is enforced: blocked invocations are rejected for billable customer code, but static assets keep serving; have a response plan to raise limits or remove policies if needed.

Where this matters for small teams and public sector projects

If you run pay-as-you-go projects on Cloudflare, these controls reduce the chance of surprise charges by pausing billable activity when a limit is hit and by providing near real-time visibility into spend per product. For AI features, the blog highlights that Spend Management complements AI Gateway per-user and per-model budgets, which can help control inference costs when routing requests through Workers.

For hands-on help with Cloudflare configurations or to review how spend limits should fit into your hosting and form-processing workflows, consider reaching out: Running WordPress or Formidable Forms? Get help from a Formidable Masterminds developer.

If you want details straight from the source, see Cloudflare's announcement on their blog for the full technical write-up and examples.