Immuta vs Snowflake Horizon
By Ari Bajo - data engineer turned writer.
Updated on November 19, 2026
Summary
Snowflake Horizon classifies data and enforces masking and row policies inside Snowflake, included in its editions; Immuta enforces one set of masking and row-level policies natively across Snowflake, Databricks, BigQuery and others. Immuta lists $96,000 a year, so it pays off only when policies must span more than one platform.
Immuta and Snowflake Horizon differ on 32 of the 70 features in my data governance feature matrix and share 22.
Immuta vs Snowflake Horizon at a glance
| Criterion | Immuta | Snowflake Horizon |
|---|---|---|
| What it is | Immuta is a data provisioning platform that classifies sensitive columns and enforces masking, row-level and access policies natively in Snowflake, Databricks, BigQuery, Redshift, Starburst and other platforms, with a Request app for self-service access to data products. | Snowflake Horizon is Horizon Catalog, the built-in catalog and governance layer for Snowflake — with data classification, column- and row-level policy enforcement, data lineage, data quality monitoring, AI guardrails, and governance that reaches external catalogs beyond Snowflake. |
| Best for | Data engineering and governance teams that need fine-grained, policy-as-code access controls enforced consistently across multiple cloud data platforms without managing per-platform SQL grants. | Data governance teams already running their data platform on Snowflake who want native, policy-driven governance without adding a separate catalog tool. |
| Category | Enterprise data governance | Platform-native data governance |
| Core strength | One set of masking and row-level policies enforced natively across Snowflake, Databricks, BigQuery and more | Governance built into Snowflake — classification and policy enforcement with no separate tool to deploy |
| Pricing | From $96,000/year | From Included (Standard Edition) |
| Free option | None | None |
| Deployment | SaaS, self-hosted, data residency | SaaS, data residency |
| Features | 35 of 70 tracked | 57 of 70 tracked |
| Notable caveat | Not a catalog: no lineage or glossary, and built-in regulation templates were retired in December 2024 | Governs the Snowflake estate only — and 7 of 70 features here are still unresearched |
Key differences between Immuta and Snowflake Horizon
The 32 features where only one of them is confirmed, by feature group. Each line says how the tool does it and links the source.
Data Catalog
AI-Powered Search
Immuta: not supported.
Snowflake Horizon: Universal Search accepts conversational natural-language queries, matches objects whose names differ from the search terms, and tolerates misspellings (docs).
Custom Fields & Templates
Immuta: not supported.
Snowflake Horizon: Object tagging supports multi-value tags, plus native and custom classification categories (docs).
Asset Certification
Immuta: not supported.
Snowflake Horizon: `SNOWFLAKE.TAGS.CERTIFICATION_STATUS` (CERTIFIED/DEPRECATED), GA 2026-10-20 (docs).
Metadata Propagation
Immuta: not supported.
Snowflake Horizon: Tag inheritance propagates tags through the object hierarchy; tag-based masking policies apply protection wherever a tag is assigned (docs).
Data Lineage
Table-Level Lineage
Immuta: not supported.
Snowflake Horizon: Lineage tracks relationships between tables and views (docs).
Column-Level Lineage
Immuta: not supported.
Snowflake Horizon: Lineage works at object and column level; column lineage shows upstream and downstream columns with their distance and is retained for one year (docs).
End-to-End Lineage
Immuta: not supported.
Snowflake Horizon: Lineage from PostgreSQL through dbt and Snowflake to Tableau dashboards is stitched into one column-level graph (Preview) (docs).
Impact Analysis
Immuta: not supported.
Snowflake Horizon: Object Dependencies audits object references via metadata, surfacing what depends on a given object (docs).
Automated Lineage Extraction
Immuta: not supported.
Snowflake Horizon: Snowflake records lineage automatically from the SQL it runs (CTAS, INSERT, MERGE, UPDATE, CREATE VIEW), and external lineage accepts OpenLineage events from dbt and Airflow (docs).
OpenLineage Support
Immuta: not supported.
Snowflake Horizon: External lineage accepts OpenLineage-compatible events through a REST endpoint, with documented setup for dbt (dbt-ol) and Airflow 2.7+; column mappings are captured best-effort (docs).
Data Classification
Native Policy Enforcement
Immuta: Policies are enforced natively in Snowflake, Databricks Unity Catalog, BigQuery, Redshift, Synapse, Starburst (Trino), S3, and others that Immuta does not operate (docs).
Snowflake Horizon: not supported.
AI Features
AI Chat Assistant
Immuta: not supported.
Snowflake Horizon: Snowflake CoCo uses catalog context to write SQL, trace lineage and review governance posture (docs).
AI Documentation Generation
Immuta: not supported.
Snowflake Horizon: Cortex generates table, view and column descriptions (docs).
Agentic Metadata Enrichment
Immuta: not supported.
Snowflake Horizon: Classification profiles with AI mode (Preview) detect and tag sensitive columns without per-asset review (docs).
Data Compliance
Data Retention Policies
Immuta: not supported.
Snowflake Horizon: Storage lifecycle policies archive or expire rows by condition "to help meet compliance requirements" (GA 2025-11-07) (docs).
Data Marketplace
Data Mesh Support
Immuta: Domains let business units manage their own policies, audit, identifiers, and data products within global policies set centrally (docs).
Snowflake Horizon: not confirmed.
Subscription Management
Immuta: Data products track approved members, and members are notified when access expires or a product is suspended or deleted; schema or quality change alerts are not documented (docs).
Snowflake Horizon: not confirmed.
Data Quality
SQL Table Tests
Immuta: not supported.
Snowflake Horizon: User-defined data metric functions run SQL-defined checks against tables to monitor state and integrity (docs).
Anomaly Detection
Immuta: not supported.
Snowflake Horizon: Anomaly detection is documented as part of data quality monitoring (docs).
Data Profiling
Immuta: not confirmed.
Snowflake Horizon: Data profiles are part of data quality monitoring (docs).
AI Governance
AI Asset Inventory
Immuta: not supported.
Snowflake Horizon: The Horizon catalog UI surfaces AI assets alongside Snowflake objects, external tables and dashboards, and models are registered with their versions and metadata in the Snowflake Model Registry (docs).
AI Lineage
Immuta: not supported.
Snowflake Horizon: Lineage covers ML objects (datasets, feature views, models, model monitors), and Cortex Agents appear as downstream consumers of semantic views and Cortex Search services (docs).
AI Agent Access Governance
Immuta: not supported.
Snowflake Horizon: Horizon enforces AI guardrails and agent policies centrally, governing what AI agents may access at query time rather than only exposing an MCP endpoint (website).
Workflows
dbt Integration
Immuta: not supported.
Snowflake Horizon: Horizon dbt connector collects model definitions and lineage. External lineage also accepts dbt-ol (Preview) (docs).
Python SDK
Immuta: not supported.
Snowflake Horizon: Snowflake Python API (docs).
Webhooks
Immuta: Webhooks send notifications for Immuta events and Request app events to external systems (docs).
Snowflake Horizon: not confirmed.
Data Context Layer
MCP Server
Immuta: not supported.
Snowflake Horizon: Snowflake-managed MCP server GA 2025-11-04 (docs).
Semantic Models
Immuta: not supported.
Snowflake Horizon: Semantic views define metrics, dimensions and relationships, built in Semantic Studio (GA 2026-09-30) (docs).
Verified Queries
Immuta: not supported.
Snowflake Horizon: Semantic views hold verified queries (question plus correct SQL, the AI_VERIFIED_QUERIES clause) that Cortex Analyst uses to answer similar questions, and it can suggest new ones from usage (docs).
Semantic Layer Interop
Immuta: not supported.
Snowflake Horizon: Import only: Semantic View Autopilot builds semantic views from Power BI files (PBIX, PBIT; GA August 2026) with their measures and relationships, and from Tableau files; export to other formats is not documented (docs).
Unstructured Data Catalog
Immuta: not supported.
Snowflake Horizon: Cortex Search services, the search indexes over documents, are governed objects with role-based access, and lineage traces them back to the source stage of files (stage lineage in preview) and forward to the Cortex Agents that use them (docs).
Deployment
Self-Hosted Deployment
Immuta: Self-managed deployments are supported for on-premises or private cloud environments on AWS, Azure, and GCP (docs).
Snowflake Horizon: not supported.
Immuta or Snowflake Horizon: which to choose
Choose Snowflake Horizon if
Snowflake is your only data platform.
What both Immuta and Snowflake Horizon do
22 features supported by both
- Data Catalog: Automated Metadata Harvesting, Search & Discovery, Usage & Popularity Statistics
- Data Stewardship: Review & Approval Workflows, Metadata Automation
- Data Classification: Sensitive Data Discovery, Data Policy, Data Masking
- Data Compliance: Audit Trail, Compliance Reporting, Data Activity Monitoring
- Collaboration: Alert Notifications
- Data Marketplace: Self-Service Access Requests, Data Products
- Workflows: REST / GraphQL API
- Security: SSO, RBAC, Audit Log, Compliance Certifications, SCIM Provisioning
- Deployment: SaaS Deployment, Data Residency
Immuta vs Snowflake Horizon integrations
Immuta lists 44 integrations and Snowflake Horizon 28; 9 are on both lists. See the integrations matrix for all tools.
- Both (9): Amazon S3, Databricks Unity Catalog, Keycloak, Microsoft Entra, Okta, Onelogin, Ping, Snowflake, Trino
- Only Immuta (35): AWS Lake Formation, AWS PrivateLink, Alation, Amazon Athena, Amazon Cognito, Amazon EMR, Amazon Redshift, Atlan, Azure Data Lake Storage, Azure PrivateLink, Azure Synapse, Centrify, Collibra, Databricks Lakebase, Databricks SQL, Google BigQuery, Google OAuth, JumpCloud, LDAP, MariaDB, Microsoft ADFS, Microsoft Purview, Microsoft SQL Server, Microsoft Teams, MySQL, OpenID, Oracle Access Manager, Oracle DB, PostgreSQL, SAML, Slack, Snowflake Horizon, Starburst, Teradata, Webhook
- Only Snowflake Horizon (19): AWS Glue Data Catalog, Apache Airflow, Apache Doris, Apache Flink, Apache Iceberg, Apache Spark, Auth0, Azure Blob Storage, Dremio, DuckDB, Google Cloud Storage, Google Workspace, OpenLineage, SAP ERP, Salesforce, Snowflake Open Catalog, StarRocks, Workday, dbt
Immuta vs Snowflake Horizon FAQ
What is the difference between Immuta and Snowflake Horizon?
Snowflake Horizon classifies data and enforces masking and row policies inside Snowflake, included in its editions; Immuta enforces one set of masking and row-level policies natively across Snowflake, Databricks, BigQuery and others. Immuta lists $96,000 a year, so it pays off only when policies must span more than one platform.
Is Immuta or Snowflake Horizon cheaper?
Immuta: from $96,000/year. Snowflake Horizon: from Included (Standard Edition). Prices come from each vendor's pricing page.
Which has more features, Immuta or Snowflake Horizon?
Immuta supports 35 and Snowflake Horizon 57 of the 70 features in my data governance feature matrix. They share 22 and differ on 32; only Immuta has native policy enforcement, data mesh support and subscription management; only Snowflake Horizon has AI-Powered search, custom fields & templates and asset certification.
Can Immuta and Snowflake Horizon be self-hosted?
Immuta: SaaS, self-hosted, data residency. Snowflake Horizon: SaaS, data residency.
Data from my data governance feature matrix, checked against each vendor's docs, and pricing pages. For more options, see the best data governance tools.
Evaluating data tools in 2026?
I curate the most comprehensive lists of data tools, up-to-date comparison tables, and actionable market guides for data teams. More useful than a Gartner report. More reliable than asking AI. Next up: Data FinOps.