Is Google Antigravity Code Secure?

Short answer: Antigravity moves you fast through Google Cloud's surface area, and that surface is unusually easy to over-scope while you iterate. IAM roles, service accounts, Vertex endpoints, storage buckets: each is a foot-gun when you're moving quickly, and the generated defaults lean permissive.

This guide is for builders shipping a Google Antigravity app who want the permissions and perimeter tightened before real users arrive. It maps to the Antigravity security audit we run.

Where Antigravity tends to over-scope

Over-scoped service accounts

Antigravity's generated service accounts often inherit a broad role like Editor when something narrow like Storage Object User would do the job. Broad IAM means a single leaked credential reaches far more than your data. Apply least privilege: tighten every account to the minimum role its task needs. Google's IAM best-practices guide is the reference.

Vertex keys in the bundle

Vertex AI keys belong on the server. During prototyping, one can take a detour through the client, and anything in the browser bundle is readable by every visitor. Confirm no Vertex or Google API key ships client-side, and rotate any that did.

Unauthenticated Cloud Functions

Cloud Functions deployed with --allow-unauthenticated are perfect for a demo and dangerous in production: anyone with the URL can invoke them. Confirm which functions still trust the world and require auth on the ones that touch real data.

Buckets less private than they look

GCS bucket ACLs are deceptively easy to mis-set. Public, uniform, and IAM-based access behave differently, and "it worked in testing" often means "publicly readable." Verify each bucket's access matches what you intended.

The Antigravity security checklist

• Least-privilege IAM: no Editor-by-default service accounts.
• Vertex/Google keys server-side only: nothing in the client bundle. Scan to confirm.
• Auth on Cloud Functions: no --allow-unauthenticated in production.
• GCS access verified: public vs uniform vs IAM matches intent.

These are the cloud-flavoured version of the eight holes in vibe-coded apps: Antigravity concentrates them in IAM and the Google Cloud perimeter.

Verify your Antigravity app

Start with a free key-leak scan, then walk the checklist. For a full review of your IAM, keys, functions, and buckets, see the Antigravity security audit or book a Launch scan: we read what shipped and open pull requests with the fixes in plain English.

Antigravity's reach across Google Cloud is its strength. Right-sizing the permissions is what keeps that reach from becoming exposure.