Datatrail
BUYER'S GUIDE - UPDATED AUGUST 2026

Data Governance Tools: The Best Data Governance Software and Platforms for 2026

Fifteen platforms checked against vendor documentation rather than marketing pages. What each one actually governs, where lineage stops, the one vendor that publishes exact rates, and the two open-source options guides still recommend that no longer exist.

Jump to the table
Read-only No card to start
Lineage map
Lineage mapped from query history. Read-only connection.
0

Read-only connection. Datatrail never moves or mutates your data.

In short

Data governance tools let an organization define, enforce, and prove how its data is described, owned, secured, and used. The leading data governance software in 2026 is Collibra, Informatica from Salesforce, Alation, Atlan, Microsoft Purview, Ataccama, Qlik Talend, erwin by Quest, Immuta, data.world from ServiceNow, Secoda from Atlassian, and Datatrail, plus the open-source OpenMetadata and DataHub. They divide into four groups that solve genuinely different problems: full governance suites with workflow and audit, catalog-led platforms built for adoption, access governance tools that enforce policy in the warehouse, and self-hosted open source. The deciding question is not the feature list, since every vendor claims the same one. It is whether your mandate is an auditor, a broken number, or an engineer who cannot safely drop a column.

Last updated August 2026

// COMPARE

Side by side

Data governance software compared

Tool Best for Governance scope Lineage granularity Deployment Pricing
Datatrail Warehouse teams that need lineage and change control, not a governance program Lineage, impact, monitoring Column-level, native Read-only connection Published, self-serve
Collibra Regulated enterprises running a formal, audited governance program Full governance suite Column-level, with conditions SaaS or self-hosted No published pricing
Informatica from Salesforce Large estates already standardized on Informatica integration and MDM Full governance suite plus MDM Column-level SaaS plus Secure Agent No published pricing
Alation Analytics-first organizations where adoption is the hard part Catalog-led governance Table-level default, column-level is an add-on SaaS or customer-managed No published pricing
Atlan Modern data teams that want governance people will actually use Catalog-led governance Column-level, native Single-tenant SaaS plus agent No published pricing
Microsoft Purview Microsoft-centric estates that want governance and compliance in one bill Governance plus compliance and DLP Column-level, with gaps SaaS plus integration runtime Published metered rates
Ataccama Data quality-led governance in regulated mid-market and enterprise Quality-led governance plus MDM Column-level SaaS or self-hosted No published pricing
Qlik Talend Teams that need integration, quality, and governance from one vendor Integration-led governance Column-level SaaS or self-hosted No published pricing
erwin Data Intelligence by Quest Organizations with an existing modeling and metadata estate Metadata-led governance Column-level SaaS or self-hosted No published pricing
Immuta Access governance and policy enforcement, not cataloging Data access governance Not a lineage tool SaaS plus native enforcement No published pricing
data.world from ServiceNow ServiceNow shops that want governance where work already happens Catalog-led governance Table and column-level SaaS No published pricing
Secoda from Atlassian Smaller data teams that want adoption without a program Lightweight catalog governance Column-level SaaS No published pricing
OpenMetadata Engineering teams that want a full governance stack with no license fee Catalog, quality, governance Column-level, native Self-hosted Free OSS, no published SaaS pricing
DataHub Platform teams that want column lineage free and can run Kafka Metadata-led governance Column-level in the free edition Self-hosted Free OSS, no published cloud pricing
Apache Atlas Existing Hadoop and Hortonworks estates only Classification and lineage Column-level within Hadoop Self-hosted Free OSS

Capabilities reflect each vendor's own documentation as checked on 5 August 2026. Only figures a vendor publishes itself, or that are returned by its own price API, appear anywhere on this page. This category is consolidating fast, so confirm current details directly before you buy.

// BASICS

The job to be done

What data governance tools are actually for

Every vendor in this category describes itself with the same six words, so the feature lists are close to useless for choosing between them. A more honest framing is that data governance tools answer four questions repeatedly, and with evidence: what data do we have, what does it mean and who owns it, where did it come from and what depends on it, and who is allowed to see it.

Products differ mainly in which of those four they were built for. Collibra and Informatica were built for the second question, because their buyer has an auditor. Alation, Atlan, and Secoda were built for the first, because their buyer has analysts who cannot find anything. Immuta was built for the fourth and does almost nothing about the others. We were built for the third. Every vendor has since bolted on the rest, and the bolted-on parts are consistently weaker than the original.

