Snowflake cost accountability is the ability to name who owns a credit event, what should change, and whether credits actually fell after the change. Dashboards show spend. Accountability produces a closable work item. It is the outcome workload governance is built to deliver.
Key takeaways
Why accountability stalls after detection
Query History and warehouse metering answer “what spent.” They do not answer who can change the dbt model, whether a resize is safe on a shared BI cluster, or whether last quarter’s rewrite still holds. Findings from Anavsan assessment sessions show the same pattern: rapid ownership after detection is rare, validation is often manual or in production, and storage growth is the least-owned cost area.
The cost of that stall never appears as a line item. It appears as a savings programme that plateaus after easy wins, and a FinOps function that slowly turns into a reporting function.
Not showback, not a resource monitor
| Practice | What it does | What it does not do |
|---|---|---|
| Showback / chargeback | Allocate consumption to a team or project | Name who can change the SQL or warehouse |
| Resource monitors / budgets | Notify or cap spend | Assign, simulate, or prove a cheaper runtime |
| Cost accountability | Owner + change + verified credit delta | Replace FinOps culture — it operationalizes it on Snowflake |
What accountability requires
Four facts, not four tools: a workload identity (not only a warehouse name), an owner who can act or an honest “needs owner,” a proposed change with risk, and a before/after credit comparison. That is Trace, Assign, Prove, Enforce stated as an outcome.
Anavsan’s Enforcement Desk is built so every row carries those four facts. If ownership is not knowable, the row says so and shows usage as a hint, not a verdict.
How to measure it
Ask four questions in a review. How many expensive recurring workloads have a named owner? How many proposed changes were simulated before production? How many closures have a credit delta from data, not a checkbox? How many “fixed” patterns returned within 90 days? If you cannot answer, you have visibility. You do not yet have accountability.
Related terms
Workload Governance
The operating discipline that produces accountability.
Read →Enforcement Desk
The worklist where accountability is visible as a row.
Read →Trace → Assign → Prove → Enforce
The loop that turns a spike into a closed record.
Read →APEX
The engine Anavsan uses to run accountability continuously.
Read →