Tools Nov 14, 2026 · Originally published Nov 13

Cloudflare launches Spend Management in beta: spending caps for Workers and Durable Objects that pause the product when reached

From warning you about overspend to stopping it. How it takes effect, what gets paused, and how it fits with AI Gateway budgets.

Image: Cloudflare blog
Primary source Cloudflare blog · blog.cloudflare.com Read the original ↗

// Key points

  • Available to all pay-as-you-go customers, starting with Workers and Durable Objects with more products to follow; set a limit, a notification email and multiple alert thresholds.
  • When the limit is hit a blocking policy pauses only cost-incurring customer-code invocations, such as Workers Cron Triggers and Queue consumers, while static assets keep serving.
  • The dashboard shows current-cycle spend per product in near real time (under 10 minutes) with an audit log; it is also configurable through the cf CLI and REST API.
  • It pairs with AI Gateway's existing per-user and per-model budgets to cap both compute and AI inference costs.

Builder's takeFor indie developers, an agent loop running away overnight and burning a month's budget is a real risk, and a hard cap beats an alert. I would cap unattended parts like cron jobs and queue consumers first, at two to three times normal spend. Like yesterday's AWS guide to capping Bedrock spend per identity, cost control is becoming a platform default.

Every Monday, the week in AI in one email

Every Monday morning: the 6 AI stories that mattered most in the past seven days, with my take, in your inbox.

Your email is only used to send the weekly and is never shared. Every email has a one-click unsubscribe link. See the latest issue →