CostCap reads your GCP billing export, learns what normal looks like, and emails you when it isn't — plus a Monday digest with your spend, forecast, and the week's biggest movers. No dashboards to babysit.
Free forever for one billing account · no credit card
Start coarse in minutes, add full service-level detail whenever you're ready — or let us host it. Every path is read-only and revocable from your console.
One click connects your billing account and spend telemetry starts flowing. Spike alerts and forecasts from today, updated every ~20 minutes.
One script sets everything up in your Google Cloud project. Flip one export toggle and full service-level history flows in. The path for teams who keep data in-house.
Zero setup on your side: we spin up a private, isolated tenant for your billing export and Google delivers your data straight into it. You flip one toggle — done. Built for teams without a resident cloud person.
Whichever door you pick, the product is the same: baselines learned, anomalies flagged, month-end forecast, Monday email. We can never touch your workloads, resources, or code — the most any path does is read billing data (Instant additionally sets up the budget alerts you approve, visible in your console and deletable anytime).
Last week vs the week before, month-to-date, top services and projects with their deltas, and every anomaly — one calm email your whole team can read.
Instant mode watches your spend rate — a burn that triples its baseline triggers an alert within the hour, not tomorrow. Plus the leaked-key signals: a service or a whole project going from $0 to billing.
Run-rate forecast of where this month lands, plus alerts at 50 / 90 / 100% of a budget you set — and an early warning the moment you're merely on pace to blow it.
Spend broken down by service and project, tracked daily. See exactly which project's BigQuery habit is growing.
Every digest opens with a short executive brief: what moved, why it matters, and the first thing to check — numbers included, jargon left out.
Email always; Slack when you want the whole channel to see it. Paste one webhook URL and every spike, new-service, and budget alert lands where it gets acted on.
Billing data never leaves your BigQuery dataset except as daily aggregates. We store totals per service per day — no resource names, no logs, no code.
The whole integration is one IAM grant you can read in a sentence.
Only the dataset holding your billing export, via roles/bigquery.dataViewer granted to costcap-reader@billhound-app.iam.gserviceaccount.com.
Daily cost aggregates per service and project. Never resource names, ARNs, logs, source code, or anything from your actual workloads.
Revoke the grant in your console — access ends instantly. Disconnect in the app and we delete every aggregate we hold.
Built for solo devs and small teams — the people the horror stories actually happen to.
Not to get started — Instant mode monitors spend with zero setup in your environment. The export unlocks full detail: service and SKU breakdowns, credits, and history (it's the only way Google exposes that data — every GCP cost tool uses it). It's free to enable, the data lives in your project (or your managed tenant with us), and a US or EU multi-region dataset backfills from the start of the previous month.
Honest answer: Google's export lags real usage by a few hours up to a day — that's a GCP limit every tool inherits, including Google's own budgets. CostCap syncs every 6 hours and flags anomalies the same day the data lands, which is typically a day or more before you'd otherwise notice.
We cap surprises, not resources: CostCap is read-only by design, because anything with the power to delete your billing link should be code you control. If you want a true hard stop, our kill-switch guide walks through Google's official recipe (budget → Pub/Sub → function) — CostCap is the early-warning layer in front of it.
roles/bigquery.dataViewer on one dataset — the one holding your billing export. It cannot see other datasets, your resources, your code, or your data. Revoke it in the console and access ends immediately.
We run the queries in our project, on our bill. Billing exports are small; your dataset never gets charged for our reads.
Pro watches unlimited billing accounts, each with its own digest section and baselines. Reseller (sub-account) exports work too — if you hit a weird schema, email us and we'll make it work.
monitored in minutes · read-only · free for one billing account