DataHub Core vs OpenMetadata

    By Ari Bajo - data engineer turned writer.

    Updated on November 19, 2026

    Summary

    DataHub Core and OpenMetadata are both free, Apache 2.0 catalogs you run yourself, with managed versions (DataHub Cloud, Collate). OpenMetadata builds data quality tests into the catalog; DataHub Core is stronger on lineage, with OpenLineage support, data products and contracts.

    DataHub Core and OpenMetadata differ on 12 of the 70 features in my data governance feature matrix and share 29.

    DataHub Core vs OpenMetadata at a glance

    CriterionDataHub CoreOpenMetadata
    What it isDataHub Core is an open-source context platform for data and AI agents, with automated data discovery, column-level data lineage, a business glossary, active metadata propagation, data stewardship workflows, and a bring-your-own data classification framework — self-hosted and community-maintained.OpenMetadata is an open-source context platform that unifies metadata for humans and AI agents, with data discovery, data quality tests, column-level lineage, and governance.
    Best forData engineering teams that want a flexible, self-hosted metadata platform and are comfortable operating it themselves across complex, multi-source data environments.Data teams that want one self-hosted, open-source platform for discovery, data quality, and governance with a wide range of integrations.
    CategoryOpen-source catalog and lineageOpen-source catalog and lineage
    Core strengthFree, Apache 2.0 catalog with strong lineage, OpenLineage support, data products and contractsFree, Apache 2.0 catalog with lineage, a glossary, data contracts and built-in data quality tests
    PricingFree, open sourceFree, open source
    Free optionOpen sourceOpen source
    DeploymentSelf-hostedSelf-hosted
    Features46 of 70 tracked48 of 70 tracked
    Notable caveatYou run it yourself, and AI agents are DataHub Cloud onlyYou run it yourself; AI agents and policy enforcement are in Collate

    Key differences between DataHub Core and OpenMetadata

    The 12 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

    • Metadata Propagation

      DataHub Core: The open-source docs-propagation action pushes column descriptions to downstream and sibling columns via lineage, enabled by default in Core (docs).

      OpenMetadata: not confirmed.

    Data Stewardship

    • Review & Approval Workflows

      DataHub Core: not supported.

      OpenMetadata: Glossary terms go through reviewer approval, and tasks route description and tag requests to owners (docs).

    • Governance Campaigns

      DataHub Core: Compliance Forms assign questions across many assets to owners; in Core they are available via API only (docs).

      OpenMetadata: not confirmed.

    • Metadata Automation

      DataHub Core: The open-source DataHub Actions framework runs event-triggered actions on metadata changes (e.g. propagation, Slack notifications) (docs).

      OpenMetadata: not confirmed.

    Data Classification

    • Sensitive Data Discovery

      DataHub Core: not supported.

      OpenMetadata: The Auto Classification agent samples data and uses PII recognizers to tag sensitive columns automatically (docs).

    Collaboration

    • Discussions & Annotations

      DataHub Core: not confirmed.

      OpenMetadata: Threaded conversations anchored to assets, columns and glossary terms (docs).

    Data Marketplace

    • Subscription Management

      DataHub Core: not supported.

      OpenMetadata: Users follow assets and get notified of changes through activity feeds and alerts (docs).

    AI Governance

    • AI Agent Access Governance

      DataHub Core: not confirmed.

      OpenMetadata: MCP tools run with the user's or bot's role and access policies, so agents only see metadata those policies allow (docs).

    Workflows

    • Webhooks

      DataHub Core: not confirmed.

      OpenMetadata: Generic webhook alerts send event payloads to external endpoints (docs).

    Data Context Layer

    • Semantic Models

      DataHub Core: Metrics and Semantic Models are first-class entities in Core (Beta, v1.7.0) with lineage through metric upstreams; they are cataloged and linked rather than auto-generated (docs).

      OpenMetadata: not confirmed.

    • Unstructured Data Catalog

      DataHub Core: Context Documents can be imported from GitHub as governed documents with owners and permissions; Notion and Confluence imports are DataHub Cloud only (docs).

      OpenMetadata: not supported.

    Security

    • Audit Log

      DataHub Core: The audit events search API logs user and system actions in Core (docs).

      OpenMetadata: not confirmed.

    DataHub Core or OpenMetadata: which to choose

    Choose DataHub Core if

    Lineage across a complex, multi-source stack matters most and your engineers are comfortable operating it.

    DataHub Core profile DataHub Core alternatives

    Choose OpenMetadata if

    You want data discovery and data quality tests in one self-hosted platform.

    OpenMetadata profile OpenMetadata alternatives

    What both DataHub Core and OpenMetadata do

    29 features supported by both
    • Data Catalog: Automated Metadata Harvesting, Search & Discovery, AI-Powered Search, Usage & Popularity Statistics, Custom Fields & Templates, Business Glossary
    • Data Lineage: Table-Level Lineage, Column-Level Lineage, End-to-End Lineage, Impact Analysis, Automated Lineage Extraction, OpenLineage Support
    • Data Compliance: Audit Trail
    • Collaboration: Alert Notifications
    • Data Marketplace: Data Products, Data Mesh Support
    • Data Quality: SQL Table Tests, Data Profiling, Data Contracts
    • AI Governance: AI Asset Inventory, AI Lineage
    • Workflows: REST / GraphQL API, dbt Integration, Python SDK
    • Data Context Layer: MCP Server, Knowledge Graph
    • Security: SSO, RBAC
    • Deployment: Self-Hosted Deployment

    DataHub Core vs OpenMetadata integrations

    DataHub Core lists 117 integrations and OpenMetadata 52; 39 are on both lists. See the integrations matrix for all tools.

    DataHub Core vs OpenMetadata FAQ

    What is the difference between DataHub Core and OpenMetadata?

    DataHub Core and OpenMetadata are both free, Apache 2.0 catalogs you run yourself, with managed versions (DataHub Cloud, Collate). OpenMetadata builds data quality tests into the catalog; DataHub Core is stronger on lineage, with OpenLineage support, data products and contracts.

    Is DataHub Core or OpenMetadata cheaper?

    DataHub Core: Free, open source (open source). OpenMetadata: Free, open source (open source). Prices come from each vendor's pricing page.

    Which has more features, DataHub Core or OpenMetadata?

    DataHub Core supports 46 and OpenMetadata 48 of the 70 features in my data governance feature matrix. They share 29 and differ on 12; only DataHub Core has metadata propagation, governance campaigns and metadata automation; only OpenMetadata has review & approval workflows, sensitive data discovery and discussions & annotations.

    Is DataHub Core open source?

    Yes, both DataHub Core and OpenMetadata are open source.

    Can DataHub Core and OpenMetadata be self-hosted?

    DataHub Core: Self-hosted. OpenMetadata: Self-hosted.

    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.