02 · Model & trust
Data lineage
Every column, traced.
From the source to the dashboard, built from the pipelines that actually run. Nothing to draw, nothing to keep up to date.
Source
- order_id
- amount
- status
- charge_id
- amount
- currency
Staging
- order_id
- amount_usd
- status
Mart
- order_date
- revenue
Used by
- Revenue
- Orders
Impact
Change one model. See everything it touches.
Pick any asset or column and see every model, dashboard and brief downstream of it, across pipelines and projects.
Source
Staging
Mart
Used by
Owners
Know who to tell. Before they find out.
Lineage carries owners and tiers, so a change or a failed check reaches the people downstream, starting with what matters most.
Downstream of stg.orders
4 assets · 3 teams
Built from code
Nothing to draw. Nothing to maintain.
- Generated from code
- Read from the pipelines that run, across every project. Always current, never hand-drawn.
- Source to dashboard
- From the ingestion source, through every model, to the dashboard and the AI answer.
- SQL and Python
- Lineage crosses languages, so a Python model is not a black box in the graph.
- With the metadata
- Owners, tiers, cost and usage sit on the same assets as the lineage.
Customer results
Numbers from teams on Bruin.
95% faster
error detection and resolution
Read the Spektra Games story
4x faster
time to insight
Read the Workhy story
~1 week
for a new engineer to be productive
Read the Fabrikatör story
The platform
Part of the Bruin platform.
Lineage runs through every piece, from the ingestion source to the AI answer.
Raw tables, in your warehouse
Tested, governed models
Your stack, your call
Replace the modern data stack.
One layer or every layer. Keep what works, swap what doesn't.
Today
On Bruin
Layer
What teams run today
On Bruin
Ingestion
On Bruin: Data Ingestionon open-source ingestr
Transformation & orchestration
On Bruin: SQL & Python + Bruin Cloud
Quality, lineage & catalog
On Bruin: Data Quality + Data Lineage
BI & dashboards
Power BI
On Bruin: AI Dashboards + Data Apps
AI on your data
On Bruin: AI Data Analyst + Scheduled Agents
Frequently asked
Questions about lineage.
Is the lineage column-level?
Yes. Bruin traces columns through SQL models, so you can follow a single figure on a dashboard back to the source columns it came from, and see which columns a change reaches.
How is the lineage built?
From the pipelines themselves: the assets, their SQL, their declared dependencies and the ingestion that feeds them. There is nothing to draw or annotate by hand, and it updates when the code does.
Does it go beyond the warehouse?
Yes. Because ingestion runs on Bruin, lineage starts at the source system, and it continues past the models to the dashboards, data apps and AI answers built on them.
Can I see the impact of a change?
Pick any asset or column and Bruin shows everything downstream of it, across pipelines and projects, together with the owners of those assets. When a quality check fails, the same graph shows what was held back.
Does it show owners?
Yes. Assets carry owners, and lineage rolls them up into owner lineage: which teams depend on which, and who to tell about a change. Asset tiers mark what matters most.
Do we still need a separate catalog?
For what runs on Bruin, lineage, owners, tiers and metadata live in Bruin Cloud next to the pipelines, so there is no second system to keep in sync. Teams with a wider catalog can keep it for the systems Bruin does not run.
Is it part of the open-source CLI?
The open-source Bruin CLI knows the full dependency graph of your pipelines. The interactive lineage view, with columns, owners and metadata, is part of Bruin Cloud.
Every number, back to its source.
$100 in credits and 50 AI tasks. No credit card.