Skip to main content

Buyer guide

Antigravity in Gemini Enterprise: Rollout and Controls Checklist

Editions, roles, APIs, sign-in, the admin defaults to change before day one, model approval, logging, and spend caps for a team rollout.

Reading time
3 min read
Sources
11 cited
In this piece
Google Antigravity−16 Mixed

Give engineers Antigravity through a Gemini Enterprise Standard or Plus seat, and change its permissive defaults before the first engineer signs in. Google lists no SOC 2 or ISO 27001 coverage for Antigravity, so clear that with security before you buy. Since August 20, 2026, eligible seats include Antigravity 2.0, the CLI, the IDE extensions, pooled credit, overage controls, and admin settings.

When you need this

  • Engineers already use Antigravity on personal Google AI plans and you want them on company terms.
  • Your Gemini Code Assist subscription is nearing its final renewal and Google points you to Gemini Enterprise.
  • Security wants to know what the agent can run, read, and send before approving it.
  • Finance wants a monthly ceiling on agent spend.

Rollout checklist

  1. Check edition and compliance fit

    Does your edition include AI developer tools, and do your audits allow them?

    SetA Standard, Plus, Standard Emerging Market, or Pay-as-you-go subscription on an invoiced Cloud Billing account. Business and Frontline do not list AI developer tools. Google states that Antigravity in Gemini Enterprise does not support Access Transparency, FedRAMP, IL4 or IL5, ISO 27001 or 42001, ITAR, or SOC 1, 2, and 3. Confirm with security before purchase.

  2. Enable APIs, then buy and assign

    Will licenses provision cleanly?

    SetThe Discovery Engine, Business AI Code, and Gemini Enterprise APIs enabled about five minutes before licenses are bought, since purchases can fail otherwise. Grant roles/discoveryengine.agentspaceUser to every developer, because the Admin role alone does not grant access.

  3. Change the permissive defaults

    What can the agent do on day one?

    SetFour changes under Settings, AI developer tools. Move terminal auto-execution from its default of Always proceed to Require review or Proceed in sandbox. Turn sandbox mode on, limit browser access to an allowlist, and limit MCP servers to an approved configuration. File access outside working folders defaults to Deny, and Google notes the intended default is Always ask.

  4. Approve models and logging

    Which models may developers pick, and what is recorded?

    SetGemini models are on by default. Claude Opus 5.5 and Sonnet 5.5 need administrator consent, bill per token, and run only in global, us, or eu locations. Turn on prompt and response logging and metadata logging, both off by default, if you need an audit trail. Google stores the logs in your project and does not use them for training.

  5. Set sign-in, region, and network

    How do engineers authenticate, and where does inference run?

    SetGoogle Cloud SSO or Workforce Identity Federation for people, Application Default Credentials for headless runs, one license per project and location, and a location of global, us, or eu. Allowlist businessaicode.googleapis.com and the Discovery Engine endpoints on port 443, and add the Gemini Enterprise API to your VPC Service Controls perimeter if you use one. Leave out the standalone Antigravity IDE, which Google does not support for enterprise.

  6. Cap the spend

    What happens when the pooled credit runs out?

    SetStandard includes US$10 and Plus US$15 of Antigravity credit per user per month, enforced weekly as one pool worth a quarter of the monthly value times licensed seats, with no rollover. Decide whether overage at pay-as-you-go rates is on, set budget caps in Cloud Billing, and track third-party model tokens, which bill separately and still draw background Gemini usage.

Questions to settle before rollout

  1. Which audits or customer contracts require SOC 2 or ISO 27001 coverage for developer tools?
  2. Who owns the AI developer tools settings, and who approves a change to them?
  3. Which teams may use Claude models, and on whose budget?
  4. How many engineers already use Antigravity on personal accounts, and by when do they move?
  5. What weekly credit pool do your seat counts give, and what happens when a heavy team drains it midweek?

Red flags

  • Terminal auto-execution left on Always proceed with the sandbox off.
  • Licenses bought before the APIs are enabled.
  • Engineers signing in with personal accounts on company code after seats exist.
  • No budget cap on the billing account that carries overage and third-party models.

Products in this piece

Sources

Official documentation
9
Public source
2
  1. Gemini Enterprise docs: AI developer tools overviewOfficial documentationdocs.cloud.google.com
  2. Gemini Enterprise docs: Configure AI developer tools settingsOfficial documentationdocs.cloud.google.com
  3. Gemini Enterprise docs: Quotas and pay-as-you-go usageOfficial documentationdocs.cloud.google.com
  4. Gemini Enterprise docs: Compare editionsOfficial documentationdocs.cloud.google.com
  5. Antigravity docs: Antigravity in Gemini EnterpriseOfficial documentationantigravity.google
  6. Antigravity docs: IDE extensionsOfficial documentationantigravity.google
  7. Antigravity blog: Bringing Antigravity to Gemini Enterprise (Aug 20, 2026)Official documentationantigravity.google
  8. Google Antigravity pricingOfficial documentationantigravity.google
  9. Gemini Code Assist docs: Gemini Code Assist Standard and Enterprise subscriptionsOfficial documentationdocs.cloud.google.com
  10. Hacker News: a company pushed off Antigravity by plan changes (Jul 21, 2026)Public sourcenews.ycombinator.com
  11. Google AI Developers forum: Antigravity CLI on Workspace and Google AI Pro accounts (Oct 12, 2026)Public sourcediscuss.ai.google.dev

Keep reading

  1. Buyer guideGoogle Antigravity Workflow PlaybookSix Antigravity setup and review habits for teams whose engineers get different results from the same agent, or whose quota runs out mid-task.
  2. Buyer guideEngineers on Personal Antigravity Plans: A Data and Terms ChecklistPersonal Google accounts put company code under consumer terms, with training on interactions and account bans. How to find these engineers and move them to company terms.
  3. Buyer guideGemini CLI or Antigravity CLI: Planning the DecisionCode Assist sign-in to Gemini CLI ends with each contract, while paid API keys keep working. Set every team a move date to Antigravity CLI ahead of its last renewal.
Read the research