The second useful lens is what stays true without human effort. Technical metadata, lineage parsed from query history, and usage counts derive themselves from the warehouse and stay correct. Business definitions, ownership, and certifications do not: someone has to write them, and someone has to update them when the model changes. The well-documented failure mode of this category is a program that populates a few thousand glossary entries in year one, and by year three half of them describe columns that no longer exist. When you evaluate a tool, ask what a brand new table looks like in it on the day it is created, before anyone touches it. If the answer is an empty entry waiting for a description, you have bought a documentation project.

Lineage is where the automated and manual halves meet, which is why it appears in every governance evaluation and why it is the part of governance we build. A catalog entry listing a column is a fact. A catalog entry that also shows the eleven models and two executive dashboards reading that column is a decision you can act on. If you want that side in depth, the data lineage tools guide covers it, data catalog tools covers the inventory side, and data quality tools covers the measurement side.

// 15 OPTIONS

The tools

What each data governance tool is actually good at

Datatrail

Lineage, impact, monitoring

Datatrail covers the technical half of governance and is honest about not covering the rest. It connects to Snowflake, BigQuery, Redshift, Databricks, or Postgres with a read-only role, parses query history alongside your dbt manifest into a column-level lineage graph, and uses that graph for the two governance jobs engineers actually get asked about: prove where this number came from, and show what breaks if we change this column. There are no stewardship workflows, no policy engine, and no regulatory reporting module. If your governance requirement is an auditor asking for evidence of data flow, this answers it in an afternoon. If your requirement is a formal program with roles, approvals, and attestation, buy one of the platforms below.

Collibra

Full governance suite

Collibra is the reference implementation of the category: business glossaries, policy management, stewardship workflows, data quality, privacy, and the reporting an auditor expects. It markets a Leader placement in the 2026 Gartner Magic Quadrant for Data and Analytics Governance Platforms. Two operational details buyers miss until late in the cycle. Column-level lineage is real but is not generated for tables created by SQL statements unless you supply the SQL through the folder-connection method, and the CLI lineage harvester reached end of life on 31 July 2026, so connectivity now runs through Edge sites. Collibra also acquired Raito in June 2025 and Deasy Labs in July 2025, and its 2026 positioning is an AI control plane rather than a catalog.

Informatica from Salesforce

Full governance suite plus MDM

Salesforce completed its acquisition of Informatica on 18 November 2025 in a deal valued at roughly 8 billion dollars, and the governance product survived intact as Cloud Data Governance and Catalog inside IDMC, now branded Informatica from Salesforce. It was named a Leader in the January 2026 Gartner Magic Quadrant for Data and Analytics Governance Platforms. It is the strongest option if you also need master data management in the same contract, and the widest in scope of anything here. Pricing runs on consumption units called IPUs; the model is documented but Informatica publishes no dollar rate per IPU. Hybrid and on-premises sources need a customer-installed Secure Agent sized at 16GB of memory minimum.

Alation

Catalog-led governance

Alation approaches governance through discovery and adoption rather than policy: it analyzes query logs behaviorally to surface which tables people actually trust, and its search experience is genuinely better than most of this list. In July 2026 it relaunched as AIOS, an intelligence operating system for enterprise AI, after acquiring Numbers Station. The detail to pin down in a contract is lineage granularity. Alation documentation states that table-level lineage is the default and that column-level lineage requires per-connector enablement, and for Snowflake specifically it requires a paid parser add-on. If column-level lineage is a governance requirement rather than a nice-to-have, get it quoted explicitly instead of assuming it is bundled.

Atlan

Catalog-led governance

Atlan is the best of the modern platforms on time to value, and it markets a Leader placement in the 2026 Gartner Magic Quadrant for Data and Analytics Governance Platforms. Column-level lineage is core rather than an add-on, backed by dedicated column-process entity types and native OpenLineage ingestion from Airflow, Spark, and dbt Cloud. Governance here means tags, classifications, ownership, and policy propagation across the graph rather than the heavy approval chains Collibra and Informatica ship. Architecturally it is a single-tenant SaaS control plane in a dedicated VPC plus a Kubernetes Secure Agent running inside your environment, so it is not self-hostable end to end. Pricing is a conversation, not a page.

Microsoft Purview

Governance plus compliance and DLP

