Google Cloud made spend-cap budgets generally available on October 13, 2026, according to its release notes. Customers can pause new usage when gross estimated spending, excluding savings and credits, exceeds a configured amount. Supported services are Gemini API, Gemini Enterprise Agent Platform (formerly Vertex AI), Cloud Run and Cloud Run functions. Each cap covers one project and one eligible service for a calendar month; customers can manage caps through the console or Cloud Billing Budget API. Enforcement is delayed, and customers still pay overages. In-flight requests can finish, while persistent compute and storage resources remain billable. Sources: Google Cloud
CloudSource: Google Cloud
Google Cloud makes spend-cap budgets generally available for four services
Why it matters
Developers gain automatic spending controls for eligible services, but Google's release announcement specifies neither a maximum enforcement delay nor an overage ceiling. [1] Google recommends setting thresholds below absolute spending limits to leave a buffer. [2] Teams should test how applications handle blocked usage and plan for recovery, which can take up to one hour. [3] Caps use gross estimated spending, excluding savings and credits. [2][3]
Attribution
Sources
- 1Google CloudGoogle Cloud release notesSource published (UTC)
- 2Google CloudManage spend cap budgets
- 3Google CloudUsing the Cloud Billing Budget API for spend cap budgets
- 4FinOps LLMGoogle Cloud AI Spend Caps: A FinOps GuideSource published (UTC)
Read the original source for full details and context.
Article · Cloud
Test GitHub Actions lockfiles by moving a nested action’s tag
GitHub’s workflow lockfile preview covers nested action dependencies beyond a top-level commit pin. This guide sets up a controlled moved-tag experiment, separates execution from dependency updates, and explains what to check before enforcing lockfiles.
AI
Oracle adds managed MCP server support for OCI Database Services
Oracle added managed MCP server support for OCI Database Services on October 13, 2026, according to its release notes. The interface lets MCP-compatible AI agents and applications inspect database resources through read-only operations; it cannot modify those resources. It supports four services: Base Database Service, Exadata Database Service on Cloud@Customer, Exadata Database Service on Dedicated Infrastructure and Exadata Database Service on Exascale Infrastructure. Clients connect through generated endpoints using Streamable HTTP, while OCI IAM authenticates clients and enforces existing access policies. Customers can choose which resource categories to expose and enable or disable servers.
Article · AI
How to test OpenCode session recovery on Cloudflare Durable Objects
Cloudflare’s experimental OpenCodeHarness documents session recovery after eviction, but external tool effects need a separate test. This guide proposes an interruption after a remote commit, then checks stored state, resumed execution, and the destination’s ledger.