Every project and folder, one total
CostMon reads directly from your GCP FOCUS billing export in BigQuery, so a spend total that's split across a dozen projects and folders finally rolls up into a single normalized number.
GCP cost monitoring
CostMon reads your GCP billing export straight from BigQuery and turns scattered project- and folder-level spend into one normalized daily view — so a forgotten BigQuery job or an expiring committed-use discount gets caught before the invoice lands.
GCP's own billing console is built around one project or one billing account at a time — the moment spend is spread across a dozen projects and folders (which it always is), there's no single place that shows the total, let alone catches a runaway BigQuery scan or an egress spike while it's still cheap to fix. Committed-use discounts silently expire, orphaned Compute Engine disks stack up, and by the time it all reconciles onto the invoice, the spend is already sunk.
Why CostMon
CostMon reads directly from your GCP FOCUS billing export in BigQuery, so a spend total that's split across a dozen projects and folders finally rolls up into a single normalized number.
See CUD coverage and expiration alongside daily spend, so a discount that's about to lapse — or usage that's drifted off it — shows up before it costs you full on-demand price.
A daily, service-level view surfaces a runaway BigQuery scan or an unexpected egress spike days after it starts, not a month later on the bill.
CostMon connects with a service account scoped to bigquery.dataViewer and jobUser on your billing export only — read-only, and it never touches your workloads or production data.
Getting started
Grant a read-only service account bigquery.dataViewer and jobUser on the BigQuery dataset holding your FOCUS-formatted billing export.
The export is queried on a schedule and mapped into the same normalized model as every other provider you connect.
Open a daily, project- and service-level view of GCP spend and catch a runaway job or an expiring discount weeks before it lands on a bill.
FAQ
Through a read-only service account key scoped to bigquery.dataViewer and bigquery.jobUser on the dataset holding your FOCUS-formatted billing export — CostMon never requests access to your workloads or production data.
No — CostMon reads the same FOCUS billing export and normalizes it alongside AWS, Azure, and every other provider you connect, so GCP spend sits in one daily view instead of its own console.
Yes — the billing export already carries project and folder detail, and CostMon preserves it, so you can break spend down by project, folder, service, or SKU.
Spend syncs in with its underlying FOCUS detail intact, including discount and commitment fields where GCP's export provides them, so CUD coverage stays visible next to raw spend.
A flat monthly rate per plan — never a percentage of your GCP bill or the savings CostMon helps you find. Free includes 2 connectors; Professional and Enterprise include unlimited connectors.
Connectors
AWS, GCP, and Azure for cloud; Anthropic, OpenAI, Amazon Bedrock, Vertex AI, and Helicone for AI usage; Snowflake and Databricks for the data cloud; Datadog, GitHub, and Vercel for the rest of the stack — plus CSV import for any tool without a native connector. 14 connectors, all normalized into the same unified view.
Connect your first providers in minutes and give finance and engineering one number they both trust. Flat pricing — never a percentage of your bill or your savings.