Purview is the only enterprise option on this page that publishes exact rates, which makes it the easiest to budget before a sales call. Unified Catalog bills per unique governed asset per day plus data governance processing units for quality and health jobs, and both rates are queryable from the Azure retail price API. The trap is naming: three different things carry the Purview label. Azure Data Catalog was retired on 15 May 2024, the classic Purview Data Catalog is described by Microsoft as no longer taking on new customers and in customer support mode with no published end-of-life date, and Unified Catalog is the current product. Column-level lineage is supported, but manual column-level lineage is unsupported when a process asset sits in between, and automated lineage only arrives from a fixed list of process systems.

Ataccama

Quality-led governance plus MDM

Ataccama ONE bundles governance, data quality, master data management, and observability in a single platform, and its center of gravity is genuinely data quality: it markets a Leader placement in the 2026 Gartner Magic Quadrant for Augmented Data Quality Solutions. That makes it a better fit than a catalog-led tool when the governance mandate came out of a regulatory finding about incorrect data rather than out of a discovery problem. It runs as SaaS or self-hosted, which matters for organizations that cannot ship metadata out. Ataccama publishes no pricing. Third-party figures circulate for it, including a widely repeated annual number that does not come from Ataccama, and we do not reprint them.

Qlik Talend

Integration-led governance

Qlik acquired Talend in May 2023 and now sells the governance capability as Qlik Talend Cloud and Talend Data Fabric, combining data integration, data quality, stewardship, and cataloging in one stack. Qlik markets a Leader placement in the 2026 Gartner Magic Quadrant for Augmented Data Quality Solutions. It is the right shape when the same team owns the pipelines and the governance obligation, because policies and quality rules sit next to the transformations. The important correction, since guides still recommend it as a free option: Talend Open Studio, the open-source edition, reached end of life at version 7.3 on 31 January 2024, downloads were removed, and the old product page now redirects to a commercial Qlik page. There is no free Talend to evaluate.

erwin Data Intelligence by Quest

Metadata-led governance

erwin has been part of Quest Software since 2021 and remains one of the more underrated options, particularly where erwin Data Modeler is already in place and the metadata can be harvested from models rather than reverse-engineered from a warehouse. Quest shipped erwin Data Intelligence 15 with automated AI model certification, a per-asset trust score built from nine components including quality, governance completeness, timeliness, and popularity, and more than 100 first-party connectors with automated lineage. It is a serious enterprise product with a smaller install base and correspondingly less community material, so plan for vendor-led enablement rather than finding answers on a forum.

Immuta

Data access governance

Immuta solves a different half of the problem and is often bought alongside a catalog rather than instead of one. It automates discovery and classification, then enforces access through policy-as-code, dynamic masking, attribute-based access control, and privacy-enhancing techniques, pushing enforcement natively into Snowflake, Databricks, BigQuery, and Starburst rather than proxying queries. In June 2026 it expanded its Databricks partnership with agentic data access, intent-driven access control built on Unity Catalog role-based access controls, a Comply app for Unity Catalog, and a scalable attribute-based architecture for group permissions. If your governance mandate is who may see which rows, this is the category to shortlist. It will not tell you what a column means or where it came from.

data.world from ServiceNow

Catalog-led governance

data.world was acquired by ServiceNow, announced in May 2025 and closed that July, and now also appears as Data Catalog inside ServiceNow Workflow Data Fabric. Its distinguishing technical choice is a genuine knowledge graph underneath, which makes relationship-heavy governance questions easier to express than in a relational metadata store. The strategic read is straightforward: if your organization runs its work in ServiceNow, putting governance requests into the same workflow engine that already handles change management removes a real adoption barrier. If you do not run ServiceNow, weigh how a standalone product is resourced inside a platform company with a very different core business.

Secoda from Atlassian

Lightweight catalog governance

Secoda joined Atlassian in December 2025 and is heading toward Rovo and the Atlassian System of Work. It has always been the least ceremonious tool in this space: fast to set up, AI-assisted documentation, and a deliberate bias toward getting analysts to use it rather than toward satisfying an audit. That makes it a good fit for a team of five to fifty people who want ownership, documentation, and lineage without standing up a governance council, and a poor fit for a regulated program that needs attestation trails. As with every acquisition on this page, ask how the standalone roadmap is funded and what renewal looks like when the parent wants a bundle.

OpenMetadata

Catalog, quality, governance

