What it costs
What a warehouse bill actually measures
An invoice tells you what you spent, never what you bought. The gap between the two is where most of the savings are.
2 minute read
Every warehouse invoice is a single number with a shape nobody can see. It is the sum of compute time, and compute time is the sum of queries, and queries belong to people, dashboards, pipelines and jobs that nobody has mapped to the line item. So the conversation about cost starts at the wrong end: somebody notices the bill went up twenty per cent, and nobody can say which twenty per cent.
The bill is a measure of time, not value
Warehouses meter the resource they allocate, not the work you got out of it. A warehouse left running between two queries bills for the gap. A model that reads a hundred times more data than it needs bills for all of it. A dashboard that refreshes every fifteen minutes for an audience that opens it on Monday bills for the other six days and twenty-three hours. None of that is visible on the invoice, and all of it is visible in the metadata the warehouse already keeps.
The questions the invoice cannot answer
- Which models cost the most to build, in money rather than seconds?
- What share of the bill is produced by objects nothing downstream reads?
- Which queries would cost materially less with a different clustering key, and by how much?
- What did the last schema change cost in re-processing?
- If you turned off the least-read tenth of the estate, what would stop working?
Every one of those is answerable from query history and account usage views. None of them is on the invoice. That is not a shortcoming of the vendor — an invoice is a billing document — but it does mean that reading the bill harder will never get you there.
Attribution is the whole exercise
The useful unit is not dollars per month. It is dollars per object, per model, per dashboard, per team — because those are the things somebody can decide about. A figure attached to a decision is worth more than a bigger figure attached to nothing. The practical test of a cost tool is whether it can hand you a sentence of the form "this specific thing costs this much and here is what breaks if it stops", and most of them cannot.
A cost figure you cannot act on is a mood, not a measurement.
More on what it costs
Run this against your own estate
Gecko reads metadata and query history — never the rows in your tables — and tells you what it found.
Get started