Live
From App‑Level LLMs to a Shared Platform: Redesigning the Stack to Tame HallucinationsFrom Ad‑hoc Checks to a Production‑Ready Agent Evaluation FrameworkReal‑Time Observability for Claude Code Sessions with the Statuspane ModEnforcing US Data Residency with Cloudflare D1AI agents CI: why repository‑centric pipelines are breakingAI Agent Inbox: Deploy Pizza Bot for Background Task ExecutionOpenAPPA delivers zero‑success prompt‑injection protection in benchmark tests – what AI engineers need to knowEU Cyber Resilience Act expands software supply‑chain responsibilities for digital product manufacturersFrom App‑Level LLMs to a Shared Platform: Redesigning the Stack to Tame HallucinationsFrom Ad‑hoc Checks to a Production‑Ready Agent Evaluation FrameworkReal‑Time Observability for Claude Code Sessions with the Statuspane ModEnforcing US Data Residency with Cloudflare D1AI agents CI: why repository‑centric pipelines are breakingAI Agent Inbox: Deploy Pizza Bot for Background Task ExecutionOpenAPPA delivers zero‑success prompt‑injection protection in benchmark tests – what AI engineers need to knowEU Cyber Resilience Act expands software supply‑chain responsibilities for digital product manufacturers
Google Cloud

Google Antigravity Enterprise Expansion Adds Governance, IDE Extensions, and Pooled Quotas

AI SummaryPowered by AI

Antigravity is now available within eligible Gemini Enterprise app subscriptions with built-in administrative controls for spend, security, and usage metrics. This expansion allows platform teams to unify advanced agentic coding tools into existing enterprise workflows without managing separate licenses or invoices.

Google has expanded the availability of Antigravity as part of its Gemini Enterprise Agent Platform following feedback from customers regarding governance needs and developer accessibility. Previously announced at I/O in May, this update brings out-of-the-box administrative controls to eligible subscriptions including Standard, Plus, and Emerging Market licenses.

What Changed

The primary shift is the integration of Antigravity directly into Gemini Enterprise app subscriptions rather than requiring separate add-on management. Administrators can now enable both Antigravity and Android Studio for users through a single console interface.

This release introduces specific billing flexibility features, including granular spend thresholds set at the project level via the Billing console.

Architecture and Operational Implications

The operational model changes significantly regarding resource management. The new architecture supports pooled quotas where shared token pools provide high-demand teams with necessary resources while preventing purchased quota from sitting idle across an organization. To maintain continuous developer workflows when these pooled limits are reached, administrators can opt into overages that smoothly transition excess usage to standard consumption-based rates.

Visibility is consolidated through centralized tracking of API calls and token consumption. This allows organizations to optimize AI investments based on actual activity metrics rather than isolated data points.

Security Considerations

The expansion brings Antigravity under Google Cloud's standard security protections, which includes configurable workspace sandboxing and browser access controls for MCP servers.

  • Audit Logging: A single toggle enables comprehensive logging of prompts, agent responses, and metadata specifically for compliance reporting.
  • Data Privacy: All activity executes strictly within the secure cloud boundary under Google Cloud's Terms of Service to maintain data ownership.

The update also extends IDE support beyond desktop applications like Antigravity 2.0 or CLI, introducing native extensions for Visual Studio Code and VS (preview). These tools enforce corporate identity standards via Workforce Identity Federation (WIF) while removing setup friction.

What This Means For Practitioners

This update signals a move toward embedding agentic AI directly into software delivery workflows rather than treating it as an experimental add-on. Platform engineers should evaluate the rollout of per-user and team controls, which are scheduled for later this year.

The ability to unify developer tools with enterprise-grade governance in one subscription reduces operational complexity but requires careful configuration of security policies around workspace access boundaries.
Google Cloud practitioners should monitor the transition from pooled quotas to overage models, ensuring that budget caps are set appropriately before enabling continuous workflows.

Originally published atGoogle Cloud Blog