Know which warehouse and which person drives your Snowflake bill
Track Snowflake costs every day per warehouse and per user, share idle time fairly between teams, and catch idle warehouses before the invoice.
What you walk away with
- Daily Snowflake cost that matches your invoice
- Compute per warehouse and per user
- Idle time shared across the teams on each warehouse
- Idle warehouse recommendations with an estimated saving
The month end surprise
Most Snowflake overruns aren't one big mistake. A warehouse gets resized for a backfill and never shrinks back. A new dashboard refreshes every five minutes. A warehouse sits up all day waiting for queries that come once an hour. Nobody notices until the invoice arrives.
What RootSpend gives you
RootSpend reads your billed cost from Snowflake's own usage view every day, then splits compute per warehouse and per user. You see:
- what each warehouse cost, and who ran the queries
- Cortex AI usage per person
- how the month is tracking against your budget
- a flag the day spend jumps well above normal
- a recommendation when a warehouse spends a big share of its time idle
That last one is often the quickest win. Usually the fix is a lower auto suspend setting.
More on the Snowflake connector.
Tools this works with
Frequently asked questions
Only a dedicated user and a read only role, created by a short setup script. No agents and no stored procedures.
Each day's warehouse bill is split by the credits each warehouse metered, then by the credits each user's queries used. Whatever is left is idle time, and it gets shared across the teams that use that warehouse.