OpenMetadata is Apache-2.0 licensed and, unusually for open source, genuinely covers governance rather than just cataloging: glossaries, classification, ownership, policies, data quality tests, and real column-level lineage. Collate, the company behind it, publishes tier limits including a free tier at five users and 500 assets but no dollar figures. The honest cost is operational. A production deployment wants a Java server, a relational database, a search cluster, and an ingestion runner, roughly 10 vCPU and 40GiB of memory before anyone logs in, breaking changes have shipped in patch releases, and Snowflake lineage ingestion needs privileges at the ACCOUNTADMIN level. Airflow has not been mandatory since v1.12.

DataHub

Metadata-led governance

Acryl Data renamed itself to DataHub on 21 May 2025 alongside a 35 million dollar Series B, and the open-source project is DataHub Core under Apache-2.0. Column-level lineage is in the free edition rather than gated behind the paid cloud, currently across 53 of roughly 103 connectors, with Kafka, object storage, Delta Lake, and most BI-adjacent sources remaining table-level. The project is healthy: v1.6.0 in May 2026, more than 100 commits a month, over twelve thousand stars. Governance features are real but more metadata-centric than workflow-centric. Infrastructure is the cost: Kafka, a relational database, a search index, a graph index, and four services, with the Kubernetes guide asking for more than 7GB of memory. DataHub Cloud publishes no pricing and its pricing URL returns a 404.

Apache Atlas

Classification and lineage

Atlas is the original open-source governance project and is still the right answer for one specific situation: an existing Hadoop estate running Hive, Spark, and Kafka where Atlas hooks are already wired in. Its classification and tag-based policy model, particularly paired with Ranger for enforcement, remains coherent. For a modern cloud warehouse it is the wrong tool. Connectivity to Snowflake, BigQuery, and Databricks is community-maintained rather than first-party, the operational footprint assumes a Hadoop-era stack, and the user interface reflects its age. If you are choosing new infrastructure in 2026, evaluate OpenMetadata or DataHub instead, and keep Atlas on the list only if it is already running.

// 4 CATEGORIES

Shortlist by mandate

The four kinds of data governance tool, and who each is for

Most bad governance purchases come from comparing tools that were never competing for the same job. Work out which of these four you are buying before you take a demo, because the shortlists barely overlap.

01

Governance suites

Collibra, Informatica from Salesforce, Ataccama, erwin, Qlik Talend

Built for a formal program with named stewards, approval workflow, policy management, and evidence an external auditor will accept. Deep, slow, and expensive, with implementation measured in quarters. Buy one when somebody in your organization is personally accountable to a regulator, and not before, because the workflow that makes them valuable is exactly what makes them heavy.

02

Catalog-led platforms

Alation, Atlan, Secoda from Atlassian, data.world from ServiceNow

Built on the theory that governance nobody uses is not governance. They lead with search, documentation, ownership, and lineage, then layer policy on top. Faster to adopt and much lighter on process. The trade is depth of workflow and attestation, which is fine right up until an auditor asks for a signed approval chain.

03

Access governance

Immuta, plus native controls in Unity Catalog and Snowflake Horizon

Built for one question only: who may see which rows and columns, under which conditions. Policy-as-code, dynamic masking, and attribute-based access control pushed natively into the warehouse. These sit alongside a catalog rather than replacing it, and they will not tell you what a column means or where it came from.

04

Automated lineage and change control

Datatrail, plus open-source OpenMetadata and DataHub

Built to derive the technical half of governance from what the warehouse already knows, with no curation project attached. Column-level lineage, downstream impact before a change ships, and evidence of data flow on demand. This is the right starting point when the pressure is coming from engineers and broken dashboards rather than from a compliance calendar.

// CONSOLIDATION

Read this before shortlisting

Most of this category changed hands in the last two years

Data governance consolidated hard, and most published comparisons still present these as independent companies. Ownership is now a real part of due diligence, because it determines roadmap direction and it determines whether the tool becomes a wedge into a much larger platform contract at renewal.

  • Informatica joined Salesforce on 18 November 2025, in a deal valued at roughly 8 billion dollars. Governance continues as Cloud Data Governance and Catalog and is being folded into Salesforce's agent governance story.
  • Talend joined Qlik in May 2023. The governance capability is now sold as Qlik Talend Cloud, and the free open-source edition was retired.
  • data.world joined ServiceNow, announced in May 2025 and closed that July. It also appears as Data Catalog inside ServiceNow Workflow Data Fabric.
  • Secoda joined Atlassian in December 2025, heading toward Rovo and the Atlassian System of Work.
  • Select Star joined Snowflake, announced November 2025, folding into Horizon Catalog.
  • CastorDoc joined Coalesce in March 2025 and is now sold as Coalesce Catalog. The CastorDoc brand no longer exists.
  • erwin joined Quest Software in 2021, and Quest continues to ship major releases, most recently erwin Data Intelligence 15.

