01 — THE ORIGIN
The EU AI Act did not create a new kind of obligation. It created a new kind of question: can you show, system by system, that you knew what your model does and chose to ship it anyway?
2019
Two auditors, one spreadsheet
The first register was built for a bank with nine models and no shared definition of “in scope”. It took eleven weeks.
2022
The register became a product
Three customers asked for the same structure. The control library was extracted and made portable across frameworks.
2024
Evidence replaced attestation
Read-only connectors removed the manual upload step. Programmes stopped depending on somebody remembering to take a screenshot.
2026
A register of record
240 programmes across financial services, health, energy and the public sector now run on the same model.
02 — PRINCIPLES
They are not values on a wall. Each one shows up in how the product is built.
Evidence over assertion
If a claim cannot be traced to a source and a timestamp, it does not belong in the register.
One register
A second system of record is a future argument. Everything maps back to the same control library.
Readable by outsiders
An auditor, a buyer or a board member should navigate the pack without a walkthrough.
Boring by design
Compliance is a routine, not a launch. We optimise for the Tuesday afternoon, not the demo.
THE COMPANY, IN NUMBERS
AS OF Q1 2026
2019
founded in Berlin by two assurance engineers
34
people across eleven countries, remote-first
240
assurance programmes running on Evident
8
frameworks mapped from one control library
03 — HOW WE WORK
01
Every programme has a named engineer
Not a shared inbox. The person who scoped your register is the person you ask when a framework changes.
NAMED · DIRECT
02
We ship the audit trail with the feature
A control that cannot evidence itself is not shipped. This slows releases down and keeps the register honest.
EVIDENCE-FIRST RELEASE
03
Decisions are written, then argued
Design and architecture notes are public inside the company. Disagreement happens in the document, not after the deploy.
WRITTEN · REVIEWED