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.
On BigQuery that means slots, reservations, on-demand bytes and scan, shuffle and spill, and unowned jobs or datasets — ranked as waste, not as a spend leaderboard.
Same four stages as Snowflake. Different objects: jobs, slots, reservations, scan, shuffle.
Rank addressable waste — idle reservation capacity, on-demand scan that should have been filtered, shuffle and spill that extends slot-seconds — not the busiest project.
Resolve the job, dataset, or reservation to an owner from evidence. Unowned jobs and datasets stay marked as needing an owner. The Private Knowledge Graph assigns — it does not AutoApply.
The exact change — query, reservation, or job config — goes through your review process until it is applied, deferred with a reason, or dismissed.
The finding closes when slot-seconds, scanned bytes, or shuffle volume return to normal. Closure is from the data, not a checkbox.
Nested under this hub — same APEX loop, BigQuery objects. Not Snowflake clones, not a Dataplex catalog, not a 200+ signal list.
On-demand bytes billed and capacity slots. Rank idle baselines, autoscale overshoot, and unpruned scans as waste, then assign an owner.
Logical vs physical billing, time travel, fail-safe, active vs long-term. Unowned datasets and missing expiration become Desk rows.
JOBS referenced_tables for ownership and unreferenced tables — not a Dataplex process/run/event catalog.
Still Snowflake-only: Cortex, Native App, Cortex Cost Simulator. No Databricks.
In product. Metadata only. Same loop. Nested cost, storage, and lineage pages.