Anavsan Explore
All terms Start Free Trial

Terminology › What it is not

Native App vs full platform: which Anavsan product?

Anavsan ships two ways to look at Snowflake spend. They share a name and are easy to confuse. The Native App monitors credits inside the account. The full platform turns those credits into owned, simulated, and closed work.

The Native App is a Snowflake Marketplace app that monitors credit, warehouse, query, and storage consumption inside the account — metadata only, no business data egress. The full platform is APEX: Trace → Assign → Prove → Enforce. They are two products for two jobs, not a crippled demo and an upgrade tax.

Key takeaways

Start with the constraint, not the catalog. If security will not approve data leaving Snowflake, you need in-account monitoring. If alerts already stall, you need ownership and proof.
Monitoring for one account is free. Typical Marketplace install is under ten minutes. Advisory only — the app does not rewrite queries or change warehouses.
You can use both. There is no required migration. Some teams keep Marketplace visibility and run APEX as the execution layer.
A new dashboard that would not change Monday is the wrong product. If you already know the expensive jobs, more monitoring will not move the bill.

Two products, two jobs

Native AppFull platform (APEX)
JobSee credit, warehouse, query, and storage patterns inside SnowflakeTrace, assign, prove, and enforce so the bill moves
Where it runsInside the account (Marketplace)Accountability / Enforcement plans at agent.anavsan.com
DataMetadata only; no business data egressMetadata only; no business data egress
ActionsAdvisory recommendationsOwners, simulation, Desk, documented closure

What the Native App actually monitors

The app reads ACCOUNT_USAGE and INFORMATION_SCHEMA. It surfaces credit consumption, warehouse utilization, idle time, queuing, query cost signals, and storage growth including Time Travel and Fail-safe. It inherits Snowflake RBAC. Listing: Anavsan Snowflake Credit and Performance Monitoring. Product walkthrough: Native App page.

What the full platform adds

Detection is an input. APEX is what happens after: workload identity via the Private Knowledge Graph, assignment, pre-production simulation, the Enforcement Desk, and proof that credits fell. Multi-account collaboration and policy live here. A 14-day trial covers Accountability and Enforcement on the pricing page.

How to choose

Start with the Native App when access is the constraint: security wants metadata-only in-account monitoring, procurement will not open a long vendor review, or you need a business case from one account this week.

Move to the full platform when visibility is no longer the bottleneck: alerts stall, engineers will not change production without impact, FinOps needs a savings record, or you run more than one account. The longer decision narrative is the Native App vs Full Platform article.

APEX

What the full platform actually is.

Read →

Workload Governance

The job monitoring cannot finish.

Read →

Cost Accountability

The gap after a Native App dashboard.

Read →

Native App product

Marketplace listing and install path.

Read →

Frequently asked questions

No. They are different products for different jobs. Stay on monitoring, add APEX when you need ownership and enforcement, or use both.
No. It runs inside the account, inherits Snowflake RBAC, and reads metadata only. Business data does not leave the account.
When visibility is no longer the bottleneck: alerts stall without owners, you need to simulate before production, you run more than one account, or FinOps needs proof that credits fell.
Yes. If you already know you need ownership and simulation, start the trial at agent.anavsan.com/signup. You do not have to install the Native App first.