None of that is automatically bad. ServiceNow and Atlassian distribution genuinely puts governance in front of people who would never open a dedicated tool, and Snowflake owning Select Star is a plus if you are a Snowflake shop. The point is to price it in. Ask directly how the standalone product is resourced after the acquisition, whether support for competing warehouses is a roadmap commitment or a legacy obligation, and what the renewal looks like when the parent wants to sell you a bundle.

One more piece of context worth having before you read anyone's analyst-report marketing: Gartner published a new Magic Quadrant for Data and Analytics Governance Platforms on 6 January 2026, and the criteria moved. The 2026 edition draws a clearer line between governance platforms and data management tools, expects platforms to serve business roles first and integrate outward for enforcement, weights AI agents and active metadata more heavily, and extends the asset types in scope to unstructured data, analytics models, and data products. Informatica, Atlan, Collibra, and Alation all market Leader placements. Read those placements as evidence of enterprise completeness, which is what the criteria reward, and not as evidence that any of them is the right size for your team.

// OPEN SOURCE

Check before you download

Two open-source options every list still recommends no longer exist

Open-source data governance is a legitimate choice and two of the projects are genuinely good. The problem is that the lists recommending them are copied from each other and years stale. Here is what the sources actually showed when checked.

Talend Open Studio is retired. It still appears in nearly every open-source data governance roundup, usually as the free way to get Talend's data quality and stewardship capability. Qlik announced its end of life at version 7.3 effective 31 January 2024, downloads were removed on that date, and the Talend Open Studio product page now returns a permanent redirect to a commercial Qlik Talend Cloud page. There is no free Talend edition to evaluate, and running the last 7.3 build means running software that has had no security updates for more than two years.

Amundsen is dormant. The main branch has had zero commits in the last twelve months and zero in 2026. The last merged pull request was on 2 April 2025, an administrative change moving a maintainer to emeritus status. The last GitHub release was August 2024, the last published Docker images including the latest tag date to March 2024, and 58 pull requests sit open with none merged in roughly sixteen months. The reference deployment still pins Neo4j 3.5, which reached end of life in 2021, and the amundsen.io domain no longer serves the project. The repository is not archived and the Linux Foundation still lists it as incubating, so the accurate word is dormant rather than dead, but it is not a foundation to build a governance program on.

OpenMetadata and DataHub are both healthy, and both are real. OpenMetadata is the more complete governance product of the two, with glossaries, classification, ownership, policies, and data quality tests alongside native column-level lineage, all Apache-2.0. DataHub tagged v1.6.0 in May 2026 with more than a hundred commits in the preceding month, and its column-level lineage is in the free Core edition rather than gated behind the paid cloud, currently covering 53 of roughly 103 connectors.

The honest accounting on both is operational cost. OpenMetadata in production wants a Java server, a relational database, a search cluster, and an ingestion runner, roughly 10 vCPU and 40GiB of memory before anyone logs in. DataHub wants Kafka, a relational database, a search index, a graph index, and four of its own services. Neither has a license fee and both have an engineer's salary attached. That is a good trade with platform engineers who have capacity, and a poor one when the governance project is somebody's side quest.

// NATIVE

Before you buy anything

Your warehouse already ships governance

Every major platform now includes access control, classification, and lineage natively. For a single-platform team this is often enough, and it is always the right baseline to measure a purchase against. Here is what each one really covers, including the limits that surface after rollout rather than before.

Databricks Unity Catalog

The most complete platform-native governance layer. Unity Catalog handles fine-grained access control, audit, and automatic column-level lineage for queries run on Databricks, aggregated across every workspace attached to the metastore, and it is on by default for workspaces created after November 2023. Two corrections, because comparison pages repeat both errors: lineage in Catalog Explorer is retained indefinitely rather than for 90 days, with system tables holding a rolling one-year window, and the long list of exclusions those pages cite has largely been removed from the documentation. Real remaining limits are nothing before 1 September 2024, no lineage preserved through a rename of a catalog, schema, table, view, or column, and no column lineage when the source or target is referenced by path rather than table name. No separate charge, but it requires the Premium plan or above.

Snowflake Horizon Catalog

