01Data product & mesh platforms
Witboost
A data product management platform from Agile Lab for building, deploying and governing data products across domains.
Best for: Self-serve data product platform.
Visit Witboost →Data Mesh Solutions
Platforms and tools for building a data mesh: data product platforms, federated query, catalogs and governance, quality and observability, and cloud data platforms.
28solutions
6Categories
6FAQs answered
02Data product & mesh platforms
Entropy Data (Data Mesh Manager)
A catalog and management tool for data products and data contracts, built around data mesh practice.
Best for: Managing data products and contracts.
Visit Entropy Data (Data Mesh Manager) →03Data product & mesh platforms
Nextdata
A data product platform from the team behind the data mesh concept, built around autonomous data products.
Best for: Data-product-first architecture.
Visit Nextdata →04Federated query & virtualization
Starburst
A federated query and lakehouse platform built on Trino, used to give domains access to distributed data.
Best for: Querying data where it lives.
Visit Starburst →05Federated query & virtualization
Trino
An open-source distributed SQL query engine for running analytics across many data sources.
Best for: Open-source federation engine.
Visit Trino →06Federated query & virtualization
Dremio
A lakehouse platform with a semantic layer and query acceleration, used for self-service analytics.
Best for: Self-service lakehouse analytics.
Visit Dremio →07Federated query & virtualization
Denodo
A data virtualization platform that offers a logical layer over distributed data sources.
Best for: Logical data access without copying data.
Visit Denodo →08Cloud data platforms
Databricks Unity Catalog
Databricks' governance layer for data and AI assets, with access control, lineage and sharing.
Best for: Governed domains on a lakehouse.
Visit Databricks Unity Catalog →09Cloud data platforms
Snowflake
A cloud data platform with data sharing and a marketplace, often used to publish data products between domains.
Best for: Sharing data products across accounts.
Visit Snowflake →10Cloud data platforms
Google Cloud Knowledge Catalog (formerly Dataplex)
Google Cloud's data governance and metadata service for managing data across lakes, warehouses and domains.
Best for: Governance across Google Cloud data.
Visit Google Cloud Knowledge Catalog (formerly Dataplex) →11Cloud data platforms
Amazon DataZone
AWS's data management service for cataloguing, sharing and governing data across organisational units.
Best for: Data sharing across AWS accounts.
Visit Amazon DataZone →12Cloud data platforms
Microsoft Fabric
Microsoft's unified analytics platform, with domains and OneLake as a shared data layer.
Best for: Microsoft-centred estates.
Visit Microsoft Fabric →13Catalog, governance & access
Microsoft Purview
Microsoft's data governance, catalog and compliance portfolio.
Best for: Governance across Microsoft and multicloud data.
Visit Microsoft Purview →14Catalog, governance & access
Collibra
A data intelligence platform for governance, cataloguing and data product marketplaces.
Best for: Enterprise governance.
Visit Collibra →15Catalog, governance & access
Atlan
A metadata and catalog platform built around collaboration, lineage and active metadata.
Best for: Modern data catalog.
Visit Atlan →16Catalog, governance & access
Alation
A data catalog and governance platform for finding, understanding and trusting data.
Best for: Search and trust in data.
Visit Alation →17Catalog, governance & access
DataHub
An open-source metadata platform for discovery, lineage and governance.
Best for: Open-source metadata.
Visit DataHub →18Catalog, governance & access
OpenMetadata
An open-source metadata platform covering discovery, lineage, quality and governance.
Best for: Open-source catalog and governance.
Visit OpenMetadata →19Catalog, governance & access
Immuta
A data security platform for policy-based access control across data platforms.
Best for: Federated access policies.
Visit Immuta →20Catalog, governance & access
Informatica
A cloud data management platform covering integration, quality, catalog and governance.
Best for: Enterprise data management.
Visit Informatica →21Catalog, governance & access
Ataccama
A data quality, governance and master data platform.
Best for: Quality and governance in one platform.
Visit Ataccama →22Quality & observability
Soda
Data quality testing and monitoring, including data contract checks.
Best for: Checking data product quality.
Visit Soda →23Quality & observability
Monte Carlo
A data observability platform for detecting and investigating data incidents.
Best for: Reliable data products.
Visit Monte Carlo →24Quality & observability
Great Expectations
An open-source framework for validating data against expectations.
Best for: Testable data quality rules.
Visit Great Expectations →25Transformation & streaming
dbt
A transformation framework that supports multi-project setups with governed model access across teams.
Best for: Domain-owned transformations.
Visit dbt →26Transformation & streaming
Dagster
An orchestration platform built around data assets, used to build and monitor data pipelines.
Best for: Asset-based pipelines.
Visit Dagster →27Transformation & streaming
Confluent
A data streaming platform based on Apache Kafka, used to publish real-time data products.
Best for: Streaming data products.
Visit Confluent →28Transformation & streaming
Apache Kafka
The open-source distributed event streaming platform behind many real-time data products.
Best for: Open-source event streaming.
Visit Apache Kafka →Mesh or fabric?
Data mesh is mainly an organisational approach built on domain ownership and data products, while a data fabric is a technology layer that connects and governs data across systems. They are often used together. Our comparison explains how to choose.
Choosing the right approach
Match your requirement to a starting point, then compare vendors.
| Starting a data mesh | A data product platform plus a catalog; agree ownership and standards first |
|---|---|
| Data stays in many systems | Federated query or virtualization such as Trino, Starburst or Denodo |
| Already on one cloud | The native governance and sharing services of that cloud |
| Trust in data products | Data contracts with quality tests and observability |
| Real-time products | Streaming with Kafka or Confluent |
| Central control matters most | A data fabric approach, see the comparison |
Related pages on PeterIndia.net
Neighbouring directories and hubs.
Data Fabric vs. Data MeshChoosing between them.Data Fabric SolutionsFabric platforms compared.Enterprise Data Fabric SoftwareMore fabric vendors.Data Governance PlatformsPolicies and control.Enterprise Data CatalogsFind and understand data.Data Observability ToolsMonitor data health.Data Quality SolutionsFix and prevent bad data.Data Integration, ETL and CDC ToolsMove and transform data.Service MeshesMesh for microservice traffic.Event MeshesMesh for events.AI Agent Meshes and InteroperabilityMesh for AI agents.Data EngineeringThe data engineering hub.
Frequently asked questions
Quick answers.
What is a data mesh?
A data mesh is a decentralised approach to analytics data, built on four ideas: domain ownership, data as a product, a self-serve data platform and federated governance.
Can I buy a data mesh?
Not as a single product. A mesh is mostly an organisational and architectural approach. Vendors supply the platform pieces: data product tooling, catalogs, federated query, governance and quality.
What is a data product?
A data product is a dataset or data service owned by a domain team, with a clear interface, documentation, quality guarantees and a contract describing what consumers can expect.
What is federated governance?
Central teams set the rules that apply to everyone, such as security and interoperability, while domain teams apply them to their own data products, ideally through automated policies.
How is a data mesh different from a data fabric?
A mesh organises people and ownership around domains. A fabric is a technology layer that connects and governs data across systems, often using metadata and automation. They can be combined.
Is a data mesh right for every company?
No. It suits large organisations with several domains and data teams. Smaller teams may do better with a central platform first.
Descriptions summarise each vendor's or project's own positioning, checked on 5 October 2026. Product names and offerings change often, so confirm details on the linked site before deciding.