Built so we can't hold your data.
Stratum analyzes the structure and logic of your Power BI models — never the rows inside them. The boundary isn't a promise layered on top of the product. It's what the product is made of.
Two inputs describe your model. Neither contains your data.
Stratum needs to understand how your measures are calculated and how your model is shaped — not what's in any row. Two metadata formats give it exactly that, and nothing more.
The model's shape and statistics
Exported from your model, a VPAX describes structure and VertiPaq statistics — the aggregate profile of the model, not its contents.
- Cardinality, memory footprint, encoding, compression
- Tables, columns, relationships, measure definitions
- Aggregate counts — never the underlying values
The logical source of truth
A data-free project representation of the model. It carries the calculation logic Stratum reasons about — the DAX itself — with no data payload attached.
- Measure and column DAX expressions
- Model relationships and dependency structure
- Display folders, formatting, metadata — no rows
The boundary is enforced by how it's built — not by a rule someone has to remember.
Policies can be misconfigured. Architecture can't be talked out of. Four design decisions make the data-safe boundary structural.
A read-allowlist that hard-refuses
Only known metadata formats are accepted. Point it at a data-bearing file and it refuses to read it — the safe path is the only path.
An offline, data-free working copy
Analysis runs against a local clone of the model's metadata. No network round-trip to your tenant is ever made.
Originals left byte-for-byte untouched
Your source files are never modified. Any remediation is emitted as a separate, corrected copy you review before adopting.
The boundary is asserted by tests
The data-safety guarantees aren't aspirational. They're pinned by an automated test suite that fails the build if the boundary is crossed.
The engagement that survives procurement.
Most governance tooling asks for access first and reassures you second. Stratum inverts that: the assessment happens without any access at all.
No tenant onboarding
Nothing is connected to your Power BI Service or workspace.
No capacity required
No Premium P1, no Fabric F64 — the boundary needs none of it.
Nothing to allowlist
No inbound connection, no gateway, no service principal to approve.
Runs where you choose
Analysis happens locally, on your terms, inside your environment.
| Data type | Read? | Stored? | Transmitted? |
|---|---|---|---|
| Row-level / source data | Never | Never | Never |
| VertiPaq statistics (VPAX) | Yes | Only within the run | No |
| Measure / model logic (PBIP) | Yes | Only within the run | Semantic stage only * |
| Live tenant connection | Never | Never | Never |
* The optional semantic-analysis stage sends measure logic — never data — to the language model that performs equivalence detection. Deterministic checks and reporting run entirely locally.
Governance you can hand to security before you hand it to the board.
Request the data-handling summary, or start with a pilot assessment that needs no access to your environment at all.