Immutable history
Versions are added, never overwritten. How far back the history reaches is yours to set.
HighlightsSchema changes
The Vault
Schema changes
don't break reports.
The Vault keeps your history for as long as you choose to retain it, so a source can change shape without taking your reports down with it.
The mechanism
Sources change shape. Your dashboards keep working.
Source systems inevitably change, which typically breaks downstream reports. The Vault is designed to absorb these changes automatically.
Reports survive source changes
When a source adds a column or changes a type, the columns your reports already read stay exactly as they were.
Your own computed columns
Add computed columns right in the Vault to derive business-ready values, with the source data untouched.
Roll back a faulty extraction
Restore the lake to any moment you still retain, and the history stays intact.
How it works
The Vault adds columns. It never rewrites them.
When a source changes a column's type or adds a new one, SchemaVortex stores it as a new, versioned column. The original lives on unchanged; it just stops loading.
Source change
'Address' column's type changed · 'ZipCode' column addedCustomerIdv1Namev1Addressv1 · keptAddress_v2v2 · addedZipCodev2 · added
One table, every version: columns are only added, never altered or removed.
One table exposes every column across every version. Existing columns are never altered or removed, so the columns a report reads don't change underneath it; rows from before a new column existed show it as empty. Most systems let a column change type in place, quietly breaking the dashboards downstream — the Vault rules that out.
Latest table
Current state: what everyday reporting reads.
History table
Your history, for audits and for looking back in time.
See a schema change break nothing.
A short live demo: we change a source's schema in front of you, and the report keeps reading the same columns.