GCP Billing SKU Dictionary
Look up selected Google Cloud charge families in plain English: what triggers each, how it bills, how to cut it.
25 explainers across 10 services so far. Each covers a family of related SKUs, not one SKU; Google’s catalog runs to thousands.
Browse by service
Networking
5 explainersEgress, load balancing, and NAT: the charges that surprise people most.
BigQuery
5 explainersAnalysis, storage, streaming, and the APIs around them.
Cloud Storage
4 explainersObject storage classes, operations, retrieval, and early deletion.
Compute Engine
5 explainersvCPU, RAM, disks, licenses, and IP addresses: billed as separate SKUs.
Kubernetes Engine
1 explainerCluster management fees, and the Compute Engine charges underneath.
Cloud SQL
1 explainerInstance vCPU and RAM, storage, backups, and the higher HA rates.
Cloud Run
1 explainerRequest-based and instance-based billing, and the difference between them.
Cloud Logging
1 explainerIngestion and retention: the classic silently-growing bill.
Vertex AI
1 explainerGenerative model tokens on Agent Platform, which Google renamed from Vertex AI in 2026.
Support
1 explainerPercentage-of-spend charges that scale with everything else.
Want this done on your real bill?
Cloud Cost Audit: We go through your real AWS or Google Cloud bill and hand you a ranked list of what to cut first. From $1,500, fixed. Nothing paid upfront.
Why this exists
Google publishes a complete price list at cloud.google.com/skus. It is accurate, exhaustive, and answers a question almost nobody is asking. When an engineer sees Network Internet Egress from Americas to China on a bill, they do not want the rate, they want to know what in their system sent bytes to China, whether the amount is normal, and how to make it smaller. That is what these 25 write-ups are for.
Questions
What is a SKU on a Google Cloud bill?
A SKU is the smallest unit Google charges for. One virtual machine appears as several SKUs, vCPU, RAM, disk, license, IP address, because each is billed separately. That is why a bill grouped by service tells you far less than a bill grouped by SKU.
Where can I find the SKU ID for a charge?
In the billing export, sku.id and sku.description carry it. In the console billing reports, group by SKU. The description is the string worth searching for here; it is the human-readable name and the one that appears on invoices. Pasting a SKU ID finds a page only for the few IDs mapped so far from Google's own pricing pages.
How current is this, and does it show prices?
Each write-up says when its explanation was last checked against Google's documentation and links the pages it was checked against. Rates are separate: they appear only after a sync from Google's Cloud Billing Catalog API, and until then no page shows one. For current list prices, use cloud.google.com/skus.
Why does my egress cost differ between two SKUs that look the same?
Egress is priced by lane. "Network Internet Egress from Americas to China" and the same charge to Europe are separate SKUs at materially different rates, and both are separate again from inter-region and inter-zone traffic inside Google.
How is this different from cloud.google.com/skus?
Google's page is a searchable price list: SKU ID, description, region, rate. It tells you what something costs and never what caused it. These pages add the part that is missing, what triggers the charge, what it usually means when it grows, and what to do about it.
Related tools
BigQuery FinOps Query Pack
Copy-paste SQL for the BigQuery cost questions you need answered fast.
OpenCost Allocation Score
Score how much of your cloud spend you can assign to a team.
OpenCloud Storage Class Calculator
On Google Cloud, read and retrieval charges can outweigh what a colder class saves on storage.
OpenMore tools for: Billing data, allocation and governance, Pricing and commitments
Knowing what a SKU is beats not knowing. Knowing which of yours is growing is better.
Finitizer breaks your bill down to the SKU, tracks how each one moves week to week, and tells you which movements are usage and which are rate changes, across Google Cloud, AWS, and BigQuery.
See how Finitizer works