Data Warehouse Cost Calculators
3 free tools · no login · nothing uploaded
Snowflake and Databricks are both billed in units that do not map cleanly onto the work you asked for, and both have a specific way of costing more than people expect.
Snowflake bills a warehouse for being awake, not for executing queries. A warehouse serving a steady trickle of short queries with a ten-minute auto-suspend never gets to sleep, so it bills a full day for perhaps a couple of hours of work. That idle share is invisible on a credit report, which shows only the total, and it is usually the largest single line in a Snowflake bill.
Databricks bills DBUs — and your cloud provider separately bills the virtual machines those DBUs ran on. The second invoice is normally the larger one, so a budget built from the Databricks bill alone captures roughly a third of the real cost. On top of that, the same notebook run on All-Purpose compute instead of Jobs compute costs several times more for identical work.
Both calculators here take your own contracted rate rather than publishing a list price. Neither vendor publishes machine-readable rates, both are contract-specific, and almost every customer of any size pays something other than list — so a calculator built on a published number would be quietly wrong for most of the people reading it.
3 tools in data platform cost
Snowflake Cost Calculator
Credits burn by the second your warehouse is awake, not while it works.
Model Snowflake compute from warehouse size, query hours, auto-suspend delay and concurrency scaling — at your own contracted credit price, not a list rate you do not pay. Shows how much of the bill is idle time waiting for auto-suspend.
Warehouse Cost Translator
What would this BigQuery workload cost on Snowflake or Databricks?
Paste real BigQuery job history and get a modelled range for the same workload on Snowflake and Databricks. The shape comes from your data; the slot-to-credit bridge is an assumption, shown as a dial and reported as a range.
Databricks Cost Calculator
The DBU line is a third of the bill. This prices the other two thirds.
Model Databricks DBUs and the cloud VMs underneath them together, compare All-Purpose against Jobs compute on the same workload, and see what Photon and spot instances change. Uses your own DBU rate and instance price.
Other categories
One warehouse modelled, or the whole data estate measured.
Finitizer joins Snowflake credits and Databricks DBUs to the cloud spend underneath them, so a job has one cost rather than two invoices — and applies the same treatment to BigQuery and Redshift alongside them.