Anavsan Explore
All terms Start Free Trial

Terminology › APEX loop

What is the Enforcement Desk?

The Enforcement Desk is the accountable worklist in APEX. It is not a warehouse leaderboard. It is a short list of inefficiencies someone can close.

The Enforcement Desk is Anavsan’s ranked worklist of addressable Snowflake waste. Every row carries a mechanism, a counterfactual dollar figure, an owner (or an honest “needs owner”), an exact fix, and a status that closes when the underlying metric recovers — through your own review process, not a silent warehouse alter.

Key takeaways

Rank by waste. A busy, efficient warehouse can be expensive and still not deserve a row. The Desk ranks the gap versus an efficient configuration.
Recurring only. One-off spikes and brand-new accounts still building a baseline stay off the list.
The fix is specific. Copy-pasteable SQL or a warehouse setting, with risk — not “consider right-sizing.”
You deploy it. Findings leave as pull requests in your repository. Anavsan does not reach into production and change a setting because it thought that would help.

Waste, not spend

Most tools rank by spend, which means your biggest, busiest, most valuable warehouse sits at the top forever. The Desk ranks by a counterfactual: what would this object have cost configured efficiently, versus what it billed? That difference is the addressable number. It is the only thing that earns a row. See cost accountability for why that number has to travel with an owner.

What every row has

  • Mechanism in plain language (idle auto-suspend, remote spill, refresh storm)
  • Evidence across 7-, 14-, and 30-day windows, including how completely hours were attributed
  • Dollar figures from your configured credit rate — never invented, never silently swapped for credits
  • Owner from tags and roles, or “needs owner” with usage as a suggestion, not a verdict
  • Exact change, risk, and projected saving from deterministic arithmetic — the AI explains; it does not invent the number

How it closes

The item moves through your change process: open, pending, resolved, with the PR link. Findings can be archived with a reason — a deliberate “we know, and we are not doing it” that stays distinct from “the waste stopped.” When a fix lands and the metric returns to its normal band after a hold period, the finding resolves itself. Nobody self-reports a win. That is Enforce as a screen, not a slogan.

In a FinOps week

Monday: six rows, not sixty. Tuesday: objects that trace to a generic admin role are grouped as needing an owner. Thursday: Ask APEX answers a question with no tile, grounded on Desk findings. Quarter end: the savings slide is an audit trail of what was found, recommended, pushed, and closed. More narrative is in the APEX product brief.

APEX

The engine the Desk sits inside.

Read →

Cost Accountability

The outcome each row is designed to produce.

Read →

Trace → Assign → Prove → Enforce

The loop behind every status.

Read →

Private Knowledge Graph

How owners and similar fixes are remembered.

Read →

Frequently asked questions

Anavsan’s waste-ranked worklist. Each row has a mechanism, dollar figure, owner, exact fix, and a status that closes when the metric recovers.
Spend ranking keeps valuable, efficient warehouses on top forever. Waste ranking shows the gap versus an efficient configuration for the same work.
No. Fixes go through your pull request and review process. Anavsan does not auto-alter production warehouses.
The Desk says ownership is unknown and shows roles and service accounts that drove usage as suggestions. It does not auto-assign a person from a guess.