Horizon is an umbrella brand over individually documented governance features rather than a product you install: tagging, classification, masking and row access policies, data metric functions, the Trust Center, and lineage. Column-level lineage went generally available in release 9.3 in February 2025, requires Enterprise Edition or higher, retains one year of history, and covers nothing before November 2024. Process lineage for procedures and tasks went generally available in October 2025. Horizon is not a billable line item, though components such as data quality monitoring and classification meter serverless compute. Keep the names apart, because they get conflated constantly: Horizon is the governance catalog, Open Catalog is the managed Apache Polaris service for Iceberg and is now closed to new customers, and Openflow is NiFi-based ingestion and not governance at all.

Google Knowledge Catalog

Renamed from Dataplex Universal Catalog on 10 April 2026, with API, CLI, and IAM names unchanged and the pricing SKUs still carrying the Dataplex name. The legacy Data Catalog service began a phased shutdown on 1 June 2026. Governance covers policy tags, column-level access control, data profiling, and quality scans. Column-level lineage is real but narrow: BigQuery, and Dataproc since May 2026, while Dataflow, Composer, Vertex AI, Looker, and anything arriving through OpenLineage stay table-level. Documented limits worth checking against your workload include no column lineage for load jobs or routines, none upstream of external tables, top-level columns only with no nested STRUCT or JSON, and a silent fallback to table-level lineage once a job creates more than 1,500 column links.

AWS Glue Data Catalog and SageMaker Catalog

Two different layers, and the difference matters for a governance evaluation. The Glue Data Catalog is a metadata store holding databases, tables, and schemas for Athena, EMR, and Redshift Spectrum, and despite a vague marketing line in its own documentation it has no lineage user interface, no lineage API, and no column-level lineage. Governance features such as fine-grained access control come from Lake Formation layered on top. Column-level lineage lives in Amazon SageMaker Catalog, built on Amazon DataZone. Read its support matrix before relying on it: automation covers Glue crawlers and Redshift by default, while Glue console jobs and EMR need explicit configuration and Visual ETL in fine-grained mode is unsupported. DataZone was not renamed and still exists separately.

The shared limitation is the platform boundary. Each of these is strong inside its own walls and blind the moment data crosses into a second warehouse, an ingestion tool, or the BI layer where people actually read numbers. If your entire estate is one platform and your governance mandate is internal, start here and buy nothing. If a dashboard in Looker or Power BI reads a Snowflake table populated from a Postgres source, no native layer will show you that whole path, and that gap is the honest reason to add a third-party tool. We cover the specific platform paths in Snowflake lineage, Databricks lineage, BigQuery lineage, and Redshift lineage.

// PRICING

Who will show you a number

Data governance pricing, and the vendors who publish it

Almost none of this category will show you a price without a call. Below is every vendor on this page that publishes real figures on its own site or through its own price API, quoted as published and cross-checked on 5 August 2026. Collibra, Alation, Atlan, Informatica, Ataccama, Qlik Talend, erwin, Immuta, data.world, Secoda, and DataHub Cloud publish nothing.

Vendor Published pricing What to watch
Microsoft Purview Unified Catalog $0.0165 per governed asset per day A governed asset is a table or view linked to a governance concept such as a data product or critical data element. Assets sitting in Data Map without that link are not billed, and an asset used in five data products still counts once per day.
Microsoft Purview data management $15, $60, or $240 per data governance processing unit (Basic, Standard, Advanced) A DGPU is 60 minutes of managed compute for quality and health jobs. Microsoft documents roughly 0.02 DGPU per simple rule per run against a million rows on Basic, so 100 such runs a day is about 2 DGPU.
Microsoft Purview Data Map (classic) $0.411 per capacity unit hour; $0.63 per vCore hour for scanning Only applies to the classic model. Data Map and scan charges stop once you consent to the pay-as-you-go model, which took effect on 6 January 2025. Power BI and on-premises SQL Server scanning are listed at zero.
Coalesce Free Developer tier, then $150 per user per month on Starter Billed by actions consumed. Coalesce Catalog, formerly CastorDoc, is bundled rather than priced separately.
AWS Glue Data Catalog $1 per 100,000 objects per month; $1 per million requests First million objects and first million requests are free. Crawlers bill separately at $0.44 per DPU hour. This is metadata storage only, not governance.
Amazon SageMaker Catalog $0.40 per GiB month; $10 per 100,000 requests; $0 per user Compute bills at $1.776 per compute unit. Per-user cost is genuinely zero, which is unusual in this category.
Google Knowledge Catalog $0.089 per DCU hour for the premium processing tier The premium tier is what lineage, data quality, and profiling run on. The 100 DCU-hour free tier excludes it. Catalog API calls are free; storage is $2.00 per GiB month.
Datatrail $99 Starter, $299 Team, $799 Scale per month Flat monthly plans on the pricing page, no sales call, no per-asset metering.

