Matia Deepens Integration with Databricks Unity Catalog to Unify Lineage and Metadata


Today at Databricks Data and AI Summit 2026, we're announcing a deeper integration between Matia and Databricks Unity Catalog.
If you run Databricks, you already keep a lot of important context in Unity Catalog. Tags that mark sensitive data, descriptions that explain what an asset is for, and the lineage that ties notebooks, jobs, and tables together. That context is valuable, but it lives in Databricks. The rest of your data picture lives somewhere else.
This integration closes that gap. Matia now brings Unity Catalog metadata directly into the Matia Catalog, so your Databricks tags, descriptions, and lineage show up alongside everything else Matia already tracks, in one place. And because that metadata becomes part of Matia's graph, it isn't just visible. It's queryable by an agent, wherever your team works.
Your Databricks context now lives in the Matia Catalog
The integration brings tags and descriptions from Unity Catalog into the Matia Catalog.
Your Unity Catalog asset tags are surfaced in Matia, so the labels you already use to classify and govern data carry over instead of being recreated by hand. Asset descriptions written in Unity Catalog are pulled in too, so the context a teammate added in Databricks is visible to everyone working in Matia.
In other words, the governance work your team already did shows up where the rest of your team can find it, not trapped in a tool only the Databricks admins open.
Matia stitches native Databricks lineage with dbt lineage into one view
Lineage no longer needs to be fragmented. Matia captures native Databricks lineage by querying Unity Catalog system tables, and enriches it by parsing your dbt artifacts. Together they give you a fuller, dbt-aware map of how your Databricks assets connect, in a single view.
That makes it easier to trace where data came from, understand what a change will affect, and triage an issue without hopping between tools.
This deepens an integration that already runs deep
This isn't a standalone bolt-on. It sits on top of the ETL, Reverse ETL, and Observability that Matia already runs alongside Databricks. Teams like Lev use Matia to move data in and out of Databricks, run dbt models, and activate the results in their operational tools, with observability across the whole path.
The Unity Catalog integration adds the governance layer to that same picture. Ingestion, activation, monitoring, and metadata all live together rather than in four disconnected tools. That's the advantage of a unified DataOps platform: your Databricks data doesn't just move through Matia, it's described, monitored, and connected in one place.
The metadata isn't just visible. It's queryable by an agent, wherever you work
Once your Databricks tags, descriptions, and lineage are in Matia, they become part of a graph that Matia's MCP can reason over. That turns metadata from something you look at into something an agent can act on.
Point an agent at it in whatever client your team already uses, and ask the questions that usually take an afternoon of digging:
- Trace what depends on a table before you drop it, across tables, columns, dashboards, and the people who rely on it.
- Find the root cause behind a wrong number on a dashboard, tracing upstream to the integration or monitor that caused it.
- Decide which monitors protect a critical asset, by pointing the agent at the dashboard that matters.
Your metadata stays open to the tools you choose, not locked to one. That means Claude, Cursor, ChatGPT, Slack, or any other MCP-enabled client.
Get started
The Databricks Unity Catalog integration is available now for teams using Matia with Databricks. If you're already connected, your Unity Catalog tags, descriptions, and lineage will start surfacing in the Matia Catalog. If you're at Databricks Data and AI Summit this week, come find us. If you're evaluating Matia, this is a good moment to see what a unified view across your Databricks stack looks like.
And if you're at Databricks Data & AI Summit, stop by to see it in person at booth 525.
View the docs here.
.png)



