Data contracts enforcement.
Schema and semantic guarantees enforced at the boundary between data producers and consumers.
What counts as Data contracts enforcement?
A data contract specifies what a table or stream must always look like — column names, types, semantics, freshness — and is enforced by tooling rather than by Slack reminders. Tools in this category either declare contracts on the catalog side, or block writes/reads that violate them on the testing side. The strongest implementations do both.
5tools, grouped by primary cluster.
Atlan
Atlan
Enterprise catalog and governance plane positioned as the AI context layer — connectors, lineage, contracts, and an MCP server for agents.
Collibra
Collibra
Enterprise data-and-AI governance incumbent: catalog, glossary, workflow stewardship, lineage, and a separate ML data-quality module.
DataHub
Acryl Data
Apache-2.0 metadata platform with a serious managed counterpart — strongest event-driven architecture and column-level SQL lineage in OSS.
OpenMetadata
Collate
Apache-2.0 unified metadata platform with a deliberately simple stack — discovery, lineage, quality, and contracts in one project.
Head-to-head, side by side.
Drill into a different capability.
How this list is built.
Inclusion here is one boolean on each tool's structured profile — if a tool you'd expect is missing, the field is recorded false or not yet verified, never an editorial call. See the methodology for how each field is sourced.