Impact & blast radius
Before a schema change or a pipeline fix ships, you want to know every report, model input, and CDE it touches. OntaVera walks the lineage graph downstream and gives you the full blast radius, drawn from parsed evidence so the assessment stands on its own.
You see the downstream impact for any column, table, or job: every report line, dashboard, model input, and CDE it feeds.
Regulatory exposure is called out, so you know when the downstream set includes a CDE or a line on a regulatory report.
The upstream view supports incident work: when a number breaks, the graph orders the candidate causes for you.
Lineage gaps along the path are surfaced with the result, so you know where the blast radius is backed by evidence and where it runs out.
Agents can propose the owner notification list for a change, and a human decides who is told and who signs off.
Each impact assessment can be sealed to the hash-chained ledger, so at exam time you can show what you knew before you shipped.
Pick a node
Start from the column, table, or job you plan to change.
Walk downstream
The graph traverses every parsed edge out to reports, models, and CDEs.
Weigh it
Impacted assets appear with their tags, including CDE status, report mappings, and open issues, so severity is visible at a glance.
Seal
The assessment seals to the ledger as part of the change record.
“If we change this column, what breaks?”
Pick the column and the graph walks every parsed edge downstream, returning every report line, dashboard, model input, and CDE it feeds. Regulatory exposure is called out, so you know immediately when a regulatory report sits in the blast radius.
“Did anyone assess impact before this change went out?”
You can prove it. Each impact assessment can be sealed to the hash-chained ledger as part of the change record, so at exam time you can show exactly what you knew before you shipped.
“Which regulatory reports does this table feed?”
Walk downstream from the table and the impacted assets appear with their report mappings and CDE status. Any line on a regulatory report in the downstream set is called out explicitly.
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.