Skip to content
Platform · Catalog

Asset inventory & business glossary

Connect your systems read-only and OntaVera builds the inventory itself: every system, dataset, and column, with business terms attached where the evidence supports the link. Banks care because attestation starts with a complete inventory, and keeping one current by hand is genuinely difficult work at bank scale. This one is derived directly from your systems and moves with them.

What you get01 / 03
01

Automated discovery runs across native connectors for the systems a first report needs, with OpenLineage ingest and an SDK for the rest, covering warehouses, lakes, core banking platforms, and marts, with no per-connector fees.

02

OntaVera works with metadata only: it reads structure and profiles in place, retains none of your data, and supports BYOK and air-gapped deployment.

03

The business glossary is wired to physical columns, and each term-to-column link is a claim checked against evidence rather than a free-floating definition.

04

Imported inventories and glossaries land as claims as well, so the catalog work your teams have already done is verified against what the scanners actually find.

05

You get coverage you can defend: a system you have not scanned shows up as a gap, because absence is treated as failure.

06

Every addition, edit, and term approval is sealed on the hash-chained ledger.

How it works02 / 03
1

Connect

Point read-only connectors at your systems; nothing is copied out.

2

Discover

Scanners walk schemas and profiles and build the asset graph automatically.

3

Attach terms

Glossary terms link to columns as claims that evidence confirms or contests.

4

Stay current

Scheduled rescans pick up drift, and a missed scan surfaces as a gap rather than a silent blank.

Questions it answers03 / 03

“Do we actually have a complete inventory of our systems and CDEs?”

Yes, and it is derived from your systems rather than compiled by hand. OntaVera discovers every system, dataset, and column through read-only connectors, and any system you have not scanned shows up as a gap, so completeness is measured rather than assumed.

“What does this column mean in business terms?”

Each column carries the glossary terms linked to it, and every term-to-column link is a claim checked against evidence. You see the business meaning alongside the physical structure, with confirmation that the link actually holds.

“How current is this inventory, and what does it not cover?”

Scheduled rescans keep the inventory moving with your systems, so it is as current as your scan cadence. Anything not covered surfaces explicitly as a gap, because absence is treated as failure rather than left as a silent blank.

The next step

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.

01

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.

02

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.

03

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.