Column-level & business lineage
When an examiner points at a number on a report, you need to show the exact columns that produced it. OntaVera traces every report line down to source columns, and it pairs that technical view with a business view your stewards and second line can read without an engineer in the room.
Trace any report line to the physical source columns behind it, transformation by transformation.
Two views sit on one graph: technical lineage for engineers, and business lineage in plain terms for stewards, second line, and auditors.
CDE lineage is derived from parsed code and scanned metadata, so the graph is generated from evidence and cannot be quietly edited.
Every lineage edge carries its evidence: the parsed statement, the connector scan, and the time it was read.
A hop with no evidence shows as unknown, and unknown counts as a finding rather than a pass.
Lineage sits on the same governed knowledge graph as your catalog, quality, and issues, which gives you one graph across all ten products.
Scan
Read-only connectors pull metadata from your warehouses, ETL tools, and BI layer. They read metadata only, copy nothing, and retain no data.
Derive
The platform parses the code and builds column-level edges. Lineage is derived from evidence and is never set by hand.
Map terms
Business terms and CDEs are linked onto the technical graph, so both views describe the same underlying edges.
Seal
Each lineage snapshot is sealed on the hash-chained ledger, so what you show at exam time is what the graph said that day.
“Where did this number on the report actually come from?”
OntaVera traces the report line back to the physical source columns that produced it, transformation by transformation. Every hop carries the parsed statement and connector scan behind it, so the answer arrives with its evidence.
“Can you show me column-level lineage for our CDEs, and prove it is derived rather than manually documented?”
Yes. CDE lineage is derived from parsed code and scanned metadata, every edge stores the statement and scan it came from, and each snapshot is sealed on the hash-chained ledger so it cannot be quietly edited.
“Which source columns feed this line of the capital report?”
Start from that report line and the graph walks you back to every physical source column behind it. Where a hop lacks evidence, it shows as unknown and is treated as a finding rather than a pass.
Start with proof, not a promise.
There are three ways in, and each one earns the next. You approve the exit criteria before we spend any more of your time or budget.
A 60-minute working session
Bring one report that is expensive to prove. We walk the mechanism against it. Nothing is required from your side.
A two-week guided sandbox
Your team works hands-on against a synthetic sample bank. It requires zero access to your systems and zero procurement.
A six-week proof on your systems
We use read-only metadata across five systems and one priority report, scored against criteria both sides sign first. The decision it produces is yours.