AI news · Source-checked implications

Claude and OpenAI on Google Cloud: two access boundaries

Claude gains an Anthropic-managed deployment option. OpenAI models enter a separate private preview. Processor, feature access and billing need separate checks.

Edited by Clinton FeyisitanPublished Announced 2026-10-23

Review scope: Official announcement and linked technical documentation read 28 October 2026. No installation, token creation, paid request or native workflow test. Dates describe the announcement and our source read separately.

Claude: choose who operates the service

Google Cloud’s 23 October announcement makes an Anthropic-managed Claude deployment option generally available alongside its Google-managed option. Google says model availability, standard pricing and Cloud billing are shared; the processor and feature rollout differ.

In the new option, Anthropic operates the stack under its terms. Google says new Claude platform features, including Managed Agents in beta, skills and code execution, are available at launch. The Google-managed option uses Google as processor and adds platform features as they are integrated.

That distinction matters before moving an agent with existing tool or data requirements. This report has not verified a customer contract, a deployment or a particular region’s feature access.

OpenAI: private preview, with controls still coming

The separate 21 October announcement puts GPT-6 Astra, GPT-6.1 Sol and GPT-6 Luna into private preview for selected enterprise customers. It describes Marketplace billing through a Google Cloud invoice and eligible commitments.

The announcement explicitly places Zero Data Retention options and Confidential Compute in the future. It also describes future availability in Gemini for business and Google Antigravity. These are not evidence of general access today.

No token rates, customer eligibility or complete deployment costs were established in this review. A Cloud invoice does not imply that an existing consumer subscription pays for API use.

A practical handover checklist

Before changing a production route, record the exact model, access approval, service operator, required tools, region, retention settings and bill owner. Then validate a permitted small workload against your existing acceptance criteria.

Our Copilot authentication report explains another case where identity and spending controls need separate checks.

Sources and review scope

This is a documentation report. It does not establish performance, security or reliability in your environment.