Follow the history
Trace a table back to recent SQL and the account that ran it. Understand its use before making a change.
A clearer view of your data
Your warehouse.Minus the waste.
Find the GCP BigQuery tables nobody queries anymore. Turn your job history into a clear, actionable report — delivered right to Slack.
Free while in beta. No credit card, no sales call.
Warehouse / overview Find the signal
Active tables Worth a closer look
The quiet corners add up.
Make them visible.Built for the people behind the pipelines.
Read-only access
Reports in Slack
You stay in control
01 / From data to decisions
Less detective work.
More useful answers.
See what has gone quiet, how long it has been idle, and what it costs to keep. Start with the evidence. Decide what to do next.
| Table | Type | Days unused | Est. daily cost |
|---|---|---|---|
| analytics.events_legacyLast touched over four months ago | Base table | 127 days | $2.40 |
| staging.campaign_backupA snapshot that stayed behind | Base table | 93 days | $0.86 |
| sandbox.experiment_v2The experiment moved on. The table did not. | Base table | 45 days | $0.32 |
Put idle storage in context
Estimated daily storage costs help you prioritize which tables deserve a closer look.
Keep your team in the loop
Get scheduled unused-table reports in Slack, where your team already works.
02 / A small setup. A clearer picture.
Connect. Observe.
Make room for better.
No agent to install. No changes to your pipelines. Just a connection to your project and a place for the reports to land.
01
Connect your project
Upload a GCP Service Account JSON key and choose your target project and region. We verify the connection before saving it.
02
Bring the report to Slack
Add a Slack incoming webhook. We will let you know when your first report is ready and send regular updates.
03
Review with confidence
Explore idle tables, inspect their query history, and decide what belongs in your warehouse. Every change stays in your hands.
03 / Transparency, by design
Your project.
Your rules.
Connecting a warehouse is a matter of trust. Here is exactly what we access, what we keep, and how you stay in control.
We read metadata. Your tables stay untouched.
We query INFORMATION_SCHEMA for job history and table metadata. We never read the contents of your tables, modify your data, or delete tables for you.
Query history includes SQL and account emails.
Collected job history includes the query's SQL text and the email of the account that ran it. These help you understand who last touched a table and how it was used.
Your key is stored with your connection.
The GCP Service Account JSON key you upload is stored in our database. We use it to read your project's metadata. You can revoke the key in GCP Console at any time.
Keep the history. Delete it when you choose.
We retain collected history for as long as your connection exists, so longer idle periods stay visible. Deleting a connection removes its key and queues deletion of all collected data for that connection.
A little less noise. A lot more clarity.
Know what you are keeping.
Connect a project. Let the history speak for itself.