SupportedDatabasesSee your Snowflake bill per warehouse and per person
Track the billed cost of a Snowflake account every day, split by warehouse and by user, with Cortex AI per person and idle time shared fairly.
Highlights
Snowflake's own numbers
The bill comes from the usage view Snowflake keeps for this, already in your billing currency. No credit math, and nothing to drift away from your invoice.
Down to the person
Each day's compute is split per warehouse by metered credits, then per user by the credits their queries used.
Idle time, shared fairly
Time a warehouse runs with no queries stays on that warehouse, and gets spread over the teams that use it.
What you get from Snowflake
- Warehouse compute per warehouse and per user
- Idle time shared across the teams that use each warehouse
- Cortex AI functions per user
- Storage, data transfer, Snowpipe, serverless and every other service
- Warehouses and users you can hand to a team
- Idle warehouse recommendations with an estimated saving
What it doesn't do yet
- The last 3 days. Snowflake publishes cost up to 72 hours late, and RootSpend fills them in on later syncs.
- Other accounts in your Snowflake organization. Connect each account on its own.
Who ran up the warehouse bill?
Snowflake bills compute by the second and storage by the terabyte, with a growing list of serverless features on top. The invoice gives you the total. It doesn't say which warehouse, which team or which person.
What you get
RootSpend reads the billed cost of your account from USAGE_IN_CURRENCY_DAILY, the view Snowflake keeps for this, already priced in your billing currency. Then it splits compute two ways:
- Per warehouse, by the credits each one metered that day.
- Per user, by the credits each person's queries used.
Whatever credits are left on a warehouse is idle time. That cost stays on the warehouse and gets spread over the teams that use it, so nobody pays for someone else's idle time, and nothing gets lost.
Catch the idle warehouse
When a warehouse spends a big share of its time running with no queries, RootSpend flags it with the evidence and an estimated monthly saving. Usually the fix is a lower auto suspend setting. RootSpend never changes the setting itself. Read more in our guide to idle warehouses.
Snowflake questions
Through Snowflake's SQL API, signed in with a key pair. You run a short setup script that creates a dedicated user and a read only role, then paste the account identifier, account locator, user name and private key into RootSpend.
No. The role only gets Snowflake's own usage and metering views, and permission to use one small warehouse to read them. Your databases, schemas and tables are off limits.
Each day's warehouse bill is split by the credits each warehouse metered, then by the credits each user's queries used. Credits nobody used are idle time, and they get shared across the teams on that warehouse.
A tiny amount. It's a few small queries on the warehouse you choose, and you'll see that cost in RootSpend like everything else.
Want to see your Snowflake spend split by team?
RootSpend is opening to a first group of teams soon. Join the waitlist, or book a demo and we will show you on sample data.
Opening soon. The waitlist gets in first.