lineageatlas

Object catalog 50

⌘ K

Names, paths, owners, columns & code.
Try customer_id or type:mp risk

50 objects

Northstar Bank · Demo50 fictional objects · 10 object types

Workspace / Impact explorer

Fictional metadata

Understand every dependency

See what changes downstream.

Trace an object through your pipelines, data products, and people.

DOWNSTREAM LINEAGE

Drag to explore · Columns = shortest hops · Select a node to trace its path

80%

DMLPSETGraphSQL / DataProductPeople

Dependency →

Traverses every reachable dependency; each object is counted once.Illustrative lineage · Impact means potentially affected

Follow the change, end to end.

Choose any catalog object as your source. Atlas follows outgoing dependencies across every level, including parameter references, schemas, reads, writes, applications, and users.

Search everything: names, paths, descriptions, owners, tags, columns, and sample code. Use type:mp, owner:maya, tag:pii, or column:customer_id to narrow results. Multiple terms are combined.
Trace a path: select a graph node or impact row. The highlighted route is one shortest dependency path. All reachable objects remain in the impact count.
Keep context: type filters dim other graph nodes instead of removing connecting paths. The list shows only matching results.
Move around: drag, use the minimap, or zoom. F fits the graph; Esc leaves expanded mode. Ctrl / ⌘ K searches.

This is a self-contained, fictional 50-object demo. It does not connect to an Ab Initio repository. The sample omits runtime and column-level impact inference.