Claude gained a new generally available route through Google Cloud on 22 October. In the Anthropic-managed offering, customers use Google Cloud credentials and billing while Anthropic operates the Claude API. The important choice sits behind that shared invoice: the new route and the existing Google-managed service have different data processors and different access to platform features.

Based on 5 reviewed sources · See sources

The native platform, through cloud billing

Anthropic says the new option receives Claude Platform features and betas on the day they launch natively. Available capabilities include code execution, skills, prompt caching and batch processing, alongside Claude Managed Agents in beta. General availability of this purchasing route does not change the maturity of each feature.

Google’s announcement says both routes offer new Claude models on day zero, the same model pricing and eligible commitment drawdown. The distinction is earlier access to platform tools on the Anthropic-managed route. Claude’s original announcement below introduces that option.

From the source · Claude ·

Claude announces the Anthropic-managed route’s general availability. The account’s follow-up describes day-zero platform features; this is a deployment announcement, not a new model.

View the original post on X ↗

The same bill can mean a different processor

Anthropic acts as data processor under its commercial terms for the new route. Google remains the processor for the existing Google-managed offering, which provides controls including VPC Service Controls, customer-managed encryption keys and regional residency options. European teams need to match their required control to the actual offering.

Anthropic’s launch page lists US and Global endpoints for the new service. It does not announce an EU endpoint. The current documentation’s comparison also separates the API request formats and IAM roles: credentials granted for one offering do not automatically grant access to the other.

The detail

Two routes through the same cloud account

Published deployment differences · checked 23 October 2026

Two routes through the same cloud account. Published deployment differences · checked 23 October 2026
QuestionAnthropic managedGoogle managed
Who processes the data?Anthropic, under Anthropic terms.Google Cloud, under existing Google Cloud agreements.
When do platform tools arrive?Day-zero Claude Platform features and betas.As features are integrated into Google-managed infrastructure.
What about European residency?Launch lists US and Global endpoints.Google lists EU residency alongside US and APAC; check the model and endpoint.
The Anthropic-managed endpoint scope comes from Anthropic’s launch announcement. The table compares documented service choices, not measured performance or a claim that every feature is generally available.Source: Google Cloud deployment announcement · 2026-10-23

Migration is more than a billing switch

The setup guide says this route creates a new Anthropic organisation for the Google Cloud project, separate from an existing Claude Enterprise or API organisation. Access roles apply across the project’s workspaces; teams requiring separate access should use separate projects. Existing discounts need to be agreed with the account team before usage, because they cannot be applied retroactively.

The broader direction resembles OpenAI’s new Google Cloud purchasing route, but the access stages differ: that OpenAI offering remains a selected-enterprise private preview. Cloud billing is becoming a common front door; availability, processing location and operational controls still need checking behind it.

Sources

Written with AI assistance from the sources above. Analysis and practical implications are our interpretation. Our editorial approach.