Two front doors to the same brain
Google ships Gemini through two platforms, and your auth, billing, compliance posture, and even the SDK's vertexai=True switch all change depending on which one you use. Pick wrong at week one and you'll be paying with a refactor at month six.
Google AI Studio — the developer front door
Lives at ai.google.dev. Auth is a single API key. There is a free tier with real (if narrow) limits. You can wire a working client in five minutes: get a key, set GEMINI_API_KEY, instantiate genai.Client(). This is the right starting point for prototypes, side projects, indie products, and most production apps that don't have a compliance reason to choose otherwise.
Vertex AI — the enterprise front door
Lives inside Google Cloud Platform. Auth is service accounts or Application Default Credentials. Billing rolls into your existing GCP invoice. You get SOC 2, HIPAA, and the ability to call non-Google models (Anthropic Claude, Meta Llama, 200+ others) through the same surface. Setup is hours, not minutes — you need a project, IAM bindings, region selection, and IAM permissions for the service account.
The decision matrix
Compliance pressure or multi-model needs? Vertex. Everything else? AI Studio.
- AI Studio: prototypes, startups, indie products, internal tools, most production traffic.
- Vertex AI: regulated industries (healthcare, finance, government), apps that already live in GCP, teams that want one bill across providers.
The SDK is the same package — google-genai — and you switch between platforms with a constructor flag. That means refactor cost from AI Studio to Vertex is mostly auth and billing, not application code.