Immutable history
Versions are added, never overwritten. How far back the history reaches is yours to set.
HighlightsSchema changes
The Vault
Schema changes
do not break reports.
The Vault keeps your history for as long as you choose. When a source changes shape, your reports keep reading the columns they already use.
The mechanism
A history your reports can rely on.
Source systems change, and reports built on them usually break. In the Vault, one edit takes the change in, and no report has to change.
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.
Undo a faulty load
If a source sends bad data, its tables can go back to an earlier point in time, with no downtime.
How it works
The Vault adds columns. It never rewrites them.
When a source changes a column's type or adds a new one, a person updates the Vault table in one edit, and SchemaVortex stores the change as a new, versioned column. The original stays unchanged and stops loading.
Source change
'Address' column's type changed · 'ZipCode' column addedCustomerIdv1Namev1Addressv1 · keptAddress_v2v2 · addedZipCodev2 · added
One table across all its column versions: columns are only added, never altered or removed.
One table exposes every column across all its versions. Existing columns are never altered or removed, so the columns a report reads do not change underneath it. Rows from before a new column existed show it as empty. Most systems let a column change type in place, which breaks the dashboards built on it. In the Vault, a column never changes type.
Latest table
Current state: what everyday reporting reads.
History table
Your history, for audits and point-in-time questions.
Related features
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.