Skip to content
SCHEMAVORTEX
Platform

Bring Your Own Data

Your spreadsheets, approved and masked like your databases.

Budgets, targets, price lists and mapping tables often live outside any database. Import them from Excel, CSV or Parquet, and they get the same approval, masks and history as everything else in the lakehouse.

In short

The data outside your databases counts too.

A report often needs a figure that nobody keeps in a database. Once the file is in the lakehouse, it sits next to the rest of your data, under the same rules.

Excel, CSV or Parquet

Your team picks a file, a sheet or a range of cells, and imports it. There is no connector to build.

Column types proposed

SchemaVortex reads the file and proposes a type for every column. Nothing is saved until someone checks them.

Governed from the first row

An imported table waits for a Data Warden's approval, then gets the same masks as any other table.

New file, same table

When the file changes, it is imported again into the same table. A versioned Vault table keeps what the earlier files said, as far back as your history reaches.

How it works

From a file to an approved, masked table in three steps.

The import wizard reads the file, proposes a table, and hands it to the same pipeline your databases use.

sales_targets_2026.xlsx
  1. 1Read the file
  2. 2Check the columns
  3. 3Import
ColumnType
Regionnvarchar(40)
Monthdate
Targetdecimal(18,2)
Notesleft out
  1. Waits for a Data Warden's approval
  2. Kept in the Vault, with its history
  3. Queried from Power BI, Excel or any SQL client

The uploaded file itself is not kept once its rows are in the lakehouse. Who imported which file, and when, stays on record.

Producer SDK

Anything with rows can send them in.

For a system without a built-in connector, a small .NET library pushes its data straight into the lakehouse, from an API, a queue or an export of your own.

Replace, append or update

Send the whole table each time, add new rows, or update rows by their key.

Runs on your side

The SDK runs in your own infrastructure and signs in with a key that belongs to a single source.

Then the same rules

Data sent this way is approved, masked and kept in the Vault like every other source.

See a spreadsheet become an approved, masked table.

A short live demo: we import a file, approve it, and query it from Power BI.