The provenance engine underneath everything.
Every record ingested by Demia passes through Mavric's normalization and attestation pipeline before it can be stored, displayed, or shared, so integrity is established before data reaches any dashboard or data room.
Downstream outputs are only as defensible as the pipeline.
Standard BI and reporting tools display what they receive, with no record of source integrity and no way to defend a specific figure under adversarial scrutiny. Mavric is the pipeline that makes the rest of the platform defensible: every record is normalized and attested before it surfaces anywhere.
Normalization without losing provenance.
Operational data arrives in inconsistent formats: sensor telemetry, PDFs, spreadsheets, API payloads. Mavric normalizes to a canonical schema while preserving a cryptographic reference to the raw source, so both the normalized record and the original are part of the evidence chain.
Timestamps anchored to external roots.
Mavric anchors record timestamps against trusted external time sources, including RFC 3161 compliant timestamp authorities and distributed ledger roots of trust, making timestamp manipulation independently detectable without relying on Demia's own clock.
Lineage as a first-class object.
Every transformation Mavric applies is recorded in a queryable lineage graph. Auditors can traverse backward from any derived figure to the raw records that produced it, with cryptographic integrity checks at every step.
Does Mavric train on our data?
No. Mavric processes and attests your records. It does not train models on customer data, and your data is never used to improve models for other customers.
Where does the model run?
Mavric runs in your deployment environment (cloud, on-prem, air-gapped, or edge), not as a shared multi-tenant service. Your data doesn't leave your governed environment to be processed.
What happens if we lose connectivity?
Mavric's edge components keep working offline. Records are normalized and attested locally, then synced to the broader pipeline once a connection is available.
Can Mavric's output be used as legal or regulatory evidence?
It is designed for that. Every record Mavric processes carries a cryptographic attestation and lineage trail built to evidentiary standards. Acceptance is ultimately the receiving party's decision.
Who can see Mavric's output?
Access follows the same zero-trust policy as the rest of the platform: scoped per user and per record, with every access logged.