New Native Oracle. Graph-native. Column-level.

See where your data
comes from. Know where it goes.

VIA is a native Oracle data catalog and lineage platform. Column-level lineage analysis that takes a senior engineer over an hour by hand is done in 5–10 minutes.

Book a demo See how it works

PREDICTION_PLAYER.PTS_FINAL

Column detail

PTS_FINAL

WKSP_VIA.PREDICTION_PLAYER

as of 2026-04-28

Resolution

Resolved 100%

Partial 0%

Unresolved 0%

Expression — PTS_FINAL

PREDICTION_PLAYER.PTS_FINAL:

DISTINCT_FINAL.PTS_FINAL

DISTINCT_FINAL.PTS_FINAL:

EXP_ROUNDING_FINAL.PTS_FINAL

EXP_ROUNDING_FINAL.PTS_FINAL:

CASE WHEN EXP_COMBINED_CALCS.POSITION IN ('WR','TE','RB')
THEN ROUND(EXP_COMBINED_CALCS.PTS_FINAL,1)
WHEN EXP_COMBINED_CALCS.POSITION IN ('QB')
THEN ROUND(EXP_COMBINED_CALCS.PTS_FINAL,2)
WHEN EXP_COMBINED_CALCS.POSITION IN ('DST','K')
THEN ROUND(EXP_COMBINED_CALCS.PTS_FINAL,0)
END

EXP_COMBINED_CALCS.POSITION:

ANALYTICS_ALL_POSITIONS_PTS_PREDICTION.POSITION

EXP_COMBINED_CALCS.PTS_FINAL:

(ANALYTICS_ALL_POSITIONS_PTS_PREDICTION.PTS +ANALYTICS_ALL_POSITIONS_PTS_PREDICTION_LAST_3_WEEK.PTS)/2

PREDICTION_PLAYER.CEILING_FINAL:

DISTINCT_FINAL.CEILING_FINAL

DISTINCT_FINAL.CEILING_FINAL:

EXP_ROUNDING_FINAL.CEILING_FINAL

EXP_ROUNDING_FINAL.CEILING_FINAL:

CASE WHEN EXP_COMBINED_CALCS.POSITION IN ('WR','TE','RB')
THEN ROUND(EXP_COMBINED_CALCS.CEILING_FINAL,1)
WHEN EXP_COMBINED_CALCS.POSITION IN ('QB')
THEN ROUND(EXP_COMBINED_CALCS.CEILING_FINAL,2)
WHEN EXP_COMBINED_CALCS.POSITION IN ('DST','K')
THEN ROUND(EXP_COMBINED_CALCS.CEILING_FINAL,0)
END

EXP_COMBINED_CALCS.CEILING_FINAL:

(NVL(ANALYTICS_ALL_POSITIONS_PTS_PREDICTION.CEILING,ANALYTICS_ALL_POSITIONS_PTS_PREDICTION.PTS)
+NVL(ANALYTICS_ALL_POSITIONS_PTS_PREDICTION_LAST_3_WEEK.CEILING,ANALYTICS_ALL_POSITIONS_PTS_PREDICTION_LAST_3_WEEK.PTS))/2

EXP_COMBINED_CALCS.POSITION:

ANALYTICS_ALL_POSITIONS_PTS_PREDICTION.POSITION

What VIA is

The streets of your
DB, visualized.

VIA (Visual Interactive Analysis) is an Oracle-native data catalog and lineage platform. It reads pipeline metadata from any ETL metadata source — with legacy PL/SQL support coming soon — builds a graph of every table, column, join, filter, and transformation, and resolves complex column-level lineage through a graph-based inference engine.

Unlike traditional lineage tools that show only the current state, VIA also adds historical insight — so you can investigate how data flows and logic looked at any point in time.

Native Oracle

Built on a cloud database with Oracle APEX and Property Graphs. Runs as a plug-in — no new vendor, no data egress.

Graph-native

Tables, columns, joins, filters and transformations as a live property graph. Multi-hop traversal is a first-class operation.

Column-level

Resolves complex SQL expressions hop by hop. Not table-to-table — every column traced to its origin.

Time-aware

Every change tracked with SCD2. Travel back to any historical snapshot — see lineage as it looked on any date.

What problems VIA solves

Four things every data team
quietly struggles with.

Modern databases run on thousands of ETL processes. Critical knowledge lives only in code, stale docs, and tribal memory. VIA replaces all three with a queryable graph.

Hidden data origins

When users question a KPI or report, the answer is buried in ETL logic and undocumented dependencies. VIA makes data origins visible and traceable.

