BigQuery bill autopsy
What is your BigQuery bill made of? Run one read-only query in your own console, paste the result here, and see who spends, what to fix first, and the quotas that stop a runaway query. Free, no sign-up — and nothing leaves your browser.
1. Run this query in BigQuery
Open the BigQuery console in the project that gets the bill and run it there (it reads only job history — who ran what and what it billed — never your tables, and returns no query text). You need BigQuery Resource Viewer or Admin on the project. It costs BigQuery's 10 MB minimum.
2. Paste the result
In the results, choose Save results → CSV (or copy them) and paste or upload here.
This page has no server behind it: the result is read and analysed by your browser only.
Why BigQuery bills surprise people
- On-demand pricing bills bytes read, not rows returned: a
SELECT *withLIMIT 10still reads every column of the whole table. - Dashboards re-run queries on every view and filter change, so one popular Looker Studio report can outspend a whole team.
- Nothing stops a runaway query by default. BigQuery's custom quotas (per user and per project, per day) and
maximum_bytes_billedon jobs do — if you set them.
PipeKeel's Cost Guard watches every job in your project every 15 minutes — PipeKeel's own, Looker Studio's, people's — alerts on spikes and daily budgets, and tells you what to fix. It runs with its own narrow, opt-in permission and never reads your data or your query text.