# Immuta Data Governance

> 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.

Source: https://toolsfordata.com/tools/immuta/ · Updated 2026-11-19

[Website](https://www.immuta.com/) · [Docs](https://documentation.immuta.com/SaaS/) · [Pricing](https://aws.amazon.com/marketplace/pp/prodview-nddvfz3vrg5uu)

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.

## Overview

- Core Strength: One set of masking and row-level policies enforced natively across Snowflake, Databricks, BigQuery and more
- Lineage Depth: Not supported
- Catalog Curation: Partial — usage stats
- Stewardship Workflows: Partial — review/approval
- Policy & Classification: Full — sensitive-data discovery, policy, enforcement, masking
- Compliance Depth: Partial — audit trail, reporting
- Marketplace & Data Products: Full — data products, access requests, data mesh, subscriptions
- Built-in Data Quality: Not confirmed
- AI & Agent Interface: Not supported
- AI Governance: Not supported
- Developer Surface: Partial — API, webhooks
- Deployment Model: Partial — SaaS, self-hosted, data residency
- Security & Access: Full — SSO, SCIM, RBAC, audit log…
- Notable Caveat: Not a catalog: no lineage or glossary, and built-in regulation templates were retired in December 2024

## What it's used for

Immuta is used to give people governed access to data across Snowflake, Databricks, BigQuery, Redshift and Starburst: it classifies sensitive columns, applies masking and row-level policies inside each platform, and turns approved access requests into policies.

## Classification

Immuta scans columns inside the data platform with built-in and custom identifiers, then writes one set of attribute- and purpose-based policies that it pushes down as native masking and row filters into 15+ platforms.

## Marketplace

The Request app publishes data products and routes access requests through review flows, with AI review assist. Approved requests become platform grants. Requests can also start from Alation, Atlan, Collibra, Unity Catalog or Horizon.

## Compliance

Immuta combines query logs from Snowflake, Databricks and Trino with column sensitivity to show who queried sensitive data. Logs are pulled once a day by default.

## AI governance

Agentic data access, in public preview since October 2026, treats AI agents as identities and gives them short-lived roles that combine the agent's and the user's rights.

## Pricing

Immuta doesn't publish prices. On AWS Marketplace, a 12-month contract for 960 Immuta Units lists at $96,000.

## Deployment

Immuta runs as SaaS on AWS in North America, Europe and Asia Pacific, or self-managed on-premises or in a private cloud.

## Security

Immuta supports SAML, OIDC and LDAP sign-in, SCIM, role-based access and audit export, with SOC 2 Type 2, ISO 27001, ISO 27701 and PCI DSS.

## Integrations

Immuta enforces access policies on Snowflake, Databricks, BigQuery, Redshift and Starburst, and syncs tags with the Collibra, Alation, Atlan and Purview catalogs.

## Review

Strengths:
- Enforces one set of masking and row-level policies natively across Snowflake, Databricks, BigQuery, Redshift, Starburst and more.
- Approved access requests become platform grants, with no ticket in between.
- Shows who queried sensitive data by joining query logs with column sensitivity.

Caveats:
- Not a catalog: no lineage, glossary or documentation, so it needs Alation, Collibra, Atlan or Purview next to it.
- Built-in HIPAA, GDPR, CCPA and PCI frameworks were retired in December 2024; regulation-specific rules are now written through the API.
- Agentic data access and the Comply AI chat are still in preview.

Recommendation: Choose Immuta when the problem is access: one policy layer across several data platforms. Pair it with a catalog; for a Ranger-based estate, consider Trust3 AI instead.

## Facts

- Immuta raised a $100M Series E in June 2022, at a reported $1B valuation.
- Immuta launched agentic data access in March 2026 and extended it to Snowflake and Databricks in June 2026.
- Immuta removed its Snowflake lineage tag propagation in July 2026, in favor of Snowflake's own.

## Pricing

- Model: custom
- Entry team price: Custom
- Entry enterprise price: $96,000/year
- Source: https://aws.amazon.com/marketplace/pp/prodview-nddvfz3vrg5uu (checked 2026-11-12)

## Features

### Data Catalog

- Automated Metadata Harvesting: Yes — Connections crawl registered platforms, and schema monitoring registers new tables and detects added, removed, or retyped columns automatically. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/schema-monitoring))
- Search & Discovery: Yes — The Data Sources list can be searched by keyword, tag, column, connection string, or global policy name and filtered by access, technology, or health. ([source](https://documentation.immuta.com/saas/govern/data-consumers/subscribe-to-data-source))
- AI-Powered Search: No — Search is keyword and filter based; no natural language or semantic search over data sources is documented. ([source](https://documentation.immuta.com/saas/govern/data-consumers/subscribe-to-data-source))
- Usage & Popularity Statistics: Yes — Audit dashboards show the most accessed data sources, active columns, most active users, and queries over time from platform query logs. ([source](https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept))
- Custom Fields & Templates: No — Metadata on data sources is limited to tags, column descriptions, and owners; custom attribute fields exist for users and request forms, not for data assets. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Asset Certification: No — There is no trust label for data assets; certifications in Immuta are data owner sign-offs on the global policies applied to their data source. ([source](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/how-to-guides/manage-policies-per-data-source))
- Business Glossary: No — Immuta has no glossary module; it uses tags, which can be imported from external catalogs. ([source](https://documentation.immuta.com/saas/configuration/tags/manage-tags))
- Metadata Propagation: No — Snowflake lineage tag propagation was deprecated in May 2026 and removed in July 2026 in favor of Snowflake's native tag propagation. ([source](https://documentation.immuta.com/saas/releases/deprecations))

### Data Lineage

- Table-Level Lineage: No — No table-level lineage is documented. ([source](https://documentation.immuta.com/saas/releases/deprecations))
- Column-Level Lineage: No — No column-level lineage is documented. ([source](https://documentation.immuta.com/saas/releases/deprecations))
- End-to-End Lineage: No — No end-to-end lineage is documented. ([source](https://documentation.immuta.com/saas/releases/deprecations))
- Impact Analysis: No — No lineage-based impact analysis; the policy explainer previews how a single policy behaves but not downstream effects of schema changes. ([source](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/data-policies))
- Automated Lineage Extraction: No — Immuta does not build lineage; its only lineage feature, Snowflake lineage tag propagation (private preview), was deprecated in May 2026 and removed in July 2026 in favor of Snowflake's native tag propagation. ([source](https://documentation.immuta.com/SaaS/releases/deprecations))
- OpenLineage Support: No — No OpenLineage support is documented. ([source](https://documentation.immuta.com/saas/releases/deprecations))

### Data Stewardship

- Critical Data Elements: No — No feature registers or monitors critical data elements. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Review & Approval Workflows: Yes — Dynamic review flows route access and masking exception requests through decision branches, any/all reviewer approval, auto-approve or deny rules, and review assist. ([source](https://documentation.immuta.com/saas/request/review-access-requests/reference-guides/review-flows))
- Governance Campaigns: No — No in-product bulk campaigns; recertification is done by exporting access summaries to tools like SailPoint or ServiceNow. ([source](https://documentation.immuta.com/saas/comply/introduction))
- Governance Scorecards: No — No questionnaire-driven maturity scorecards in the product; governance maturity content exists only in the knowledge base. ([source](https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept))
- Metadata Automation: Yes — Identification runs automatically when data sources are registered or new columns are detected, and classification frameworks then apply sensitivity tags that drive policies. ([source](https://documentation.immuta.com/saas/configuration/tags/data-discovery))

### Data Classification

- Sensitive Data Discovery: Yes — Identification scans data sources with built-in and custom identifiers based on column names, data patterns, and dictionaries, and tags PII and other sensitive columns automatically. ([source](https://documentation.immuta.com/saas/configuration/tags/data-discovery))
- Data Policy: Yes — Global subscription and data policies control table access and apply row-level, purpose-based, time-based, and column masking rules based on user attributes and data tags. ([source](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/data-policies))
- Native Policy Enforcement: Yes — Policies are enforced natively in Snowflake, Databricks Unity Catalog, BigQuery, Redshift, Synapse, Starburst (Trino), S3, and others that Immuta does not operate. ([source](https://documentation.immuta.com/saas/configuration/integrations))
- Data Masking: Yes — Dynamic masking by hashing, NULL, constant, regex, rounding, or custom function is applied at query time, with reveal policies and masking exceptions for approved users. ([source](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/reference-guides/data-policies))

### AI Features

- AI Chat Assistant: No — The Comply app's AI chat answers questions about who can access what, but it is in private preview. ([source](https://documentation.immuta.com/saas/comply/introduction))
- AI Documentation Generation: No — No AI-generated descriptions for tables or columns; AI is used only for policy explanation, access review, and access questions. ([source](https://documentation.immuta.com/saas/configuration/application-configuration/reference-guides/immuta-ai-faq/immutas-ai-features))
- Agentic Metadata Enrichment: No — No AI agents enrich or tag metadata; tagging is driven by rule-based identifiers and classification frameworks. ([source](https://documentation.immuta.com/saas/configuration/application-configuration/reference-guides/immuta-ai-faq/immutas-ai-features))

### Data Compliance

- Audit Trail: Yes — The universal audit model records application events (policy, tag, attribute, and access changes) and query events, searchable in the UI and exportable to S3 or ADLS Gen2. ([source](https://documentation.immuta.com/saas/govern/detect-introduction))
- Compliance Reporting: Yes — Governance reports list users, groups, subscriptions, purposes, and access history per data source, and audit dashboards show sensitive data access by user and data source. ([source](https://documentation.immuta.com/saas/govern/detect-introduction/index/reference-guides/reports))
- Regulatory Framework Mapping: No — Built-in HIPAA, GDPR, CCPA, and PCI classification frameworks reached end of life in December 2024; teams now write custom frameworks through the API. ([source](https://documentation.immuta.com/saas/releases/deprecations))
- Data Activity Monitoring: Yes — Immuta ingests query audit logs from Snowflake, Databricks, and Trino, scores the sensitivity of each query, and can alert on events; query events are pulled once a day by default. ([source](https://documentation.immuta.com/saas/govern/detect-introduction/detection/detect-concept))
- ROPA: No — No GDPR Article 30 processing register. ([source](https://documentation.immuta.com/saas/comply/introduction))
- Data Retention Policies: No — Time-based policies hide rows older than a set age from users but do not archive or delete data. ([source](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/data-policies/how-to-guides/time-based-tutorial))
- Data Subject Rights: No — No DSAR or deletion request handling is documented. ([source](https://documentation.immuta.com/saas/comply/introduction))

### Collaboration

- Alert Notifications: Yes — Request app notifications for access requests, decisions, expirations, and data product changes can go to Slack, Microsoft Teams, email, or webhooks. ([source](https://documentation.immuta.com/saas/request/notifications/how-to-guides/manage-slack-notifications))
- Discussions & Annotations: No — No comments or threaded discussions on data sources; contact details for data owners are shown instead. ([source](https://documentation.immuta.com/saas/govern/data-consumers/subscribe-to-data-source))
- Ticketing Integrations: No — No Jira or ServiceNow ticket creation; the Request app is designed to replace ticket-based access requests. ([source](https://documentation.immuta.com/saas/request/introduction))

### Data Marketplace

- Self-Service Access Requests: Yes — Consumers request access to data products or assets from the Request app or from their catalog (Alation, Atlan, Collibra, Unity Catalog, Horizon), and stewards approve or deny. ([source](https://documentation.immuta.com/saas/request/configure/reference-guides/start-from-your-data-catalog))
- Data Products: Yes — Data product managers publish curated sets of data sources with descriptions, subject matter experts, request forms, review flows, and data use agreements. ([source](https://documentation.immuta.com/saas/request/access-data-products/reference-guide/data-products-and-assets))
- Data Mesh Support: Yes — Domains let business units manage their own policies, audit, identifiers, and data products within global policies set centrally. ([source](https://documentation.immuta.com/saas/configuration/domains))
- Subscription Management: Yes — 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. ([source](https://documentation.immuta.com/saas/request/notifications/reference-guides/notifications-reference-guide/notifications))

### Data Quality

- SQL Table Tests: No — No data quality rules or tests. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Data Health Scores: No — Data source health shows whether background jobs succeeded, not a data quality score. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Anomaly Detection: No — No anomaly detection on data values or volumes. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Data Profiling: Unknown — Background jobs compute table statistics such as row counts for health checks, but column-level profiling for users is not documented. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Data Contracts: No — No data contract support. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))

### AI Governance

- AI Asset Inventory: No — Agents can be registered as identities with groups and attributes, but this is in public preview and there is no catalog of models or AI applications. ([source](https://documentation.immuta.com/saas/agentic-data-access/introduction))
- AI Lineage: No — No training data lineage for models. ([source](https://documentation.immuta.com/saas/agentic-data-access/introduction))
- AI Regulatory Compliance: No — No EU AI Act, NIST AI RMF, or ISO 42001 controls. ([source](https://documentation.immuta.com/saas/agentic-data-access/introduction))
- AI Model Health Score: No — No model health or trust score. ([source](https://documentation.immuta.com/saas/agentic-data-access/introduction))
- AI Agent Access Governance: No — Agentic data access vends ephemeral roles that combine an agent's and a user's entitlements so masking and row policies apply at query time, but it is in public preview (October 2026). ([source](https://documentation.immuta.com/saas/agentic-data-access/introduction))

### Master Data Management

- Master Data Management: No — Immuta has no MDM capabilities. ([source](https://documentation.immuta.com/saas/configuration/integrations))

### Workflows

- REST / GraphQL API: Yes — REST APIs manage data sources, policies, projects, domains, tags, frameworks, and access requests, with a V2 API for policy as code and GraphQL for audit export. ([source](https://documentation.immuta.com/saas/developer-guides/api-intro))
- dbt Integration: No — Immuta documents how to keep policies in place during dbt runs, but does not ingest dbt models, tests, or lineage. ([source](https://documentation.immuta.com/saas/govern/authoring-policies-in-secure/dbt-transform-workflow))
- Python SDK: No — Immuta provides a CLI binary and REST APIs but no pip-installable Python SDK. ([source](https://documentation.immuta.com/saas/developer-guides/the-immuta-cli/installation))
- Webhooks: Yes — Webhooks send notifications for Immuta events and Request app events to external systems. ([source](https://documentation.immuta.com/saas/request/notifications/reference-guides/webhooks))

### Data Context Layer

- MCP Server: No — The only MCP server is GitBook's server for the Immuta documentation; no MCP server exposes Immuta metadata or policies. ([source](https://documentation.immuta.com/saas/configuration/work-with-llms))
- Knowledge Graph: No — No property graph of metadata is documented. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Semantic Models: No — No semantic model generation. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Verified Queries: No — Agentic data access vends scoped, short-lived roles so agents query data on behalf of a user; there is no store of approved questions, SQL or metrics for agents to reuse. ([source](https://documentation.immuta.com/SaaS/agentic-data-access/agentic-data-access-reference-guide))
- Semantic Layer Interop: No — Data sources carry tags, descriptions and policies; no metric or semantic model import or export (dbt MetricFlow, Snowflake semantic views, LookML, OSI) is documented. ([source](https://documentation.immuta.com/saas/configuration/integrations/registering-metadata/data-source-overview))
- Unstructured Data Catalog: No — S3 buckets, prefixes or objects can be registered by hand as data sources with owners, tags and access policies, but Immuta doesn't harvest unstructured content or index documents. ([source](https://documentation.immuta.com/SaaS/configuration/integrations/amazon-s3-integration))

### Security

- SSO: Yes — Users can sign in through SAML 2.0, OpenID Connect, or LDAP identity providers such as Okta, Microsoft Entra ID, and OneLogin. ([source](https://documentation.immuta.com/saas/configuration/people/section-contents/reference-guides/saml-protocol))
- RBAC: Yes — Global permissions (such as GOVERNANCE, AUDIT, USER_ADMIN) and domain-scoped permissions control what each user can do in Immuta. ([source](https://documentation.immuta.com/saas/configuration/people/users-index/reference-guides/personas-and-permissions))
- Audit Log: Yes — Logins, permission changes, policy edits, and tag changes are recorded as application audit events on the Audit page. ([source](https://documentation.immuta.com/saas/govern/detect-introduction))
- Compliance Certifications: Yes — The trust center lists SOC 2 Type 2, ISO 27001, ISO 27701, and PCI DSS attestations. ([source](https://www.immuta.com/trust/))
- SCIM Provisioning: Yes — SCIM 2.0 syncs users and groups from identity providers such as Okta and Microsoft Entra ID. ([source](https://documentation.immuta.com/saas/configuration/people/section-contents/reference-guides/scim-protocol))

### Deployment

- SaaS Deployment: Yes — Immuta SaaS is the recommended option, with automatic updates and no infrastructure to run. ([source](https://documentation.immuta.com/saas/configuration/application-configuration/reference-guides/deployment-options))
- Self-Hosted Deployment: Yes — Self-managed deployments are supported for on-premises or private cloud environments on AWS, Azure, and GCP. ([source](https://documentation.immuta.com/saas/configuration/application-configuration/reference-guides/deployment-options))
- Hybrid Deployment: No — There is no on-premises agent model; SaaS connects directly to data platforms (optionally over PrivateLink) and runs identification inside them. ([source](https://documentation.immuta.com/saas/configuration/application-configuration/reference-guides/deployment-options))
- Data Residency: Yes — SaaS tenants are deployed into North America, Europe, or Asia Pacific global segments, and tenant data does not leave its segment. ([source](https://documentation.immuta.com/saas/configuration/application-configuration/reference-guides/deployment-options))

### Open Source

- Open Source: No — Immuta is proprietary; the core platform is not released under an open-source license. ([source](https://www.immuta.com/trust/))

## Integrations

44 integrations, each sourced from the vendor docs.

- Authentication: AWS PrivateLink, Amazon Cognito, Azure PrivateLink, Centrify, Google OAuth, JumpCloud, Keycloak, LDAP, Microsoft ADFS, Microsoft Entra, Okta, Onelogin, OpenID, Oracle Access Manager, Ping, SAML
- Data Governance: AWS Lake Formation, Alation, Atlan, Collibra, Databricks Unity Catalog, Microsoft Purview, Snowflake Horizon
- Data Storage: Amazon S3, Azure Data Lake Storage
- Data Transformation: Amazon EMR
- Data Warehouse: Amazon Redshift, Azure Synapse, Databricks SQL, Google BigQuery, Oracle DB, Snowflake, Starburst, Teradata
- Databases: Databricks Lakebase, MariaDB, Microsoft SQL Server, MySQL, PostgreSQL
- Notifications: Microsoft Teams, Slack, Webhook
- Query Engine: Amazon Athena, Trino

## Alternatives

- [Trust3 AI (formerly Privacera)](https://toolsfordata.com/tools/trust3-ai/): The closest match: policy enforcement, classification and masking across clouds, built on Apache Ranger.
- [Microsoft Purview](https://toolsfordata.com/tools/microsoft-purview/): Consider Purview for data security and compliance on a Microsoft estate.
- [Collibra](https://toolsfordata.com/tools/collibra/): Consider Collibra if access policies are part of a wider governance program.
- [Snowflake Horizon](https://toolsfordata.com/tools/snowflake-horizon/): Consider Horizon if most data is on Snowflake: masking and policies are built in.
- [Databricks Unity Catalog](https://toolsfordata.com/tools/databricks-unity-catalog/): Consider Unity Catalog if most data is on Databricks: fine-grained access control is built in.
- [Collate](https://toolsfordata.com/tools/collate/): Consider Collate to push access policies into Snowflake and Databricks from a catalog.
