Unity Catalog
Judgement: Situational
LF-open-sourced but still Databricks-tilted in practice.
Unified governance layer for tables, files, models, and functions, originally built inside Databricks and donated to the Linux Foundation.
Now competing with Iceberg REST as a catalog protocol. The two camps overlap and influence each other; expect convergence over the next couple of years.
Why it counts as a standard
Unity Catalog publishes a public REST API that other catalogs and engines can implement and consume. The API is the standard surface — that is what makes "speaks Unity" a portability claim rather than a Databricks lock-in. The reference implementation is open source under the Linux Foundation.
At a glance
- Category
- Catalog APIs
- Governance
- Linux Foundation (originally Databricks)
- Status
- Open-sourced 2024; growing ecosystem
- First released
- 2024
Links
Related standards
Other standards in Catalog APIs.
- Iceberg Catalog — Iceberg REST Catalog
- Schema Registry — Confluent Schema Registry
- DuckLake
- Hive Metastore — Apache Hive Metastore
See Unity Catalog in context
Open the interactive Data Landscape to compare Unity Catalog against every other open standard, or grab the raw JSON. Spotted something wrong? Open an issue.