Skip to content

To deploy Google Antigravity using models hosted directly within your organization’s Google Cloud infrastructure, you can integrate with Gemini Enterprise. Every session runs under Google Cloud’s enterprise security controls, data residency guarantees, and the Google Cloud Terms of Service.

Supported products: Antigravity 2.0 Antigravity CLI Visual Studio Code Visual Studio JetBrains (Preview) Zed (Preview) Xcode (Preview)

You can connect Antigravity to Gemini Enterprise in two ways:

  • Google Cloud Project & API - Connect directly via Google Cloud project APIs to use Antigravity with consumption-based billing.
  • Gemini Enterprise license - Connect with your Gemini Enterprise license (Standard or Plus) to get access to included quotas, managed overages, and centralized administrative controls.

By connecting Google Antigravity to your Google Cloud project, your organization gains:

Enterprise Governance

Operates under your existing Google Cloud Terms of Service with centralized administrative controls.

Data Residency & Security

Satisfies private networking (VPC Service Controls) and regional data residency constraints. Enterprise prompts, responses, code, and telemetry are never stored outside your private environments.

To set up Gemini Enterprise subscriptions, follow the official Google Cloud onboarding guide.

Complete the following three steps to provision your Google Cloud project and enable API access.

  1. Select or Create a Google Cloud Project: Select an existing project or create a dedicated project for your team’s Antigravity workloads.

  2. Verify Cloud Billing: Ensure that Cloud Billing is active for your selected Google Cloud project. You can inspect your project’s billing status in the Cloud Console.

  3. Enable the API: Enable the Gemini Enterprise API (aiplatform.googleapis.com) to allow Antigravity clients to connect to your project’s model endpoints.

Google Antigravity uses a single sign-on (SSO) flow. When you sign in with your corporate business account, your license tier is automatically detected without requiring manual tier selection.

  1. Start Antigravity 2.0, the Antigravity CLI, or your supported IDE extension.
  2. Select Sign in to open the browser authentication flow.
  3. Choose Business account (subject to the Google Cloud Terms of Service).
  4. Select Continue with Google Cloud (or configure Advanced SSO / WIF).
  5. Complete authentication in your browser.
  6. Once authenticated, the License Selector displays your assigned licenses.
  7. Confirm the project linked to your license and select it. Alternatively, select Other to self-assign a license by entering your project ID and selecting a location (global, us, or eu).

Bring Your Own Identity (BYOID) uses Workforce Identity Federation (WIF) to let your organization authenticate through an external identity provider, such as Okta, instead of a standard Google Account.

  1. In Antigravity, select Business account.
  2. Select Advanced WIF Configuration.
  3. Enter the WIF Configuration String provided by your organization’s administrator.
  4. Complete sign-in through your federated identity provider.
  5. Select or self-assign a license from the License Selector.

For headless environments and automated terminal workflows, Antigravity supports authentication using Google Cloud Application Default Credentials (ADC). ADC is available across the Antigravity CLI, Antigravity 2.0, and Antigravity IDE.

Complete the following steps to generate and verify your credentials:

  1. Generate local Application Default Credentials for your project using the Google Cloud SDK:

    gcloud auth application-default login --project {GCP_PROJECT}
  2. Verify that your credentials file exists. On Linux and macOS, the default path is:

    ~/.config/gcloud/application_default_credentials.json

Enable ADC authentication based on your Antigravity surface:

  • Antigravity CLI: ADC is enabled only when the AGY_ADC_AUTH environment variable is set to true:

    export AGY_ADC_AUTH=true
  • Antigravity 2.0 and IDE: enable ADC using one of the following two options:

    • Launch from a terminal with AGY_ADC_AUTH=true set (same as the CLI).

    • Because launching from a terminal is not always feasible, enable the enableAdc user setting manually in ~/.gemini/config/config.json:

      {
        "userSettings": {
          "enableAdc": true
        }
      }

To sign out of ADC on the CLI, unset the environment variable and restart your terminal session:

unset AGY_ADC_AUTH

Similarly, for Antigravity 2.0 and IDE, undo any changes to ~/.gemini/config/config.json (or unset AGY_ADC_AUTH if launched from a terminal) and restart the application.

This section provides a brief walkthrough of key ADC parameters to be aware of.

Antigravity resolves credentials using the standard ADC search order. Learn more about how ADC finds credentials.

Antigravity resolves the Google Cloud project ID from the first source found, in this order:

  1. The quota_project_id field in the ADC file (set using the gcloud CLI, or edited manually).
  2. [CLI only] The GOOGLE_CLOUD_QUOTA_PROJECT environment variable.
  3. The project ID reported by the metadata server (for service accounts).

Antigravity resolves the endpoint location from the first source found, in this order:

  1. The surface-specific configuration:
    • [CLI]: the GOOGLE_CLOUD_LOCATION environment variable.
    • [Antigravity 2.0 / IDE]: the location field in the ADC file.
  2. Otherwise, the location defaults to global.

Antigravity CLI, Antigravity 2.0, and IDE Extensions support multi-region deployment endpoints to satisfy regional data residency requirements:

Endpoint RegionBase Endpoint URISupported Capabilities
GlobalglobalText Generation, Code Inference, Multimodal, Image Generation
US Multi-RegionusText Generation, Code Inference, Multimodal
EU Multi-RegioneuText Generation, Code Inference, Multimodal

For full endpoint specifications, consult the Deployment Endpoints Documentation.

Request & Response Logging

Audit model interactions and maintain enterprise compliance records for your Gemini Enterprise instance. Learn more

VPC Service Controls (VPC-SC)

Enforce private networking security perimeters by adding the Gemini Enterprise API (aiplatform.googleapis.com) to your VPC-SC perimeter. Learn more

  • No Licenses Appear During Setup: Licenses are assigned by your organization’s Google Cloud administrator. If the License Selector is empty, contact your administrator to ensure your account has been granted access to a Gemini Enterprise Standard or Plus license.
  • Missing BYOID Sign-In Option: Ensure you are running the latest release of Antigravity 2.0, the Antigravity CLI, or your IDE Extension, as enterprise authentication and BYOID support are included natively in all recent releases.

When contacting Google Cloud Support, include the diagnostic log file from your most recent session:

  • Antigravity CLI (Linux and macOS):
    ~/.gemini/antigravity-cli/cli.log
  • Antigravity 2.0 (macOS):
    ~/Library/Logs/Antigravity/language_server.log