A note on the numbers you will find elsewhere. Review and procurement sites publish confident-looking annual figures for Collibra, Alation, Immuta, Ataccama, and the rest, and they contradict each other badly enough that some of them are simply wrong. One widely syndicated listing renders Collibra at a per-user monthly rate that is almost certainly an annual contract figure mangled into the wrong unit, and the Ataccama and Immuta numbers in circulation do not come from either vendor. We do not reprint any of them here, and neither should the internal comparison you build. Get the quote.

The pattern worth noticing is that the hyperscalers publish exact metered rates while the specialist governance vendors publish nothing at all. That is a reasonable proxy for how each expects to be bought. Metered rates mean you can model cost from your own asset counts before talking to anyone. Quote-only means budget approval and a procurement cycle before you can even compare. If you want to know what Purview will actually cost, count the tables you would link to a data product and multiply by $0.0165 a day; there is more detail in our breakdown of Microsoft Purview pricing, and the same exercise for the enterprise end in how much Collibra costs. Ours are on the pricing page for the same reason.

// 4 QUESTIONS

How to choose

Four questions that decide which data governance tool you need

01

Who is asking for this?

An auditor, a frustrated analyst, a security review, or an engineer who broke a dashboard. Those four buyers need four different products, and a tool built for one is consistently weak at the others. Write the answer down before the first demo, because vendors will happily reframe your mandate into the shape of what they sell.

02

How much is automatic?

Ask what a brand new table looks like in the tool on the day it is created, before anyone touches it. If the answer is an empty entry waiting for a description, you have bought a documentation project rather than governance. This one question predicts whether the deployment is still accurate in two years better than any feature list.

03

Is column lineage included or extra?

Nearly every vendor claims column-level lineage and the claims are not equivalent. Alation documents table-level as the default with column-level requiring per-connector enablement and, for Snowflake, a paid add-on. Collibra does not generate it for tables created by SQL statements unless the SQL is supplied. Get granularity, connector coverage, and price in writing.

04

What does it cost at your real scale?

Metered vendors let you model this yourself from asset counts. Quote-only vendors do not, so ask for the pricing metric on the first call rather than the price: per source, per governed asset, per seat, or per consumption unit. The metric tells you how the bill grows as your warehouse grows, which matters more than the first-year number.

// HONEST

Where we fit

When Datatrail is the right pick, and when it is not

We should be direct, because this is a page about governance and we are not a governance suite. Datatrail connects to Snowflake, BigQuery, Redshift, Databricks, or Postgres with a read-only role, parses query history alongside your dbt manifest into a column-level lineage graph, and covers the technical half of governance: what exists, where it came from, what depends on it, and what breaks if you change it. There is no policy engine, no stewardship workflow, no attestation chain, and no regulatory reporting module.

So if your mandate is a formal, audited program with named stewards and approval chains, Collibra and Informatica have spent fifteen years building exactly that and we have not. If the mandate is access control, Immuta enforces policy natively in the warehouse and we do not enforce anything. If the driver is data quality found by a regulator, Ataccama and the quality-led vendors are a better starting point. If you want a free self-hosted stack and have the engineers, OpenMetadata is a genuine answer.

Where we are hard to beat is the situation most warehouse teams are actually in, which is not a compliance program at all. Far more in the warehouse than dbt models, a handful of dashboards executives genuinely read, engineers who cannot safely drop a column because nothing shows what reads it, and no appetite for a six-month rollout. For that team the useful governance artifact is downstream impact analysis before a change ships and schema change alerts after it does, both of which arrive the day you connect rather than the quarter you finish curating. It also happens to satisfy the most common real audit request, which is evidence of where a reported number came from. Compare us directly against Atlan, Alation, or open-source tooling.

// FAQ

Questions people ask

Data governance tools, answered

What are data governance tools?

