Two launch stages, one date
Both companies published their announcements on October 21, 2026. Google Cloud says OpenAI’s GPT-6 Astra, GPT-6.1 Sol, and GPT-6 Luna are rolling out now in private preview to selected enterprise customers, with API access through its Model Garden. OpenAI says general availability is planned in the coming weeks. Those statements describe different access stages: a limited preview is not broad availability. OpenAI also says Microsoft remains its primary cloud partner.
Separate product details from provider claims
Google describes this route as using its cloud governance and infrastructure. Google says prompts, context, and outputs stay within a designated data perimeter and are not used to train foundation models. The same post says Zero Data Retention options and Confidential Compute are coming soon; do not treat those future options as available today. These are provider statements, not an independent security review. Confirm the terms and controls for the specific account, region, model, and preview before sending any data.
A low-risk preview checklist for an app team
- Illustrative example: test a fake support-ticket assistant using invented tickets with no real names, customer details, or credentials. Keep the first exercise away from live tools and production data.
- Before connecting an app, confirm preview eligibility, model names, regions, request limits, API shape, billing path, and which controls are available now. Ask the provider which announced features are still forthcoming.
- Record the expected behavior on a small fixed set of fake tickets. Check that the model cites the supplied ticket text, marks missing information as unknown, and does not invent a refund promise or update a record.
- Compare the same cases with your current model or a simple fallback, and log latency, errors, output differences, and total cost. This is your application’s test set, not evidence that one provider or model is generally better.
- Only after review, decide whether the new route fits a real workload. Keep a fallback and a way to disable the integration while preview terms, availability, and behavior can still change.
Preview is not a benchmark or a security sign-off
The announcements describe a partnership and an access rollout, not comparative model results. We did not access the preview or run an API test. Treat Google’s security and governance descriptions as provider claims; independently review the contract, configuration, and data path that would apply to your deployment.