FR
live

Google Cloud brings OpenAI’s GPT-6 models to Model Garden and becomes the only hyperscaler with Gemini, Claude and GPT

On October 21, 2026, Google Cloud put OpenAI’s models — GPT-6 Astra, GPT-6.1 Sol and GPT-6 Luna — into its Model Garden, becoming the only hyperscaler offering Gemini, Claude and GPT on a single platform. For a CISO the story is not the catalog but the governance: these models are billed through Marketplace, stay inside your data perimeter and plug into VPC Service Controls.

A brass manifold where three steel pipes of different diameters converge into a single outlet, one amber valve wheel on the shared line.

October 21, 2026. Google Cloud announces that OpenAI’s models — GPT-6 Astra, GPT-6.1 Sol and GPT-6 Luna — are now available in its Model Garden. October 21, 2026. The Mountain View company claims to be “the only hyperscale cloud provider” offering Gemini, Claude and GPT side by side, alongside more than 200 first-party, third-party and open models. October 21, 2026. OpenAI, for its part, confirms it will sell its frontier models and its Codex coding agent through Google Cloud in the coming weeks. Why it matters: the cloud war is no longer fought over catalogs, but over governance — and that is exactly where Google Cloud is attacking.

A strategic shift, not just a catalog addition

Since 2019, OpenAI has built its business on a de facto exclusive partnership with Microsoft Azure. The October 21 announcement does not end that relationship, but it relativizes it: OpenAI becomes one model vendor among several, distributed across multiple clouds, much as Anthropic did before it. Google Cloud uses the move to claim a unique position — the neutral broker that hosts all three major closed models while owning only one of them.

The three models span a clearly tiered spectrum of price and capability. GPT-6 Astra targets demanding work: coding, computer use, professional tasks and scientific research. GPT-6.1 Sol promises near-Astra intelligence at lower cost, aimed at agentic coding and professional work. GPT-6 Luna is the fast, cost-efficient model for everyday work at scale. The segmentation mirrors the Opus / Sonnet / Haiku hierarchy that buyers already know from Anthropic.

The move fits a broader commercial trend. Google Cloud saw revenue jump 63% in Q1 2026 to $20.03 billion, growth that dwarfs AWS’s 28% and Azure’s 40%. AWS still leads in absolute terms, but Bedrock does not distribute GPT, and Azure hosts OpenAI without offering Gemini. The “only hyperscaler with all three” position therefore has a direct translation: a company that wants to arbitrate the three model families no longer needs three clouds. It is also a retention weapon — the more AI spend a customer concentrates on Google Cloud, the costlier it is to leave.

This also settles a question that has hung over enterprise AI for two years: whether buyers would accept a single-vendor lock-in for their models. The answer, spelled out by the two most prominent AI labs moving to multi-cloud distribution, is no. OpenAI gains a second distribution channel and Google Cloud gains gravity; the customer gains leverage. Procurement teams should read this as the new normal — a model is a component you can source from multiple clouds, not an anchor that chains you to one. For AWS, the pressure is now visible: Bedrock aggregates Claude and Nova but still lacks GPT, and the neutral-broker argument it once held is now Google’s.

Governance is the real front line

The Google Cloud post deliberately steps away from the “who has the best model” debate and plants itself on compliance. That is the point a CISO should keep. Three guarantees structure the offer.

First, the data perimeter: prompts, context and outputs stay within your designated perimeter and are never used to train foundation models. A Zero Data Retention (ZDR) option is promised “coming soon” — it is not available at launch, which is worth noting before you sign.

Second, access isolation: OpenAI models run on dedicated Google Cloud infrastructure, queries are routed through hardened, isolated gateways, and the third-party provider has no unauthorized access to your cloud environment. Confidential Compute is also flagged “coming soon”.

Third, unified auditing: every agent and model interaction runs under an authenticated identity, with VPC Service Controls and centralized audit logging across the fleet. For a company that must prove to an auditor where its data went, that is the difference between an API consumed ad hoc and an AI workload governed like the rest of the estate.

Billing gets simpler

The detail that changes a CFO’s life fits in one sentence: OpenAI models are transacted through the Google Cloud Marketplace. One invoice, usage drawn against existing cloud commitments, and counting toward Flexible Savings Plans (FSP) — the discount mechanism Google Cloud has been pushing since early this year. No separate contract to negotiate with OpenAI, no orphaned budget line: AI joins the same circuit as the rest of your cloud spend.

Yashodha Bhavnani, VP of AI Products at Box, captures the customer logic: using OpenAI models through Google Cloud gets you “OpenAI’s frontier AI models alongside Google Cloud’s security and compliance capabilities”. That is precisely the pitch the platform wants circulating: the best model, without giving up governance.

What to watch before you board

The announcement is strong, but it is a private preview. The three GPT-6 models are available today only to a selection of enterprise customers, on request, with a gradual rollout. Two major capabilities — ZDR and Confidential Compute — are promised without dates. And the integration into Gemini for Business and Google Antigravity is “coming soon”, not live.

In practice, a customer who wants to lock in non-retention of their data contractually cannot do so at launch. That is the kind of detail a CISO should demand in writing before moving a sensitive workload. The rest — private preview, interest forms — is the standard choreography of a big launch, not cause for alarm.

Finally, watch the balance of power this deal creates. Google Cloud becomes dependent on OpenAI’s goodwill to distribute GPT, while OpenAI sheds its single-cloud dependence on Azure. For the customer that is mostly good news — competition among distributors pushes price and governance in the right direction — but it means contractual guarantees (ZDR, data residency, sub-processors) must be checked model by model, not just platform by platform.

Verdict

If you are already on Google Cloud and comparing models, this announcement centralizes your decision. You will be able to arbitrate Gemini, Claude and GPT on the same invoice, under the same VPC Service Controls perimeter and the same audit trail — without renegotiating three contracts. If you are on Azure and tied to OpenAI, nothing forces you to move: your existing contract stands, and OpenAI has announced no retreat from Azure. If you require data non-retention from day one, wait until ZDR is actually live before signing. The strategic signal is clear: Google Cloud is betting that enterprise AI buying decisions will be won on governance, not benchmark leaderboards.

References

The cyber brief, every Tuesday

The flaws that matter and the patches to apply, in a ten-minute read.

No spam. One-click unsubscribe.
read next

On the same topic

Amazon ECS Gateway automates service ingress and removes per-service provisioning

On October 20, 2026, AWS launched ECS Gateway, an account-level resource that provisions and manages Application Load Balancers, ACM certificates, WAF rules and security groups for your ECS services. A platform team defines the standard once, an application team connects a service with one line: the per-service ingress bottleneck is gone.

AWS puts S3 inside the Vercel Marketplace and swaps static keys for OIDC federation

On October 14, 2026, AWS made S3 — including S3 Tables and S3 Vectors — provisionable from the Vercel dashboard and v0, using an OIDC token exchange that removes static access keys from the path. For front-end teams that consume object storage without ever opening the AWS console, the days of an IAM key pasted into an .env file are over.

← Back to the feed

Type at least two characters.

↑ ↓ navigate ↵ open esc dismiss