A bank, a hospital, a training lab, a data controller and a defence programme all need to know what a model did and why. Each calls it something different — validation, audit, diagnosis, erasure, assurance — and each is told the same thing by their current stack: that the answer cannot be recovered after training. It cannot. It has to be produced during it.
So these are not five products. They are five readings of one record, under one licence. What differs between them is not the mechanism but the obligation driving it, the person who signs, and how long the sale takes.
AI Training
Is this run failing, and where?
Regulated Finance
What changed, and can a validator verify it?
Medical AI
Which site caused this, and can we show it?
Data Obligation
What data is in here, and can I remove it?
Defense & Safety-Critical
What did the system do to itself in the field?
ORMAS is one licence. Terms are agreed per institution and written into the contract — there is no price list.
Which of the five is yours?
Every engagement starts with one specific problem — a run that died, an audit that asked a question you could not answer, a dataset you cannot vouch for.
We reply within a few days. Every message is read by a person.
Start a conversation
Tell us what you are trying to see inside your models, and we will say plainly whether this is the right thing for it.
Useful to bring
- What you train and what you need to prove about it
- Anything you have already tried