Google Cloud spend caps now generally available

Today, we’re announcing that spend caps on Google Cloud Budgets are generally available. 

With this release, we’re delivering ways to protect your workloads from runaway costs without risking resource deletion. More importantly, we’re introducing three major updates, directly inspired by your feedback since the initial preview, to bring programmability, real-time visibility, and automated guardrails to your cost-control playbook.

How the new spend caps can help your business 

We have significantly enhanced the usability and power of spend caps in three ways: 

1. Automation through spend caps API: Managing guardrails manually across hundreds of projects is a major operational challenge. To address this, we have launched the spend caps API, which can be accessed from the existing Cloud Billing Budgets API. You can now programmatically enforce your financial boundaries for eligible services within each project, without additional overhead. You can automatically lift, update, or delete caps on the fly and instantly apply a spend cap whenever a developer spins up a new sandbox project.

2. Real-time visibility with live cost reports: Spend caps for AI services trigger within minutes of usage using estimated, live costs. When a cap triggers, you need to know exactly why and when the limit was breached. You can now view these faster, estimated costs directly inside your Cost Reports. Instead of waiting hours for standard billing pipelines to settle net costs, you get the exact financial snapshots that triggered the enforcement, giving you the immediate context needed to run a precise root-cause analysis.