Google Cloud has announced that spend caps on Google Cloud Budgets are now generally available. This feature allows businesses to protect their workloads from unexpected cost overruns without risking resource deletion. The update includes three major enhancements inspired by user feedback: programmability, real-time visibility, and automated guardrails.
The first enhancement is the spend caps API, which enables programmatic management of financial boundaries across projects. Users can now automatically enforce, update, or delete spend caps without manual intervention. The second improvement is real-time visibility through live cost reports, which provide immediate financial snapshots when a cap is triggered. The third update is automated monthly resets, which automatically lift spend caps at the beginning of each month, though manual overrides remain an option.
Google Cloud recommends deploying spend caps in non-production environments first, such as developer sandboxes and testing clusters. Users should also configure alerts wisely, ensuring the right team members are notified when a budget is nearing depletion. Additionally, it's important to understand the difference between fixed and on-demand costs, as spend caps only halt pay-as-you-go and CUD-covered requests.
Spend caps work alongside Google Cloud's Early Anomalies Detection to provide a comprehensive defense against runaway cloud spend. Users can get started by navigating to the Budgets and Alerts page in the Google Cloud Billing Console or exploring the newly published spend caps API documentation.