PLATFORM PROFILE, read 13 Nov 2026
OpenMetadata and AI-ready data: 7 of 10 conditions by rule, rarest check named owner (7 of 17 tools); it trails OvalEdge most on the label reaching the agent (6 to 8)
Compare OpenMetadata with EunoOpen the coverage matrix
- Category
- Open-source metadata platform and data catalog (OpenMetadata) with a managed, AI-extended commercial edition (Collate)
- Status
- Exists under this name on 13 Nov 2026 (open-metadata.org and docs.open-metadata.org serve OpenMetadata v2.0.x with a v2.1.x snapshot, GitHub open-metadata/OpenMetadata published 2.0.8 and 2.1.0-rc2 on 13 Nov 2026, and getcollate.io sells Collate 2.0 as the managed, AI-extended version built on OpenMetadata).
- Warehouses named
- Snowflake, BigQuery, Databricks, Redshift, Athena, Azure SQL, Trino, PostgreSQL, Unity Catalog
- Transformation named
- dbt, dbt Cloud, Airflow, Dagster, Fivetran, Airbyte, Prefect
- BI named
- Tableau, Power BI, Looker, Metabase, Superset, Qlik Sense, Qlik Cloud, QuickSight, Mode, Sigma, MicroStrategy, Hex, Lightdash, Redash, Grafana
- Rank and total
- 4 of 17, 61.0 of 100
7 of 10 checked by rule, 3 set by a person, 0 none found7 of 10 checked by rule, 3 set by a person, 0 none found
checked by rule set by a person none found on 13 Nov 2026
What OpenMetadata checks, condition by condition
| Condition | How it is checked | Evidence |
|---|---|---|
| Named owner | by rule | Collate says Automations apply owners, domains, tags and descriptions in bulk to assets that match a filter. Source, read 13 Nov 2026. |
| Documented | by rule | Collate says Automations apply owners, domains, tags and descriptions in bulk to assets that match a filter. Source, read 13 Nov 2026. |
| Certified | by rule | Collate says it has a governance automation framework with customizable certification workflows that classify tables and dashboards as Bronze, Silver or Gold. Source, read 13 Nov 2026. |
| Quality tests pass | by rule | OpenMetadata docs say a failed data quality test case automatically opens an incident with a severity where enough information exists. Source, read 13 Nov 2026. |
| Fresh | by a person | OpenMetadata docs say a contract run does not check SLA values and that freshness must be checked with test cases added to the contract. Source, read 13 Nov 2026. |
| Sensitivity classified | by rule | OpenMetadata docs say Auto-Classification is a workflow that detects and tags sensitive data such as PII across database columns, scanning column names and sample data. Source, read 13 Nov 2026. |
| Lineage known | by rule | OpenMetadata docs say the Lineage Agent can generate column-level lineage automatically, and that users can edit it by hand. Source, read 13 Nov 2026. |
| Active use | by rule | OpenMetadata docs say the usage workflow ingests query history, and is available only for a short list of connectors (BigQuery, ClickHouse, Databricks, Exasol, MSSQL, PostgreSQL, Redshift, Snowflake) or a supplied query log file. Source, read 13 Nov 2026. |
| Metric defined | by a person | OpenMetadata docs list a metrics feature to define and govern business metrics with lineage to data assets. Source, read 13 Nov 2026. |
| Access policy allows AI use | by a person | OpenMetadata docs say PII.Sensitive columns have sample data masked except for admins, bots and table owners, and that the default policy lets every user view sample data until a Deny rule is added. Source, read 13 Nov 2026. |
OpenMetadata on the seven criteria
| Criterion | Weight | Score | Why |
|---|---|---|---|
| Labels by rule | 25 | 7 | Scheduled certification workflows set Gold, Silver, Bronze from rules and PII is auto-classified; vendor documentation only. |
| Signals a rule can read | 20 | 6 | Owner, description, tags, tier, PII, incidents, lineage and usage for some connectors; test results and freshness are not certification inputs. |
| The label reaches the agent | 20 | 6 | MCP on by default with identity scoping and tag filtering via search; none found on 2026-11-13 for certification filter. |
| Reach across the stack | 15 | 6 | Certification covers tables and dashboards and lineage propagation reaches columns; dbt and BI connectors listed; some plan marks unreadable. |
| Re-checks itself | 10 | 6 | Certification re-runs on a schedule and workflows start on change events, setting or clearing tier; withdrawal on failed test not shown. |
| Evidence beyond the vendor | 5 | 5 | Public release record and Docker pulls show adoption; the customer story is vendor-published and no analyst page readable. |
| Price transparency | 5 | 4 | Plans with included users and assets published, free tier open; no dollar prices for paid tiers. |
Where OpenMetadata is strongest
Collate ships rule-based Gold/Silver/Bronze certification workflows for tables and dashboards that re-run on a schedule, plus lineage propagation of tags, tier and owners, and an MCP server whose calls inherit the caller's or bot's access policy.
Where OpenMetadata falls short
The certification rules read owner, description, tier and custom properties rather than test results or freshness, certification is a manual control in the open-source docs read, and no MCP tool or filter by certification label was found.
OpenMetadata in each situation
| Situation | Rank | Total | Leader |
|---|---|---|---|
| Board readiness | 5th, tied with Atlan, OvalEdge and Databricks Unity Catalog | 60.0 | Euno leads at 64.5 |
| Metrics that disagree | 2nd, tied with Euno and OvalEdge | 60.5 | Euno, OpenMetadata and OvalEdge tie for first at 60.5 (listed in that order by the published rule) |
| Agent this quarter | 3rd, tied with Euno | 61.5 | OvalEdge leads at 66.5 |
| dbt, no owner list | 3rd, tied with Euno | 61.5 | OvalEdge leads at 63.5 |
| Certified data only | 4 | 62.5 | OvalEdge leads at 66.5 |
The evidence on OpenMetadata, fact by fact
- openmetadata-01 (Profile, OpenMetadata's own claim): Collate says its managed plan is OpenMetadata, fully managed, with AI agents, and lists SOC 2 Type II, SCIM 2.0 and a 99.9% SLA. Source, read 13 Nov 2026.
- openmetadata-02 (Profile, observed): The OpenMetadata GitHub repository, created 2021-08-01, describes itself as an open platform for trusted data context for humans, AI assistants, and agents; it is licensed Apache-2.0 and has about 15.8k stars and 425 contributors. Source, read 13 Nov 2026.
- openmetadata-03 (Profile, observed): The openmetadata-ingestion package on PyPI (version 2.0.8.0 on 2026-11-13) is distributed under the Collate Community License, which bars offering a competing hosted service, so the ingestion code is source-available rather than plain Apache-2.0. Source, read 13 Nov 2026.
- openmetadata-04 (Profile, OpenMetadata's own claim): OpenMetadata documentation says its connector section spans API, database, dashboard, messaging, pipeline, ML model, storage, search, metadata and drive services (339 connector pages in the v2.0.x index). Source, read 13 Nov 2026.
- openmetadata-05 (Labels by rule, OpenMetadata's own claim): Collate says it has a governance automation framework with customizable certification workflows that classify tables and dashboards as Bronze, Silver or Gold. Source, read 13 Nov 2026.
- openmetadata-06 (Labels by rule, OpenMetadata's own claim): Collate says its dashboard certification workflow is a scheduled, rule-based automation that sets Gold, Silver, Bronze or no certification. Source, read 13 Nov 2026.
- openmetadata-07 (Labels by rule, OpenMetadata's own claim): OpenMetadata docs describe Tier and Certification as system classifications with their own controls on data assets; the page describes setting them on an asset, with no rule that sets certification in the open-source docs read. Source, read 13 Nov 2026.
- openmetadata-08 (Labels by rule, OpenMetadata's own claim): Collate documents a Set Action workflow node that can set display name, description, tags, tier, status, certification and glossary terms on an asset. Source, read 13 Nov 2026.
- openmetadata-09 (Labels by rule, OpenMetadata's own claim): Collate says Automations apply owners, domains, tags and descriptions in bulk to assets that match a filter. Source, read 13 Nov 2026.
- openmetadata-10 (Labels by rule, OpenMetadata's own claim): OpenMetadata docs say Auto-Classification is a workflow that detects and tags sensitive data such as PII across database columns, scanning column names and sample data. Source, read 13 Nov 2026.
- openmetadata-11 (Labels by rule, OpenMetadata's own claim): Collate says AI Automations run agents on a schedule you define to document, test, classify and report on assets. Source, read 13 Nov 2026.
- openmetadata-12 (Labels by rule, OpenMetadata's own claim): OpenMetadata docs say a data contract has a status of Draft, In Review, Approved, Rejected, Deprecated or Archived, set through the API, and that there is no built-in approval workflow for contracts. Source, read 13 Nov 2026.
- openmetadata-13 (Signals a rule can read, OpenMetadata's own claim): Collate says certification levels come from customizable criteria on the asset itself (ownership, description, tag such as Tier, custom properties); test results and freshness are not listed as inputs. Source, read 13 Nov 2026.
- openmetadata-14 (Signals a rule can read, OpenMetadata's own claim): OpenMetadata docs say the auto-classification confidence setting (0 to 100, default 80) sets the minimum score to tag a column as PII.Sensitive, and sample-data scanning is optional. Source, read 13 Nov 2026.
- openmetadata-15 (Signals a rule can read, OpenMetadata's own claim): OpenMetadata docs say a failed data quality test case automatically opens an incident with a severity where enough information exists. Source, read 13 Nov 2026.
- openmetadata-16 (Signals a rule can read, OpenMetadata's own claim): OpenMetadata docs say a contract run does not check SLA values and that freshness must be checked with test cases added to the contract. Source, read 13 Nov 2026.
- openmetadata-17 (Signals a rule can read, OpenMetadata's own claim): OpenMetadata docs say the usage workflow ingests query history, and is available only for a short list of connectors (BigQuery, ClickHouse, Databricks, Exasol, MSSQL, PostgreSQL, Redshift, Snowflake) or a supplied query log file. Source, read 13 Nov 2026.
- openmetadata-18 (Signals a rule can read, OpenMetadata's own claim): OpenMetadata docs describe Tier 5 as unused datasets and say Data Insights helps identify them; a person sets the tier by hand. Source, read 13 Nov 2026.
- openmetadata-19 (Signals a rule can read, OpenMetadata's own claim): OpenMetadata docs list a metrics feature to define and govern business metrics with lineage to data assets. Source, read 13 Nov 2026.
- openmetadata-20 (Signals a rule can read, OpenMetadata's own claim): OpenMetadata docs say the Lineage Agent can generate column-level lineage automatically, and that users can edit it by hand. Source, read 13 Nov 2026.
- openmetadata-21 (Signals a rule can read, OpenMetadata's own claim): OpenMetadata docs say PII.Sensitive columns have sample data masked except for admins, bots and table owners, and that the default policy lets every user view sample data until a Deny rule is added. Source, read 13 Nov 2026.
- openmetadata-22 (The label reaches the agent, OpenMetadata's own claim): OpenMetadata docs say the MCP server ships installed and enabled by default. Source, read 13 Nov 2026.
- openmetadata-23 (The label reaches the agent, OpenMetadata's own claim): OpenMetadata docs say a personal access token gives the AI agent the same role and access policy as the person who created it. Source, read 13 Nov 2026.
- openmetadata-24 (The label reaches the agent, OpenMetadata's own claim): OpenMetadata docs recommend a Bot service-account token for unattended agents, with access set by role-based policy assigned to the bot. Source, read 13 Nov 2026.
- openmetadata-25 (The label reaches the agent, OpenMetadata's own claim): OpenMetadata's MCP tools reference says one call to get_entity_details can fold in business context, lineage and data quality for an asset. Source, read 13 Nov 2026.
- openmetadata-26 (The label reaches the agent, OpenMetadata's own claim): OpenMetadata's MCP tools reference lists a tool that returns AI context scoped to a persona, defaulting to the caller's active persona. Source, read 13 Nov 2026.
- openmetadata-27 (The label reaches the agent, OpenMetadata's own claim): OpenMetadata docs say the MCP server can be registered in Databricks Unity Catalog so Databricks agents can call its tools. Source, read 13 Nov 2026.
- openmetadata-28 (The label reaches the agent, OpenMetadata's own claim): Collate says an AI Studio agent runs under a chosen bot identity, and the bot determines what the agent can access and act on. Source, read 13 Nov 2026.
- openmetadata-29 (The label reaches the agent, none-found): None found on 2026-11-13: a documented MCP tool or filter that returns or filters assets by a certification label (Gold, Silver, Bronze), in the MCP Tools Reference (the word certification does not appear) Source, read 13 Nov 2026.
- openmetadata-30 (Reach across the stack, OpenMetadata's own claim): Collate says a Lineage Propagation automation applies description, tags, glossary terms, owners, tier and domain from selected assets to every asset reachable downstream through lineage. Source, read 13 Nov 2026.
- openmetadata-31 (Reach across the stack, OpenMetadata's own claim): Collate says the propagation can apply metadata to columns and fields through column-level lineage. Source, read 13 Nov 2026.
- openmetadata-32 (Reach across the stack, OpenMetadata's own claim): Collate says propagation can be halted at an asset that matches a stop condition, for example a sensitive-data marker. Source, read 13 Nov 2026.
- openmetadata-33 (Reach across the stack, OpenMetadata's own claim): OpenMetadata docs say Tableau dashboards get lineage to database services through the Tableau Metadata API; the dashboard connector docs also list Power BI and Looker. Source, read 13 Nov 2026.
- openmetadata-34 (Reach across the stack, OpenMetadata's own claim): OpenMetadata connector docs include pages to ingest tags, tiers, owners, glossary terms, lineage and exposures from dbt. Source, read 13 Nov 2026.
- openmetadata-35 (Reach across the stack, OpenMetadata's own claim): Collate's pricing page lists PII and Tiering Inheritance under Lineage with a dash in the Free Tier column; the plan marks for Premium and Enterprise did not extract as text. Source, read 13 Nov 2026.
- openmetadata-36 (Re-checks itself, OpenMetadata's own claim): Collate says certification workflows run on a schedule or on demand. Source, read 13 Nov 2026.
- openmetadata-37 (Re-checks itself, OpenMetadata's own claim): Collate says governance workflows can start on change events for chosen fields such as description, owners and tags. Source, read 13 Nov 2026.
- openmetadata-38 (Re-checks itself, OpenMetadata's own claim): OpenMetadata docs say the Data Contract Validation application runs every contract daily at midnight by default. Source, read 13 Nov 2026.
- openmetadata-39 (Evidence beyond the vendor, observed): The public GitHub release record shows OpenMetadata 2.0.8 published 2026-11-13 and a 2.1.0 release candidate the same day, so the project is under active release. Source, read 13 Nov 2026.
- openmetadata-40 (Evidence beyond the vendor, OpenMetadata's own claim): Collate's case study page quotes a Dataroots data engineer saying a Slack bot built on Collate returns a verdict in about seven minutes; the page is published by Collate, not by Dataroots. Source, read 13 Nov 2026.
- openmetadata-41 (Evidence beyond the vendor, none-found): None found on 2026-11-13: a Gartner Peer Insights, Forrester or IDC page naming Collate or OpenMetadata, in gartner.com review pages (HTTP 403 to automated reads) Source, read 13 Nov 2026.
- openmetadata-42 (Price transparency, OpenMetadata's own claim): Collate publishes three plans with included users and assets (Free 5 users and 500 assets, Premium 25 and 5,000, Enterprise 50 and 10,000), with the Free tier sign-up open and other tiers via Book a Demo. Source, read 13 Nov 2026.
- openmetadata-43 (Price transparency, OpenMetadata's own claim): Collate's pricing page says customers can stay on a plan and buy extra users and data assets, but the extracted page text shows no dollar amounts. Source, read 13 Nov 2026.
- openmetadata-44 (Price transparency, OpenMetadata's own claim): Collate's pricing page lists Automated PII Classification as a Premium-plan feature on top of the Free tier, and metadata automations as 1 on the Free tier. Source, read 13 Nov 2026.
- openmetadata-45 (Price transparency, none-found): None found on 2026-11-13: dollar prices for Collate Premium or Enterprise, in getcollate.io/pricing (plans show Book a Demo) Source, read 13 Nov 2026.
- openmetadata-46 (Evidence beyond the vendor, observed): The Docker Hub API for the openmetadata/server image shows 5,745,484 pulls and an update on 2026-11-13, an adoption signal that does not come from a vendor page. Source, read 13 Nov 2026.
- openmetadata-47 (The label reaches the agent, OpenMetadata's own claim): OpenMetadata's MCP tools reference says search_metadata accepts a raw OpenSearch query filter, with an example that filters tables by the PII.Sensitive tag, so an agent can filter by tag at query time; the reference does not mention certification. Source, read 13 Nov 2026.
Compare OpenMetadata
Sources
- www.getcollate.io, read 13 Nov 2026
- github.com/open-metadata/OpenMetadata, read 13 Nov 2026
- pypi.org/project/openmetadata-ingestion, read 13 Nov 2026
- docs.open-metadata.org/_llms/v2-0-x/connectors/connector.txt, read 13 Nov 2026
- docs.getcollate.io/ai-2-0/how-to-guides/data-governance/workflows/default-workflows/table-certification.md, read 13 Nov 2026
- docs.getcollate.io/ai-2-0/how-to-guides/data-governance/workflows/default-workflows/dashboard-certification.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/data-governance/classification/tiers.md, read 13 Nov 2026
- docs.getcollate.io/ai-2-0/how-to-guides/data-governance/workflows/elements/nodes/set-action.md, read 13 Nov 2026
- docs.getcollate.io/ai-2-0/how-to-guides/data-governance/automation/index.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/data-governance/classification/auto-classification.md, read 13 Nov 2026
- docs.getcollate.io/ai-2-0/collate-ai/ai-automations.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/data-contracts/spec.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/data-quality-observability/incident-manager.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/connectors/ingestion/workflows/usage.md, read 13 Nov 2026
- docs.open-metadata.org/_llms/v2-0-x.txt, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/data-lineage/column.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/data-governance/classification/sample-data-using-pii-tag.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/mcp.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/mcp/reference.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/how-to-guides/mcp/databricks.md, read 13 Nov 2026
- docs.getcollate.io/ai-2-0/collate-ai/ai-studio/agents.md, read 13 Nov 2026
- docs.open-metadata.org/v2.0.x/connectors/dashboard/tableau.md, read 13 Nov 2026
- www.getcollate.io/pricing, read 13 Nov 2026
- docs.getcollate.io/ai-2-0/how-to-guides/data-governance/workflows/governance-workflow-triggers.md, read 13 Nov 2026
- github.com/open-metadata/OpenMetadata/releases, read 13 Nov 2026
- www.getcollate.io/case-studies, read 13 Nov 2026
- www.gartner.com/reviews/market/metadata-management-solutions/vendor/collate/product/openmetadata, read 13 Nov 2026
- hub.docker.com/v2/repositories/openmetadata/server, read 13 Nov 2026
Last reviewed 13 Nov 2026.