Picture this.
It's a few weeks from now. GPT-6 goes GA on Google Cloud. Five teams in your company try it on the same day. Nobody tags anything. At month-end, finance sends you one line from the invoice and one simple question:
"Who spent this?"
That's the moment I want to help you avoid.
On October 21, 2026, Google Cloud announced that OpenAI models are coming to Model Garden. Most posts so far explain what was announced. This one is about what you should set up before it reaches your teams.
Grab a coffee. This takes about 6 minutes to read.
What actually happened (the 60-second version)
-
Three OpenAI models are coming to Model Garden:
- GPT-6 Astra: for demanding work like coding, computer use, and research
- GPT-6.1 Sol: close to Astra, but at a lower cost
- GPT-6 Luna: fast and cheap, built for everyday work at scale
- Status: private preview for select enterprise customers. General availability is planned "in the coming weeks."
- Billing: you buy them through Google Cloud Marketplace. Usage shows up on your normal Google Cloud invoice and draws down your existing cloud commitment.
- Codex: you can already connect Codex CLI and Desktop to the Gemini platform for inference.
- Coming later: OpenAI models inside Gemini for business and Google Antigravity.
Google says this makes it the only hyperscale cloud offering Gemini, Claude, and GPT on one platform.
Why "one invoice" is the real news
Before this, using OpenAI models in a Google Cloud shop usually meant a separate contract, a separate vendor review, and a separate bill.
Now? Anyone with the right access in your project can try GPT-6 next to Gemini, and it all lands on the same invoice.
That's great for developers. It's also how surprise bills are born.
Easy to start means easy to overspend.
The good news: you already have the tools to stay in control. You just need to set them up before the excitement starts.
Step 1: Match the model to the job
Don't let every team default to the biggest model. Here's a simple starting point based on how Google describes each one:
| What the team is doing | Start with | Why |
|---|---|---|
| High-volume, simple tasks (summaries, tagging, routing) | GPT-6 Luna or your current Gemini setup | Fast and cheap at scale |
| Agentic coding, multi-step work | GPT-6.1 Sol | Near top-tier quality at a lower price |
| Hardest problems (complex code, research, computer use) | GPT-6 Astra | Most capable, likely most expensive |
My rule of thumb: start with the cheapest model. Move up only when it fails your own test prompts. Not a benchmark chart. Your prompts.
And keep your existing Gemini workloads as the baseline. Compare against it, don't just replace it.
Step 2: Label every single call
Vertex AI lets you attach labels to API calls. Those labels flow into Cloud Billing, so you can filter and group costs by team, environment, or use case.
Here's what that looks like for a Gemini call in Python:
from google import genai
from google.genai import types
client = genai.Client(vertexai=True, project="your-project-id", location="global")
response = client.models.generate_content(
model="YOUR_GEMINI_MODEL",
contents="Summarize this support ticket in two lines.",
config=types.GenerateContentConfig(
labels={
"team": "support",
"env": "prod",
"use_case": "ticket_summary",
}
),
)
For partner models, the docs show labels passed through an X-Vertex-AI-Labels header instead, and labels only reach billing on the PayGo option.
Heads up: at the time of writing, GPT-6 isn't in the public docs yet. So check whether labels work for OpenAI models once they go GA. If they don't, fall back to separate projects per team. Old trick, still works.
A simple label scheme I like:
-
team: who owns it -
env: dev, staging, prod -
use_case: what it's for
Three labels. That's enough to answer "who spent this?" in seconds.
Step 3: Set budgets before GA, not after
Create a budget with alerts so nobody finds out at month end:
gcloud billing budgets create \
--billing-account=YOUR_BILLING_ACCOUNT_ID \
--display-name="ai-models-monthly" \
--budget-amount=1000USD \
--threshold-rule=percent=0.50 \
--threshold-rule=percent=0.90 \
--threshold-rule=percent=1.0,basis=forecasted-spend
Important: budgets alert you. They don't stop spending. If you need a hard stop, you'll need to wire up automation yourself, or use quotas.
Step 4: Ask finance three questions
Before your teams go wild, sit down with finance and your Google account team:
- Does OpenAI usage draw down our cloud commit? Google says yes.
- Do we get our savings plan discount on it? Read this one carefully. Google says usage counts toward Flexible Savings Plans. "Counts toward" and "gets discounted" are not always the same thing. Get the answer in writing.
- Who approves Marketplace purchases in our org? If the answer is "nobody," fix that first.
Step 5: Check the governance boxes
If you work in a regulated industry, read the fine print:
- ā Your prompts and outputs are not used to train foundation models
- ā VPC Service Controls and unified audit logging
- ā³ Zero Data Retention: coming soon
- ā³ Confidential Compute: coming soon
If your security team requires Zero Data Retention, wait for it. Don't run production data through the preview just because it's shiny.
What we still don't know
Let's be honest about the gaps:
- No public per-token pricing on Google Cloud yet
- No exact GA date
- No list of supported regions
- The models aren't in the public Model Garden docs yet
So this is a "get ready" article, not a "here are the benchmarks" article. I'll write a follow-up once pricing and GA land.
Your 5-minute checklist
Copy this into your team's channel:
- Decide which teams get access first
- Agree on a label scheme (team, env, use_case)
- Create a budget with alerts for AI spend
- Ask finance about commit drawdown and savings plan discounts
- Confirm your data rules (wait for ZDR if you need it)
- Fill the interest form if you want preview access
Final thought
Having Gemini, Claude, and GPT on one platform is a big deal. More choice usually means better results.
But choice without guardrails is just a bigger bill.
Set up the boring stuff now. Thank yourself later.
Your turn: would you run GPT-6 and Gemini side by side, or stick with one model family? Tell me in the comments. š
References
- Google Cloud announcement: Google Cloud expands model choice and flexibility, bringing OpenAI models to customers
- OpenAI announcement: OpenAI models are coming to Google Cloud
- Google Cloud interest form: OpenAI models on Google Cloud
- OpenAI interest form: Get access to OpenAI frontier models on Google Cloud
- Google Cloud blog: Flexible billing and cost controls for agents on Google Cloud
- Vertex AI docs: Custom metadata labels
- Cloud Billing docs: Create, edit, or delete budgets and budget alerts
- gcloud reference: gcloud billing budgets create
Top comments (1)
I'd run them side by side on a small set of real tasks and compare the total cost of getting an acceptable result, including retries and review time. A cheaper call isn't much of a saving if someone spends ten minutes fixing the answer. That's the number I'd want next to each team's spend.