CostMonStart free

Snowflake cost monitoring

Catch Snowflake credit burn before the invoice does

CostMon reads Snowflake's organization usage views. It turns daily credit use into one view by service type, usage type and account. A warehouse-compute line that climbs from repeated resumes or oversized warehouses stands out within days of the change.

Snowflake organization usage views, live today

Snowflake warehouse billing has two rules that are easy to get wrong. Both stay hidden until the invoice arrives. Every resume from auto-suspend bills a minimum charge, however short the query is. Each step up in warehouse size roughly doubles the credit rate. A dashboard that polls every few minutes, with a short auto-suspend timeout, pays that minimum again and again. Snowflake's usage views report credits for the whole org, with a reporting lag. The pattern can run for a month before anyone sees it.

Cost anatomy

What actually drives your Snowflake bill

60-second minimum per resume
Each time a warehouse resumes from auto-suspend, Snowflake bills at least 60 seconds of compute. This holds even if the query that woke it ends in a few seconds.
Per-second billing after that
Past the first minute, billing runs per-second until the warehouse suspends again. The resume minimum, rather than the query itself, is usually what a chatty workload pays for.
Warehouse size roughly doubles cost
Each step up in warehouse size roughly doubles the credits billed per hour. Right-sizing is as much a lever on the bill as auto-suspend.
Auto-suspend timeout, tuned wrong
A short auto-suspend timeout on a bursty workload forces repeated resumes. A BI dashboard that refreshes every few minutes is one example. Each resume pays its own 60-second minimum. The "savings" setting can cost more than a longer timeout.
Serverless features, separate meters
Snowpipe, serverless tasks, Search Optimization and Automatic Clustering run on Snowflake-managed compute. Each bills on its own credit meter. These meters add to warehouse compute.

Alerts

How CostMon warns you about Snowflake spend

CostMon's default rule watches every service on your account from the day you connect it. An alert always shows up in your CostMon feed. Add an email, Slack, or webhook channel to send it somewhere else too.

Anomaly rulesource = snowflake, service = COMPUTE

A bursty dashboard polling every couple of minutes, paying the 60-second resume minimum over and over.

Budgetsource = snowflake

A monthly budget on total Snowflake credit spend catches a warehouse running oversized for its workload.

Sample alert, illustrative

From
alerts@costmon.com
Subject
CostMon alert: Anomaly: snowflake / COMPUTE spend spike
Anomaly: snowflake / COMPUTE spend spike

snowflake / COMPUTE was $540.00 on 2026-07-09 — 80% above its 14-day average of $300.00.

Severity: warning
Occurred on: 2026-07-09

To find what to cut, the recommendations list flags idle spend and commitment gaps to review.

Why CostMon

Built for Snowflake spend, from day one

Daily sync beats a lagging org rollup

CostMon syncs Snowflake's organization usage views on a schedule. A trailing window corrects late data. Credit burn is visible each day. You do not wait weeks for it to reconcile.

Warehouse compute, split from the serverless meters

CostMon splits spend by service type, usage type, account and region. Warehouse-compute credits stay apart from the serverless meters that bill beside them. You see a climb early and know which account and meter to open in Snowsight.

One number for finance and engineering

Stop reconciling Snowflake's usage views against a spreadsheet. Everyone looks at the same normalized credit spend, broken down the same way, next to the rest of your stack.

Read-only, usage-view-scoped credentials

CostMon connects with a Programmatic Access Token scoped to Snowflake's built-in ORGANIZATION_USAGE_VIEWER role. It's read-only and never touches your warehouses, data, or query results.

  • 60sminimum credit charge every time a warehouse resumes
  • 2×credits per hour roughly double with each warehouse size step up
  • Usage viewsSnowflake organization usage pull, daily

Getting started

From API key to first alert, for Snowflake

  1. 01

    Connect with a Programmatic Access Token

    Add a PAT scoped to the built-in ORGANIZATION_USAGE_VIEWER role. CostMon never touches your warehouses, databases, or query results, only usage views.

  2. 02

    CostMon syncs and normalizes

    CostMon pulls daily credit spend from ORGANIZATION_USAGE.USAGE_IN_CURRENCY_DAILY. It splits it by service type, usage type, account and region. Those rows join your other sources in one cost table.

  3. 03

    See the credits, then get the alert

    Open a daily view of Snowflake credits by service type and account. Repeated warehouse resumes push the COMPUTE line up, and a rule fires. Then use Snowsight to find the warehouse.

FAQ

Common questions about the Snowflake connector

How does CostMon connect to Snowflake?

Through a Programmatic Access Token scoped to Snowflake's built-in ORGANIZATION_USAGE_VIEWER role, read-only and scoped to usage and billing views. CostMon never requests access to your databases, warehouses, or query results.

How often does Snowflake cost data sync?

On CostMon's regular background schedule, reading a trailing window to account for Snowflake's own reporting lag on organization usage views. Recent days get corrected in place as more complete data arrives, rather than staying wrong.

Can I see Snowflake spend broken down by individual warehouse?

Not by warehouse name. CostMon reports at the level Snowflake's organization usage views give: service type, usage type, account and region, for each day. That shows warehouse-compute credits climbing. It also keeps them apart from the serverless meters. To find the exact warehouse, open Snowsight's warehouse metering views. CostMon tells you early that something moved, and in which account. Snowflake tells you which warehouse.

Does CostMon replace Snowflake's own usage views?

No. CostMon reads the same organization usage views. Snowflake credits then sit beside your cloud and AI bills, so you need no separate login. Snowflake's warehouse metering views stay the place for detail on each warehouse and query.

What does the Snowflake connector cost?

A flat monthly rate per plan. It never charges a percentage of your Snowflake spend or the savings CostMon helps you find. Free includes 2 connectors; Professional and Enterprise include unlimited connectors.

Connectors

Cloud, AI, and SaaS: all in one place

AWS, GCP, and Azure for cloud. Anthropic, OpenAI, Amazon Bedrock, Vertex AI / Gemini, and Helicone for AI and LLM spend. Snowflake and Databricks for the data cloud. Datadog, GitHub, and Vercel for the rest of the stack. Add CSV import for any tool without a native connector. That's 14 connectors, all normalized into the same unified view.

Connect it. Get the first alert.

Connect a provider and CostMon builds a daily baseline for it. From there, a spike reaches your team as an alert.

Esc