CostMonStart free

GCP cost monitoring

Catch GCP overspend across every project

CostMon reads your GCP billing export straight from BigQuery. It turns spend from many projects into one daily view. A runaway BigQuery job or an egress spike shows before the invoice lands.

Start freeSee how it works
GCP BigQuery billing export, live today

The GCP billing console works on one project or one billing account at a time. Spend soon spreads across a dozen projects. No single page shows the total. Nothing warns you about a runaway BigQuery scan or an egress spike while the fix is still cheap. The spend is sunk by the time the invoice arrives.

Cost anatomy

What actually drives your GCP bill

Committed-use discounts need steady usage
A committed-use discount (CUD) gives the discounted rate only while usage matches the commitment. If usage falls below it, or the term ends, spend moves toward full on-demand price. CostMon does not track CUD end dates. A total that rises for this reason shows in your daily spend.
BigQuery on-demand bills by TB scanned
On-demand BigQuery pricing bills per TB scanned, regardless of how many queries run. A query missing a partition filter can scan an entire multi-terabyte table for a result that only needed a day's worth of rows.
Orphaned disks and static IPs
A persistent disk or a reserved static IP bills on its own meter. It keeps billing after you delete the instance, until someone removes it.
Egress and inter-region transfer
Network egress to the internet, and transfer between regions, bill on their own per-GB meter, distinct from and additional to compute and storage. The charge tracks the number of GB moved. Nothing in the compute or storage line shows it.

Alerts

How CostMon warns you about GCP spend

CostMon's default rule watches every service on your account from the day you connect it. An alert always shows up in your CostMon feed. Add an email, Slack, or webhook channel to send it somewhere else too.

Anomaly rulesource = gcp, service = BigQuery

A query missing a partition filter, scanning an entire multi-terabyte table in one run.

Budgetsource = gcp

A monthly budget on total GCP spend catches the total rising. A committed-use discount that ends causes that rise.

Sample alert, illustrative

From
alerts@costmon.com
Subject
CostMon alert: Anomaly: gcp / BigQuery spend spike
Anomaly: gcp / BigQuery spend spike

gcp / BigQuery was $430.00 on 2026-06-21 — 79% above its 14-day average of $240.00.

Severity: warning
Occurred on: 2026-06-21

To find what to cut, the recommendations list flags idle spend and commitment gaps to review.

Why CostMon

Built for GCP spend, from day one

Every project, one total

CostMon reads directly from your GCP FOCUS billing export in BigQuery. Spend split across a dozen projects rolls up into one normalized number.

Spend by project, service, SKU and region

Each cost row keeps its project, service, SKU, region and charge category. You can split a project's bill into the services and SKUs behind it.

BigQuery and egress spikes, caught early

The daily service view shows a runaway BigQuery scan or an unexpected egress spike days after it starts, well before it lands on the bill.

Read-only, billing-export-scoped credentials

CostMon connects with a service account scoped to bigquery.dataViewer and jobUser on your billing export only. Those two roles let it query the export. They give no read access to your other datasets.

  • Per TB scannedBigQuery on-demand pricing bills by data scanned
  • ~16 daysearlier than the invoice
  • BigQueryGCP billing export query, daily

Getting started

From API key to first alert, for GCP

  1. 01

    Point CostMon at your billing export

    Grant a read-only service account bigquery.dataViewer and jobUser on the BigQuery dataset holding your FOCUS-formatted billing export.

  2. 02

    CostMon syncs and normalizes

    The export is queried on a schedule and mapped into the same normalized model as every other provider you connect.

  3. 03

    See the total, then get the alert

    Open a daily view of GCP spend by project and service. An unfiltered BigQuery scan shows up as a jump on the BigQuery line, which trips a rule.

FAQ

Common questions about the GCP connector

How does CostMon connect to GCP?

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.

Does CostMon replace the GCP Billing console?

No. CostMon reads the same FOCUS billing export. GCP then shows beside AWS, Azure and your AI providers on a single daily chart.

Can CostMon see spend across multiple projects?

Yes. The billing export carries project detail, and CostMon keeps it. You can break spend down by project, service, SKU or region.

Does CostMon track committed-use discounts?

Not by end date. CostMon does not read commitment IDs or expiry dates from the export. It does show total GCP spend each day, so a lapsed discount shows as a rising total. It also has commitment coverage and utilization recommendations.

What does the GCP connector cost?

A flat monthly rate per plan. It's 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

Cloud, AI, and SaaS: all in one place

AWS, GCP, and Azure for cloud. Anthropic, OpenAI, Amazon Bedrock, Vertex AI / Gemini, and Helicone for AI and LLM spend. Snowflake and Databricks for the data cloud. Datadog, GitHub, and Vercel for the rest of the stack. Add CSV import for any tool without a native connector. That's 14 connectors, all normalized into the same unified view.

Connect it. Get the first alert.

Connect a provider and CostMon builds a daily baseline for it. From there, a spike reaches your team as an alert.

Start freeSee how to connect a provider
Esc