# Anthropic — Manage costs and demonstrate ROI for Claude Code on Google Cloud

- Company: Anthropic (anthropic.com)
- Announced: 2026-10-27
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://claude.com/resources/articles/how-to-manage-costs-and-demonstrate-roi-for-claude-code-on-google-cloud
- Record: https://forck.live/items/28403-manage-costs-and-demonstrate-roi-for-claude-code-on-google-cloud
- Subject: Claude
- Models affected: Claude Code, Claude, Fable, Sonnet

Anthropic published a guide for platform teams on controlling and measuring Claude Code spending on Google Cloud, built around a control, track and prove framework. Claude on Google Cloud uses consumption-based pricing, so the bill reflects how many tokens tasks consume and which models handle them, and agentic work like Claude Code spends more tokens per task than chat because it reads files, runs tools and reasons across a whole task. Anthropic says high-cost sessions are often high value, usually power users on new workflows, while waste tends to sit with heavy spenders using a model like Fable for routine work Sonnet can handle. Google Cloud's native tools include per-project billing, budget alerts, spend caps in preview, BigQuery exports, per-minute quotas and provisioned throughput. The self-hosted Claude apps gateway runs in the customer's Google Cloud project, signs developers in through an identity provider so every request carries a verified identity, and sets model allowlists per IdP group plus spend caps per user, group or organization by day, week or month. Claude Code warns developers in the CLI at 75% and 95% of a cap, returns 429 at the cap until the period resets or an admin raises it, and caps can be changed through the gateway's admin API.

## Evidence

Verbatim from https://claude.com/resources/articles/how-to-manage-costs-and-demonstrate-roi-for-claude-code-on-google-cloud:

> As organizations delegate more work to Claude Code, spend grows with it, and platform teams need a way to both control costs and understand impact. Inspired by a recent webinar (opens in new tab) with Google Cloud, we share how organizations using Claude Code can better track and optimize these considerations on Google Cloud, including three core levers: control, track, and prove.
> 
> Controls for managing Claude Code spend
> 
> Claude on Google Cloud has consumption-based pricing, so your bill is a readout of how much your developers are using Claude in your Google Cloud environment. Adoption drives usage; usage is what you pay for, and it’s also where the value shows up.
> 
> Your Claude Code bill is a product of how many tokens tasks consume and the models that handle them. Token consumption scales with task complexity and conversation length. Chat is a Q&A conversation. An agentic tool like Claude Code spends more tokens per task relative to chat because it's doing multistep work: reading files, running tools, and reasoning across a whole task. Meanwhile each model has its own price per token, so matching the model to the task is the other major cost control.

---

Record: https://forck.live/items/28403-manage-costs-and-demonstrate-roi-for-claude-code-on-google-cloud
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md