Data layer
Traditional platforms copy your data into a vendor’s vault. Meridian’s data layer builds the structure inside your own environment instead: its own databases, fed by connectors to your databases, streams and enterprise systems.
- Role
- Connect
- Primary user
- IT & data engineers
- Core value
- Structures your sources into one ontology inside your own environment — with history and provenance.
Every integration ends up in someone else’s vault.
Conventional platforms move your data into a central vault — often in the vendor’s cloud, in a format only they can read. The result: costly pipelines, stale copies and a data model that is no longer yours.
A data layer inside your environment
Meridian runs its own databases between your source systems and the operational picture — on your servers or in your sovereign cloud, under your control.
One ontology
People, vehicles, sites, organisations and events, and the links between them, in one model you define — every change versioned: who, what, when and why.
Read-only connectors
Connectors read from your databases, streams and registries without writing to them. Operational networks (OT/SCADA) are only read through your existing DMZ or data diode.
Open and exportable
A documented model with open interfaces: applications, analysts and local AI — through the open Model Context Protocol (MCP) — use the same layer, and you can always take it with you.
Screenshots of Meridian. Case data is fictitious demo data; ship and flight positions and grid figures come from live public sources. Map data © OpenStreetMap contributors.
The middle layer of three.
The data layer sits between your sources and the screens on top. Your source systems stay the system of record; the data layer keeps what the operational picture needs — with provenance per field and a history of every change, which is what makes replay possible.
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