Data governance tools are software platforms that let an organization define, enforce, and prove how its data is described, owned, secured, and used. In practice that means a catalog of assets, a business glossary, ownership and stewardship assignments, lineage showing where data came from, data quality rules, access policies, and an audit trail. The category splits into governance suites such as Collibra and Informatica, catalog-led platforms such as Atlan and Alation, access governance tools such as Immuta, and open-source options such as OpenMetadata and DataHub.

What do data governance tools do?

They answer four questions repeatedly and with evidence: what data do we have, what does it mean and who owns it, where did it come from and what depends on it, and who is allowed to see it. A governance tool automates the parts a warehouse already knows, such as schemas, lineage, and usage, and provides workflow for the parts only people know, such as definitions, ownership, and approvals. The proportion of those two is the single biggest difference between products.

What is the best data governance software?

There is no single best data governance software, because the category serves different mandates. For a regulated, audited program, Collibra or Informatica from Salesforce. For a Microsoft estate that wants published pricing, Microsoft Purview. For quality-led governance, Ataccama. For modern teams that need adoption, Atlan. For access control specifically, Immuta. For a free self-hosted stack, OpenMetadata or DataHub. Start from which of those mandates you actually have, because tools built for one are usually poor at the others.

What are the best open source data governance tools?

OpenMetadata and DataHub are the two credible open-source data governance tools in 2026. Both are actively developed, both have real column-level lineage at no license cost, and OpenMetadata covers glossaries, classification, policies, and quality tests as well. Apache Atlas remains viable only for existing Hadoop estates. Two options still recommended in published lists are no longer valid: Amundsen has had no commits in twelve months, and Talend Open Studio was retired on 31 January 2024.

What is the difference between data governance and data management?

Data governance decides the rules and data management carries them out. Governance defines what a customer is, who owns that definition, what quality level it must meet, and who may access it. Management is the pipelines, storage, integration, and master data processes that move and maintain the data under those rules. A governance tool is where the policy, ownership, and evidence live; a data management stack is where the work happens. Most confusion in vendor material comes from suites that sell both.

What is the difference between data governance and data quality?

Data quality measures whether data is accurate, complete, fresh, and consistent. Data governance is the wider framework that decides which quality standards apply, who is accountable when they are missed, and how that is proven. Quality is one capability inside governance, which is why quality-led vendors such as Ataccama and Qlik Talend sell into governance programs, and why governance suites all ship quality modules. If your mandate came from broken numbers rather than an audit, start with the quality side.

How much do data governance tools cost?

Almost nobody in this category publishes pricing. Collibra, Alation, Atlan, Informatica, Ataccama, Qlik Talend, erwin, Immuta, data.world, and Secoda all quote per deployment against connected sources, governed assets, and seats, and enterprise programs routinely land in six figures a year. The exceptions publish real metered rates: Microsoft charges $0.0165 per governed asset per day plus processing units, the AWS and Google catalog layers publish per-request rates, and Datatrail publishes flat monthly plans. Treat third-party price estimates on review sites with suspicion, because they contradict each other badly.

What is enterprise data governance?

Enterprise data governance is governance run as a formal program across the whole organization rather than inside one team: a governance council, defined stewardship roles, policies that apply to every domain, and evidence produced on a schedule for auditors and regulators. It implies workflow, approvals, and attestation, which is what separates the enterprise suites from the lighter catalog tools. If nobody in your organization is accountable to an external body for how data is handled, you probably need automated lineage and ownership rather than an enterprise program.

Do I need a data governance tool if I already use dbt?

dbt gives you tests, model documentation, and a model-level dependency graph, which covers more governance ground than teams expect. What it does not give you is coverage outside dbt. Raw landing tables, ingestion, ad hoc queries, and every dashboard downstream sit outside the project, and dbt documentation only describes what someone remembered to describe. Add a tool when you need column-level lineage across the whole warehouse, evidence for an auditor, or access policy. Until then, dbt plus discipline is a reasonable answer.

Which data governance tool is best for Snowflake?

Start with Snowflake Horizon Catalog, since tagging, masking, classification, and column-level lineage are already included, with lineage requiring Enterprise Edition or higher and retaining one year of history. Add a third-party tool when governance has to cross the Snowflake boundary into ingestion, a second warehouse, or the BI layer, which Horizon does not see. For access policy specifically, Immuta enforces natively in Snowflake. For lineage and impact analysis across the whole path, Datatrail connects read-only and parses query history.

Governance evidence without the governance program

Connect your warehouse read-only and get column-level lineage, downstream impact, and schema change alerts from day one. Published pricing, no sales call.