// WHERE DOES THIS COME FROM?

Unclear change impact

Schema and logic changes can affect many downstream reports — but the impact is often discovered too late. VIA shows what could break before a change is made.

// WHAT DOWNSTREAM BREAKS?

Audit and compliance pressure

Regulatory requests need more than a current-state view. VIA's historical lineage explains how data and calculations looked during any reporting period.

// WHAT DID IT LOOK LIKE THEN?

Knowledge loss

Critical system understanding lives in code or in the heads of a few experts. When they leave, it leaves with them. VIA captures and visualizes that knowledge.

// WHO STILL KNOWS THIS?

How it works

Think Google Street View,
but for your DB.

VIA surveys every street and alley in your database, records the current and historical state of all connections, and lets anyone walk the data floor — no map-reading skills required.

Read ETL metadata

Extract

VIA reads your ETL pipeline metadata and detects new or changed processes. Only changes are reprocessed.

SCD2 MANAGER

→ Fresh metadata, always current.

Construct a property graph

Build

The graph engine converts raw ETL expressions into a network of nodes (tables, columns) and edges (transformations, joins, filters).

GRAPH BUILDER

→ A property graph of the warehouse.

Resolve column-level lineage

Infer

The inference engine traverses the graph, resolving complex SQL expressions until every column's true source is known.

INFERENCE ENGINE

→ Column-level lineage, fully resolved.

Explore by clicking

Visualize

APEX queries the property graph and renders an interactive Cytoscape.js visualization. Pan, zoom, time-travel — no SQL required.

APEX · Cytoscape.js

→ Self-service lineage for everyone.

Incremental processing keeps refreshes fast.

Only ETL processes that have actually changed are reprocessed — a routine catalog refresh completes in minutes even on warehouses with thousands of mappings.

Refresh

~minutes

Mappings

thousands

Traversal

unlimited

What VIA helps you achieve

Outcomes, not just diagrams.

VIA isn't a passive catalog. It's an active instrument that data engineers, analysts, and governance teams reach for when something matters.

5–10 min

vs. 1+ hour by hand

Trace data with confidence

Follow data from source to target across transformations, joins, and filters with column-level detail. No more SQL archaeology.

Any date

queryable history

Investigate the past

Travel back to understand how lineage, dependencies, and calculation logic looked on any specific date. SCD2 history, queryable.

Instant

downstream blast radius

Assess impact faster

See every downstream table and column affected by a change — before you make it. Reduce incident analysis from hours to minutes.

0 SQL

for non-engineers

Enable self-service

Give analysts, engineers, and governance teams an interactive way to explore the data landscape — no SQL required.

Questions VIA helps answer

Real questions.
Real answers.

01 Where does this data come from?
02 Where did it come from six months ago?
03 Why did this report show that value on that date?
04 What changed in the logic?
05 What would be affected if we changed this object?

From the Oracle ecosystem

VIA does something we've wanted from the Oracle Data Integrator ecosystem for years — turn invisible column-level lineage into something a data team can actually navigate. It's native, it's graph-powered, and it lives where Oracle data already lives. We expect a lot of teams across the Oracle ecosystem to find this incredibly valuable.

Oracle Database & APEX team

Partner perspective · Oracle ecosystem

ORACLE

FAQ

Questions, answered.

Don't see what you're looking for? We'll walk you through it on a demo.

Book a demo

01 Do we need to install or license any external software?

No. VIA runs as a plug-in inside your existing database — cloud or on-premise. There is no new vendor and no additional licensing fee.

02 How is VIA different from a third-party data catalog?

Most catalogs work from metadata too — but stop at table-to-table links. VIA goes further: it resolves lineage recursively through the actual SQL expressions (including filters and join conditions), renders it as an interactive property graph you can traverse in any direction, and tracks every change over time with a built-in timeline so you can see how lineage looked on any past date.

03 How does the time-travel capability work?

Every mapping, table, join, and column transformation is versioned with effective dates using the SCD2 pattern. Temporal property graph snapshots are created automatically. You pick a date in the APEX UI and see lineage exactly as it existed then — no manual export, no archive restore.

04 How long does a refresh take on a real database?

Routine refreshes complete in minutes, even on databases with thousands of ETL mappings. VIA's incremental engine compares the current ETL state against its last known state and only reprocesses mappings that have actually changed.

05 What does deployment look like?

You deliver your ETL metadata to VIA, which injects it into the cloud database and runs an initial load to build the full lineage graph. From there, incremental loads — typically daily, weekly, or monthly — pick up only what has changed. Routine operations are scheduled and largely self-maintaining.

See VIA in action