Search costs
One box, every dimension. A word (autopilot, neo4j, gemini), a service, a cluster, a workload — or paste a bucket link and see what it costs.
7 days
14 days
30 days
90 days
This month
Last month
12 months
last 30 complete days · complete through 2026-11-16
How to read this page — Search costs
One box over every dimension of the bill. Explore needs you to pick the dimension that holds the answer; search does not — type a word and every service, SKU, cluster, namespace, workload, region and named resource whose text contains it is added up together.
- A word, not a dimension
- <code>autopilot</code> is not a dimension — it is a word inside eight SKU names across two regions. Searching it adds them up. The same for <code>neo4j</code>, <code>gemini</code>, <code>egress</code>.
- A bucket, a disk, an instance
- Paste <code>gs://bucket-name</code>, a console URL, or the export's own <code>//storage.googleapis.com/…</code> — all three reduce to the name and match the per-resource ledger.
- Counted once
- A row matching on two columns at once — <code>kubernetes</code> hits the service AND several SKUs — counts once in the total, so the number never double-counts.
- Then hand off to Explore
- Every matched value links into Explore already filtered to it. Search finds the thing; Explore explains it.
What this page will not tell you
- Anything the ledger does not store: arbitrary resource labels and tags are dropped on ingest, so you cannot search by a label you set yourself — only the five Kubernetes ones.
- Named resources are kept for 35 days, so a bucket search over a longer period covers only the recent part of it. The dimensions themselves go back as far as the ledger does.
- Free text matches text. A search for a number, or for a word that appears in no name, finds nothing even though the money is there under a different word.
reading the cost ledger…