Google Cloud Spend Caps Reach General Availability With an API and Live Costs
TL;DR A spend cap is a Google Cloud budget rule that pauses eligible services in a project once usage cost passes the budget's target amount, and it leaves the resources themselves in place. Google made spend caps generally available on 30 October 2026, after a preview period. The release adds three things: a spend caps API on the existing Cloud Billing Budgets API, live cost reports showing the…
Google Cloud introduced spend caps as a budget rule on 30 October 2026, allowing for pauses in service usage when costs exceed predetermined thresholds. This feature, which adds a spendCap object to the existing Cloud Billing Budgets API, enables three threshold rules at 50%, 80%, and 100% of the CURRENT_SPEND. Forecasts of the costs triggering enforcement are available through live cost reports, providing immediate context for root-cause analysis.
Once a cap is enforced, services stop serving paid requests, but the resources remain intact. The cap can be lifted manually or automatically at the start of the next budget period, with services taking up to an hour to return to normal. Google recommends using strict low-dollar caps for sandboxes and testing clusters first. The new controls leave architecture decisions, such as workload placement, to the users while preventing runaway costs.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
