Platform
Platform · Mavric

The provenance engine underneath everything.

Every record that Demia ingests passes through Mavric's normalization and attestation pipeline before Demia stores, displays or shares it. Mavric establishes integrity before data reaches any dashboard or data room.

Close-up of a processor chip on a circuit board
CapabilitiesMulti-source ingestionSchema normalizationCryptographic attestationTimestamp anchoringLineage graph construction

Downstream outputs are only as defensible as the pipeline.

Standard BI and reporting tools display what they receive. They keep no record of source integrity and give no way to defend a specific figure under adversarial scrutiny. Mavric is the pipeline that makes the rest of the platform defensible. Mavric normalizes and attests every record before the record surfaces anywhere.

Normalization without losing provenance.

Operational data arrives in inconsistent formats: sensor telemetry, PDFs, spreadsheets, API payloads. Mavric normalizes the data to a canonical schema. Mavric also keeps a cryptographic reference to the raw source. Both the normalized record and the original are then part of the evidence chain.

Timestamps anchored to external roots.

Mavric anchors record timestamps against trusted external time sources. These sources include RFC 3161 compliant timestamp authorities and distributed ledger roots of trust. An independent party can then detect timestamp manipulation without reliance on Demia's own clock.

Lineage as a first-class object.

Mavric records every transformation it applies 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.

Common questions

Does Mavric train on our data?

No. Mavric processes and attests your records. It does not train models on customer data. Mavric never uses your data 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 does not leave your governed environment for processing.

What happens if we lose connectivity?

Mavric's edge components continue to work offline. The edge components normalize and attest records locally. They sync the records to the broader pipeline when a connection is available.

Can Mavric's output be used as legal or regulatory evidence?

Demia designed Mavric output for that use. Every record Mavric processes carries a cryptographic attestation and lineage trail built to evidentiary standards. The receiving party makes the final decision on acceptance.

Who can see Mavric's output?

Access follows the same zero-trust policy as the rest of the platform. The policy scopes access per user and per record. The platform logs every access.

Platform flow
Click any product to explore it. The highlight shows where you are.
Capture
At the source
Process & Route
Normalize, attest, govern
Certify & Distribute
Compliance outputs
Current product
Click to explore