• Sources: primary
  • Summary: Spend Management is in beta for pay-as-you-go customers, starting with Workers and Durable Objects, and is configurable through the dashboard, the cf CLI, or a REST API with a usage_block action. When a cap is hit, new billable invocations are rejected, including Cron Triggers and Queue consumers, while static assets keep serving. Service resumes when the limit is raised, the policy is disabled, or the next billing cycle starts. Cloudflare says spend is shown in under 10 minutes, computed by a two-stage metering pipeline that aggregates usage into one-minute and then five-minute windows before an account-partitioned usage engine and a rating engine price it.
  • Why it matters: A runaway Worker or Durable Object bill can now be stopped by an enforced cap instead of only an alert email.
  • Background: Most cloud providers offer budget alerts that notify but do not stop spending, which is why hard caps are a long-standing developer request. Enforcing a cap means metering usage across a global network, pricing it against plan allowances, and pushing a block decision back to every location, so caps always trail real usage by the aggregation delay. Cloudflare's post notes that billing cycles start from the subscription date, not the calendar month.