Google Cloud made Budgets spend caps generally available, adding programmatic controls, live cost reports, and automatic monthly resets.

Google Cloud made spend caps on Cloud Budgets generally available, following an earlier preview. Google describes the feature as blocking eligible service usage to control runaway spending without deleting resources.

A new spend-caps application programming interface, or API, is accessible through the existing Cloud Billing Budgets API. Customers can programmatically apply, lift, update, or delete caps for eligible services within individual projects, including newly created development sandboxes.

For AI services, Google says enforcement triggers within minutes of usage, using estimated live costs rather than waiting for standard billing pipelines to settle net costs. Those estimates are now visible in Cost Reports, providing the cost snapshot associated with an enforcement event.

Triggered caps can now reset automatically at the beginning of the next month, allowing blocked services to resume, while manual controls remain available. Default alerts go to billing administrators and project owners at 50%, 80%, and 100% of the cap, and Google recommends starting with non-production environments. The excerpt states that caps halt pay-as-you-go and committed-use-discount-covered requests, but its discussion of provisioned-throughput treatment is truncated and does not support a broader claim that every charge stops.