Governed by default
The five gates are live from the moment your data is discovered.
HighlightsGovernance built in,
Governance
Governance built in,
not bolted on.
Every column passes the same five gates before anyone sees it. Approval and masking happen as the data flows, so what your team queries is already governed.
The foundation
Who can see what, answered before anyone asks.
Most platforms add governance afterwards, as a layer someone has to maintain. SchemaVortex starts governed and stays that way.
No second copy to keep in sync
Masking is applied as the query runs: whoever queries gets the view masked for them.
Separation of duties
Three stewards hold distinct keys. Nobody outside these three roles ever sees ungoverned data.
Every decision audited
Each approval, classification and mask change is recorded: who, what and when.
How it works
Five gates. Three stewards. One masked table.
Every column travels left to right through the same pipeline. Each gate narrows what a given person can see; the stewards below hold the keys.
Origin source data Consumer Power BI, Excel, any SQL client
1
Gate 1
Vault Approval
Nothing enters the Vault until a steward approves the table and its columns.
2
Gate 2
Production Data Mask
Operational secrets and internal financials stay hidden, even from the BI developers.
3
Gate 3
Compliance Mask
PCI, PHI and PII fields, controlled one column at a time.
4
Gate 4
Sensitivity Mask
Internal, Confidential and Restricted, each visible only with the right clearance.
5
Gate 5
Delivery Mask
Anything still sensitive stays with the stewards who own the lake.
Governed by
Data Warden
Sensitivity Governor
Vault Manager
Because the platform applies the masks at query time, there's no sanitized copy of production to build and keep in sync. The masked table is the table.
See the five gates in action.
A short live demo: watch a column pass the five gates, then query it masked.