Browse every source
A single schema browser spans the Vault and the Mart, with every source, schema, table and view.
HighlightsYour data,
The Catalog
Your data,
in one catalog.
Every table and view across the Vault and the Mart in one place: browsing, querying in the built-in SQL editor, lineage on any column, and notes and tags. There is no extra tool to buy.
The concept
The schema, the views and the lineage, in one place.
Your team's notes and tags sit beside them.
A built-in SQL editor
Views are written and edited in the built-in SQL editor, with full syntax highlighting.
Lineage from the SQL
Clicking any table or column in the SQL opens its full lineage, back to the source and forward to every Mart view.
Notes and tags
Tables, views and Vault columns carry notes and tags that everyone reads. Authors keep developer notes beside them.
How it works
From browsing to lineage.
The catalog is built from what the platform already runs: the schema, the views and the lineage. It is always current.
The schema browser searches by name and filters by tags and notes. A selected view shows its columns with their types.
Notes and developer notes
What your team learns stays with the data.
The reason behind a trimmed key or a null check is written beside the object it concerns. When the person who knew it leaves, the next author and the next AI session read it there.
Notes and tags
Every table and view carries a note and tags, and so does every column in the Vault. They appear wherever the object is listed, and a list can be filtered on them.
Read by everyone
Everyone who signs in reads the notes and tags. AI Chat reads them too when it answers a question about the catalog.
Developer notes for authors
A Vault table or a Mart view also carries a developer note on how to work with it. Mart Managers read and write it, and so does their AI session through the AI Assistant. Report consumers never see it.
Version history
Each change to a developer note is kept as a version. The note shows whether its last change came from an AI session. A note describes structure and rules and never holds a data value.
The catalog you do not have to maintain.
Most catalogs are a second product you buy, point at your sources and scan on a schedule. SchemaVortex's catalog comes built in.
A bolt-on catalog
A catalog deployed beside the lake
Deployed beside the lake, fed by scheduled scans, curated by hand. Lineage is best-effort, and it is out of date the moment something changes.
SchemaVortex
A catalog built into the platform
The catalog, the schema and full lineage are already there, because the platform owns the pipeline end to end. There is nothing to deploy or keep in sync.
Browse, query and trace, live.
A short live demo: browse the catalog, write a query and trace a column to its source.