Trust & governance
The governance foundation for customer control: purpose-bound access, traceable query logs and customer-held keys.
- Role
- Foundation
- Primary user
- CISOs, legal & compliance
- Core value
- Purpose-bound access, traceable query logs and customer-held keys — designed around your governance requirements.
Compliance on paper is not compliance.
Policies define who may see what, and why. Most platforms cannot prove it afterwards. When a regulator, a court or a data-protection authority asks, the answer must come from the system — not from a spreadsheet.
Customer-controlled encryption keys
You hold the keys (CCEK), not the vendor. Data can only be decrypted inside your own perimeter.
Traceable query logging
Every query recorded locally in a tamper-evident log — who asked what, on which legal basis — designed for the safeguards the German Federal Constitutional Court set for automated data analysis.
Access by role and purpose
Each user sees only what their role and the purpose of their task allow — on the map, in cases and in AI answers alike.
Evidence for NIS2 & DORA
Incident timelines, supplier inventories and audit evidence drawn from the platform’s own records — to support your reporting.
Zero trust, everywhere.
Around every part of Meridian: identity and authorisation at every layer, keys under your control, an append-only record of what the platform does — and no telemetry or phone-home.
Data architecture: your own data layerEvery part of Meridian is designed on the same sovereign architecture: European engineering, customer-controlled keys and no telemetry — for your own cloud, on-premise or air-gapped environment. Deployment is scoped to your operational and applicable legal requirements.
Sovereignty
