Snowflake is the deep worked example of the APEX loop. Anavsan is the Workload Governance Platform for Snowflake and BigQuery. Powered by APEX, it traces waste (not spend) to a workload and owner, assigns the fix, enforces a decision through your review process, and proves closure from the data.
200+ Snowflake signals feed the Private Knowledge Graph. Credits, warehouses, queries, storage, and Cortex get an owner — then a decision, then proof.
Feature pages nest under this hub — not as peers of the APEX engine. Warehouses, storage, Cortex, and the Native App.
Trace credit waste to the query and warehouse that caused it. Assign the owner. Enforce the fix through your review process — not another spend chart.
Time Travel, Fail-safe, clone sprawl, and tables that sit unused. Attribute growth by object and team, then prove the footprint came down.
Cortex and AI Services credits attributed to a workload and owner — so token spend is governed the same way as warehouse burn.
Credit and performance monitoring inside your Snowflake account from Marketplace. Metadata only. The full loop lives on the platform, not in the listing.
Assessments and the Cortex simulator — Snowflake-specific, no login required to begin.
Five questions on visibility, ownership, validation, and proof. A scorecard against the gaps that leave Snowflake budgets exposed.
Score enforcement readiness across visibility, ownership, governance, drift, and follow-through — before the next warehouse drift cycle.
Directional Cortex credit estimates from official Snowflake service pricing — before AI_COMPLETE or Search hits the bill.
Not a second APEX explainer — the warehouse-level words teams already use.
When intermediate data leaves warehouse memory for local disk or remote storage. Runtime grows; credits follow runtime. Governance still has to own the pattern.
Marketplace monitoring versus the Private Knowledge Graph, Enforcement Desk, and PR-gated closure. Same product family — different depth.
A short recap in Snowflake vocabulary. The engine write-up lives on APEX.
200+ Snowflake signals rank addressable waste — idle warehouses, spilling queries, Time Travel bloat, Cortex token burn — not the busiest credit line.
The Private Knowledge Graph resolves the workload and owner from tags, roles, and evidence. When ownership is not knowable, it says so — it does not guess.
The exact warehouse, query, or Cortex change goes through your PR process. PKG is for assignment and closure — not AutoApply into production.
The finding closes when warehouse credits, storage bytes, or Cortex tokens recover. Nobody self-reports a win.
What this page covers, how we connect, and how the Native App differs from the full loop.