Skip to content
METRIC OAK

New: the 3-week Data Platform Assessment: fixed fee, priced roadmap. See what's included →

Comparison

Unity Catalog vs Snowflake Horizon: which governance catalog?

Unity Catalog vs Snowflake Horizon: what each governs, open-source status, Iceberg interoperability, access policies and how to choose.

Hemant Walchale

Hemant Walchale
· 3 min read

If you run Databricks or Snowflake, the governance catalog is one of the decisions that is hardest to reverse. It holds your permissions, lineage and table metadata, and in 2026 it also decides which other engines can read your data. This page compares the two native catalogs: Unity Catalog on Databricks and Horizon Catalog on Snowflake.

The short answer

  • Your catalog usually follows your main platform: Unity Catalog on Databricks, Horizon on Snowflake. Neither is a reason on its own to switch platforms.
  • If several engines must read the same tables, plan around Apache Iceberg and the Iceberg REST catalog API, which both support.
  • Define access policies once per engine, and keep them as code so the two stay in step.

How they compare

Unity Catalog Snowflake Horizon Catalog
Home platform Databricks Snowflake
Open source Yes, Apache 2.0 project (fewer features than the managed version) Apache Polaris (open source) is integrated for Iceberg access
What it governs Tables, views, volumes (files), functions, ML models Tables, views and other Snowflake objects, plus Iceberg tables
Table formats Delta Lake and Iceberg Snowflake tables and Iceberg tables
External engines Iceberg REST and Delta Sharing Iceberg REST through Horizon (Polaris)
Access control Grants on catalogs, schemas and objects; row filters and column masks Role-based grants; row access and masking policies
Lineage Captured automatically for workloads that run on Databricks Captured for Snowflake objects
Data sharing Delta Sharing, an open protocol Secure data sharing and Marketplace

What usually decides it

  1. Your main engine. Each catalog is strongest for the engine it ships with: that’s where lineage capture, policy enforcement and auditing are most complete.
  2. Files and models, not just tables. Unity Catalog governs files in volumes and ML models alongside tables, which matters for AI teams working with documents.
  3. Many engines. If Spark, Trino, Flink or DuckDB also need the data, make Iceberg the table format and use a REST catalog both platforms understand.
  4. Moving off Hive metastore. Databricks estates still on the legacy Hive metastore should plan the upgrade to Unity Catalog first.

Policies are the hard part

Sharing table metadata across engines is now straightforward. Sharing policies isn’t: a masking rule defined in Unity Catalog doesn’t apply when Snowflake reads the same Iceberg table, and the reverse is also true. Keep grants, row filters and masks in code (Terraform or SQL in Git) and test both engines with the same user identities. This is the work that auditors check; see what is data lineage and BCBS 239 lineage.

The short version

Use the catalog that comes with your main platform, use Iceberg when more than one engine needs the data, and manage access policies as code in both places. For the platform decision itself, see Databricks vs Snowflake and what is Unity Catalog.

Sources

Not sure where your own platform stands? Take the free 3-minute data platform scorecard, or see how we work on Databricks. Need people to do this alongside your team? See data engineering consulting. Unfamiliar terms are explained in the data engineering glossary.

Frequently asked questions

Is Unity Catalog open source?

Yes. Databricks open-sourced Unity Catalog under the Apache 2.0 license, with an OpenAPI specification and a server implementation. The managed Unity Catalog inside Databricks has more features than the open-source project, so check which capabilities you need before planning to run the open-source version.

What happened to Snowflake Open Catalog and Polaris?

Snowflake created Polaris Catalog, an Iceberg REST catalog, and donated it as the open-source Apache Polaris project. Snowflake Open Catalog was the managed service built on it. Snowflake's documentation now says customers who haven't had an Open Catalog account can't sign up for one, and that Apache Polaris is integrated into Horizon Catalog for external engines.

Can one catalog govern both Databricks and Snowflake?

Partly. Both can read Iceberg tables through REST catalogs, so one catalog can be the source of table metadata for both engines. Row filters, masking policies and grants are still enforced by each platform's own engine, so you will define some policies in both places.

Have 30 minutes? Get a senior architect’s view of your data platform.

No sales deck. You talk to the engineer who would lead the work.

Book an architecture review
Hemant WalchaleYou talk to Hemant Walchale, founder145 published guidesProfiles: LinkedIn · Clutch · GoodFirms

Free, takes 20 seconds

Get your starter data platform roadmap

Pick your platform and your main goal. You get a 90-day plan written by senior data engineers: what to do first, next and after.

You’ll also get our monthly email (confirm it in your inbox). Unsubscribe any time. Privacy policy.