SQL, ETL & BI parsing
Describing how data moves is painstaking work, and even careful documentation drifts as pipelines change. OntaVera reads lineage from the SQL, ETL jobs, and BI definitions that actually run, so the graph reflects production code rather than a point-in-time description of it.
The engine parses SQL, stored procedures, ETL pipelines, and BI report definitions into column-level lineage.
Connectors cover warehouses, databases, ETL tools, and BI layers, with no per-connector fees.
The platform reads code and metadata only, so no data leaves your systems; BYOK and air-gapped deployment are both supported.
Every parsed edge links back to the exact statement it came from, so you can show the evidence behind the picture.
Whatever the parser cannot resolve, such as dynamic SQL or an unsupported job type, is flagged as a named gap and is never silently dropped.
The platform re-parses as code changes, so lineage tracks the pipelines as they evolve rather than freezing at a point in time.
Connect
Read-only connectors pull code and metadata from your warehouses, schedulers, and BI tools.
Parse
The engine resolves each statement into column-level inputs and outputs, dialect by dialect.
Attach evidence
Each edge stores the statement, the source system, and the scan time it was derived from.
Flag gaps
Anything unresolved lands as an explicit gap on the graph, because absence is treated as a failure rather than a quiet hole.
“Is this lineage documented by hand, or actually read from the code?”
It is read from the code. The engine parses SQL, stored procedures, ETL pipelines, and BI definitions into column-level lineage, and every edge links back to the exact statement it came from.
“What happens when there is SQL the parser cannot read?”
Anything the parser cannot resolve, such as dynamic SQL or an unsupported job type, is flagged as a named gap on the graph. Nothing is silently dropped, so you always know where the picture is complete and where it is not.
“Does this keep up when the pipelines change?”
Yes. The platform re-parses as code changes, so the lineage graph tracks your pipelines as they evolve rather than freezing at a point in time.
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.