Research · Documentation

Provenance and EU AI Act conformity


Every deliverable carries who did what, under which clearance, on sovereign infrastructure — the paperwork regulated deployments need.

Per-item provenance

Every episode and annotation in a delivered dataset carries its provenance: who produced it, under which verified credentials and clearances, when, and under which quality checks. Provenance is captured as the work happens, not reconstructed afterwards.

Conformity fields built in

Deliverables carry the fields that EU AI Act deployments need from their training-data providers — so a customer's conformity assessment can cite its data supply chain rather than apologise for it.

Sovereign by construction

Identity, data, inference and voice run on EU infrastructure with no third-country vendor in the data path. For regulated European buyers this is not a hosting detail — it is the product.

← Research hub