Google Cloud Spend Caps Reach General Availability with API and Monthly

Google Cloud has made spend caps generally available on Cloud Billing Budgets, pausing new usage of a covered service in a project once a monthly budget is reached without deleting resources. InfoQ's report says the release adds an API, estimated live costs that trigger caps within minutes for AI services, and automatic monthly resets. Enforcement remains limited to the Gemini API, the Gemini Enterprise Agent Platform, Cloud Run, and Cloud Run functions.

Steef-Jan Wiggers wrote the 10 November 2026 report for billing administrators and project owners. This report covers how a triggered cap treats in-flight requests and persistent resources, the three changes since the July public preview, and the one-project, one-service calendar-month scope. It also covers the October Hacker News criticism, Simon Willison's case for default hard caps, AWS and Azure spend limits, and the early-anomaly baseline configured beside caps.

01In-flight requests and persistent resources

A spend cap is a budget with enforcement attached. When estimated spend on the capped service reaches the target amount, new requests to that service in that project are blocked. In-flight requests run to completion and are charged, persistent resources keep running, and nothing is deleted.

Usage covered by committed-use discounts is paused along with pay-as-you-go usage, while Provisioned Throughput for AI models is never halted. Billing administrators and project owners receive alerts at 50, 80, and 100 percent of the cap. The documentation is the source for the block, the in-flight charge, and the rule that nothing is deleted.

02Live cost estimates and monthly resets

Google changed three things between the July public preview and the GA release, and Google's blog post is the source for that list. Enforcement for AI services now runs on estimated live costs shown in Cost Reports rather than on settled billing data, which can lag by hours. Those live estimates are what can trigger a cap within minutes for AI services.

A triggered cap resets automatically at the start of the next month. In the preview, the block stayed in place until someone lifted it in the console, and that console option remains. Caps can now be created, lifted, and deleted through the existing Cloud Billing Budgets API.

03One project and list-price scope

A cap covers one project and one service for a calendar month, so folders, organizations, labels, and multi-service budgets are out of scope. Reseller accounts are outside the cap. Subscription charges such as Gemini Enterprise seats are outside the cap as well.

The estimate that drives enforcement is calculated at list price and excludes credits and discounts. Enforcement is also not instant. The documentation states that "any cost overages are billed as normal" and advises setting the cap "slightly below your absolute limit."

Compute Engine, Cloud Storage, and networking are not eligible services. The cap addresses a runaway model or agent loop and does not cover a forgotten GPU instance. Eligible products remain the Gemini API, the Gemini Enterprise Agent Platform, Cloud Run, and Cloud Run functions.

04October criticism and rival limits

The narrower scope drew criticism when the preview expanded in October. On a Hacker News thread, one commenter who had asked Google for the capability a year earlier to control AI spend called the result "very crude, not granular like the rich IAM system," noting the four-product, month-only design. Another observed that Cloud Run had been added that morning, so the service list was still growing.

Developer Simon Willison argued in October that pay-by-usage services should default to hard caps, because coding and personal agents make it far easier to spin up code that calls paid APIs. He wrote that "most businesses and individuals would prefer errors to a surprise $10,000+ bill." He cited Google's caps alongside a project-level spend limit in AWS's new account experience.

That AWS limit pauses the whole project and stops its resources when reached, preserving data for 90 days, and AWS is rolling it out to a limited number of customers. Azure's spending limit remains confined to free accounts and credit-based subscriptions. Microsoft states it isn't available for subscriptions with commitment plans or with pay-as-you-go pricing.

05Sandbox caps and early anomalies

Caps can now be created, lifted, and deleted through the existing Cloud Billing Budgets API. Google suggests wiring that API into project provisioning, so a new sandbox gets a cap on creation. Lifting a cap in the console remains available alongside the automatic monthly reset.

Spend caps pair with early anomalies. Early anomalies are a daily baseline model that flags directional cost variances per service and names the top SKUs behind a spike. Google positions that daily baseline as the detection half of the same control loop.

Both are configured from the Budgets and Alerts page in the Billing console or through the Budgets API. Billing administrators and project owners receive alerts at 50, 80, and 100 percent of the cap. Each cap covers one project and one service for a calendar month.