Data Catalog Pricing Compared for 2026

Data catalog pricing is hard to compare because most vendors do not publish it. Enterprise catalogs are sold by custom quote, open-source catalogs are free to license but not free to run, and catalogs bundled with a data platform hide their cost inside compute. Yet public numbers do exist: cloud marketplace listings, official consumption price lists, and published plans.

This guide collects those public numbers in one place, explains the pricing models behind them, and shows how to compare quotes on total cost rather than on the license line. All figures were checked against their sources in October 2026. They are list prices or published rates, not what any particular customer pays.

How Much Does a Data Catalog Cost?

A useful answer has three parts. First, the license or subscription, which is the number a vendor quotes. Second, the cost to run it: infrastructure for self-hosted tools, consumption meters for usage-based ones, and the people who administer it. Third, the cost to adopt it: connecting sources, defining a business glossary, assigning owners, and getting business users to rely on it.

Public list prices only answer the first part, and only for a standard package. They are still the best place to start, because they show the order of magnitude each vendor expects and how the price scales.

Data Catalog Pricing Models

Most catalogs use one of five pricing models. The model matters as much as the number, because it decides what makes the bill grow.

• Platform subscription by quote. An annual subscription for a package of users, connectors, or modules, negotiated per customer. Typical of enterprise suites such as Collibra, Alation, and Atlan.
• Per user or per seat. A published price per seat or seat bundle. The bill grows mainly with the team rather than the data estate. Dawiso uses this model, with an object allowance per contributor seat.
• Consumption or per asset. Pay-as-you-go meters for governed assets, processing, or compute. Microsoft Purview and Informatica's IPU model work this way, so the bill grows with the data estate and with how often checks run.
• Open source and open core. No license fee, but the cost moves to infrastructure, upgrades, and the engineers who keep the catalog running, with a commercial managed version for teams that do not want to run it. DataHub and OpenMetadata follow this model.
• Bundled with a data platform. The catalog comes with a warehouse or lakehouse, and its cost sits inside platform consumption and edition. Databricks Unity Catalog and Snowflake Horizon are examples. They are centered on their own platform, and data elsewhere is governed through that platform, so teams with several platforms often look for a catalog that sits across them.

Data Catalog Pricing Compared

The table lists the public price signal for each catalog, where it comes from, and where to read more. Marketplace prices are starting prices for a standard package and exclude private offers.

Specialist tools sit at the top of the range. On Microsoft Marketplace, for example, the Solidatus lineage platform lists at $250,000 per year for 5 author and 25 consumer users. For an evaluation of catalogs by capability rather than price, see the best data catalog tools for 2026.

What Marketplace List Prices Do and Do Not Tell You

Cloud marketplaces are the main source of public prices for enterprise catalogs, because a transactable public offer shows a price. They are useful, with limits.

• They show the entry package. Atlan's listing names five admins and five members; Alation's says "starting at." Real deployments are usually larger.
• They are the vendor's own number. Many deals go through private offers at negotiated prices, but a marketplace listing is the one price a vendor publishes itself, which makes it the fairest anchor for comparison.
• They reveal the pricing structure. Term discounts and the number of users or connectors named in a listing show what will drive the bill as you grow.
• They help with procurement. Buying through a cloud marketplace can count toward an existing cloud spending commitment, which is one reason vendors list there.

Total Cost of Ownership Beyond the License

Across every pricing model, the same costs sit outside the price list:

• Implementation. Connecting sources, configuring roles and domains, and importing existing definitions. For heavy enterprise suites this is a project measured in months.
• Running costs. Infrastructure and on-call time for self-hosted open source, consumption for usage-based tools, and connector maintenance as sources change.
• People. Data stewards and owners who curate metadata. This is often the largest cost and does not change much between vendors.
• Adoption. A catalog that business users do not open is the most expensive outcome, because the spend continues and the value does not arrive.
• Coverage gaps. A catalog that covers only one platform leaves the rest of the estate ungoverned, which often leads to a second tool. See total cost of ownership.

How to Compare Data Catalog Quotes

Put every quote on the same footing before comparing numbers.

1. Fix the scope. List the sources, the number of people who curate metadata, and the number who only consume it.
2. Price three years, not one. Include expected growth in users, sources, and governed assets, and the effect of term discounts.
3. Ask what is capped. Users, connectors, assets, environments, or modules. A cap is a future price increase.
4. Separate license from services. Ask for implementation and support as separate lines, with the internal effort you will need.
5. Check usage-based meters. For consumption pricing, model the meters with your own volumes and schedules, and set budget alerts.
6. Test adoption. Run a pilot with business users, not only the data team, and measure whether they come back.

Where Dawiso Fits

Dawiso publishes its pricing: the Standard plan starts at 5,340 EUR per year (445 EUR per month) for five contributor seats and twenty viewer seats, the Corporate plan covers 60 seats and adds the MCP Server and SQL access to all metadata, and the Enterprise plan covers 260 or more seats with options such as a test environment and on-premise deployment. Every plan includes an unlimited number of connectors and an allowance of 100,000 cataloged objects per contributor.

That model fits teams that want to govern a mixed estate without the bill growing with each new source. The data catalog, business glossary, and lineage connect Microsoft, Snowflake, Databricks, Oracle, SAP, and BI platforms through Dawiso's connectors, and governed context can be served to AI agents through the MCP Server on the Corporate and Enterprise plans.

Conclusion

Data catalog pricing is more public than it looks. Marketplace listings start Alation at $60,000 and Atlan at $120,000 per year, and Collibra's 12-month Cloud Platform subscription is listed at $170,000. Microsoft Purview publishes per-asset and processing rates. Open-source catalogs move the cost from the license to engineering time, and platform catalogs are centered on their own platform. The license, though, is only the first line of the budget. Compare quotes over three years, on the same scope, with caps, services, and adoption included, and the cheapest list price is often not the cheapest catalog.

Sources

• Microsoft Marketplace - Alation: The Industry's Leading Data Catalog (plans and pricing, accessed October 2026)
• Microsoft Marketplace - Atlan - Active Metadata Platform for Azure (plans and pricing, accessed October 2026)
• Microsoft Marketplace - Solidatus US Entity (plans and pricing, accessed October 2026)
• AWS Marketplace - Collibra Data Intelligence Platform (12-month Cloud Platform subscription)
• Microsoft Azure - Microsoft Purview pricing (Data Governance tab, US East, accessed October 2026)
• Informatica - 5-Minute Pricing Guide for Informatica Processing Units (IPU)
• Databricks - How much does Unity Catalog cost, and is Unity Catalog free?
• Snowflake documentation - Data lineage (Enterprise Edition requirement)
• Dawiso - Pricing