BillSnap

Catch runaway GCP spend
before it catches you.

Statistical anomaly alerts for every GCP project. We pull your existing billing export, compute a 14-day rolling z-score per SKU, and Slack you whenever something is unusual.

Start free trial → See how it works

$15/month per project · 14-day free trial · No card required to start

Why GCP's native budget alerts miss the actual problem

Native budget alerts fire when your total monthly spend crosses a fixed dollar threshold. They miss the real failure mode:

A Dataflow job that was spending $20/day yesterday
  is suddenly spending $400/day today.
You set your budget at $1,000/month -- the alert
  doesn't fire until day 25.
By then you've burned $9,500.

That story cost me $1,800 last quarter. BillSnap is what I built so it doesn't happen again.

Three things BillSnap does that budget alerts don't

σ

Cross-SKU z-score detection

14-day rolling baseline per service.sku. Anything more than 2σ above its own history fires a single daily digest — not a per-SKU alert storm.

Slack + email in < 24h

Pulls your billing export at 09:00 UTC daily. Anomalies hit your Slack and inbox before lunch — not 4 days too late, like threshold-based alerts.

🔒

Read-only, dataset-scoped IAM

You grant roles/bigquery.dataViewer on your billing dataset only. No project-wide access, no API keys to manage. Revoke with one bq command.

60-second walkthrough

Prefer reading? See the written walkthrough — same content, screenshots, copy-pasteable commands.

Pricing

$15 / month
per connected project
  • Daily anomaly detection
  • Slack + email alerts
  • Tunable z-score threshold
  • 30 days of alert history
  • Cancel anytime, no questions
Start 14-day free trial

No card required to start. We'll only ask for one when the trial ends.

Frequently asked questions

Why would I give you read access to my billing data?

You don't, exactly. You grant a dedicated service account (billsnap-reader) roles/bigquery.dataViewer on the specific dataset that holds your GCP billing export — nothing else. We cannot see other resources, cannot modify anything, and cannot read any other dataset. The full SQL we run is published here. Revoke at any time with one bq remove-iam-policy-binding.

What clouds do you support?

GCP only at launch. AWS Cost & Usage Report support is on the roadmap for the next quarter — vote for it via the in-app feedback button after you sign up.

How is this different from CloudZero, Vantage, Finout?

Those tools are FinOps platforms aimed at companies spending $100K+/month with 5-figure annual contracts and a dedicated FinOps team. BillSnap is $15/month per project, deliberately minimal, and aimed at indie builders and small startups whose biggest cost risk is a single runaway job.

What about false positives?

We default to z=2.0 with a $1/day floor and require 14 days of baseline before any SKU is eligible. One digest per project per day caps the noise at one notification, not ten. If alerts feel noisy, raise the threshold to 2.5 or 3.0 from the dashboard.

How long does setup take?

About three minutes. Sign in with Google, paste your project ID and billing-export table name, copy two gcloud commands, click Verify access. Real customers have hit "Project connected ✓" in under three minutes. See the illustrated walkthrough for the full sequence, or the billing-export guide if you don't have GCP billing export enabled yet.

Can I use it for multiple projects?

Yes. $15/month per project. Each project gets its own configuration (threshold, min-cost floor, Slack channel, email recipients).

What happens during the trial?

14 days, full functionality, no card required. We email you on day 13 to ask if you'd like to keep going. If you say nothing, the trial expires and detection stops; no charge.

Refunds?

30-day no-questions refund for your first month. See refund policy.

Are you SOC 2 / HIPAA / ISO 27001?

No. BillSnap is solo-built and appropriate for indie projects and small-startup workloads — not regulated industries. We do not store your raw billing rows; only the SKUs that triggered an alert and the metadata needed to render the dashboard.

Can I see the code?

The detection SQL is published here. The rest of the stack (Cloud Run + BigQuery + Pub/Sub + Firestore) is described in the architecture page. The 5-minute walkthrough and illustrated docs cover the customer-facing surface.

Stop finding out about cost spikes from your monthly invoice.

14 days free, no card, three-minute setup.

Start free trial →