On 12 October 2026, Google Cloud made budget spend caps for Cloud Run generally available. You set a spending cap, and when it's reached, your Cloud Run workloads pause.
What's new
- A hard stop, not just an alert: budget alerts tell you spending is high; a spend cap pauses the Cloud Run workloads it covers once the cap is reached.
- Generally available: a supported production feature, not a preview.
- Part of a wider pattern: Google's new Gemini agent uses the same idea for AI work, with a hard limit on a project's AI spend set in the Cloud Billing console.
Find out what your setup is really costing you
A free optimization assessment and a prioritized roadmap. No obligation.
Why it matters for your business
Most surprise cloud bills come from something that kept running: a test service left on, a job stuck in a loop, traffic nobody expected. For a small team without someone watching the bill every day, a cap turns a surprise bill into a pause you can review and resume.
There is a trade-off: a paused service is a service that's down. Caps suit test environments, internal tools and side projects best. For customer-facing services, set caps with headroom and alerts well before the limit.
How D3V can help
- Zenta Pulse shows yesterday's cloud and AI spend by project and service, alerts you when spending spikes, and on Google Cloud can cap a runaway bill automatically.
- Our free optimization assessment finds what your setup is really costing you, with a prioritized roadmap.
- With CloudCare Billing, you keep Google's pricing with zero markup and get quarterly spend reviews and Zenta Pulse at no additional cost.
Source: Cloud Run release notes and budget spend caps documentation, Google Cloud.
