Enforces defensibility
The Clean Room
Your outputs will be subpoenaed, investigated, or cited in enforcement actions. Every input is cryptographically signed at the point of capture. Every decision carries a full chain of custody. The runtime is hardware-attested. The audit trail is non-repudiable. If you need to reconstruct exactly what happened and prove it in court, this is the environment.
Without this
Without the Clean Room, you can assert the system works — you can't prove it. A regulator or court will notice the difference. The liability is structural, not accidental.
How it works
Every step in the chain — question, data lookup, model inference, answer — is cryptographically signed and hash-linked. The execution environment is sealed. Bypass isn't a policy decision; it's structurally impossible. The audit trail isn't a log — it's a proof.
Failure mode: Fails hard — Uncertainty is not allowed. Authority is mandatory. Bypass is structurally impossible. Human discretion is removed from runtime.
Who operates it, who receives it
Operator
The Auditor
Operating under inspection, where mathematical proof matters more than intent.
Consumer
The Regulator
Doesn’t consume the output at all—they examine the chain of custody.
When to choose this
Deploy for
- Life-safety systems
- Medical decision support
- Defense and critical infrastructure
- Financial systems with legal liability
Do not deploy for
- Internal tooling
- Exploratory analysis
- Drafting or summarization
Where it runs
Deployment
Appliance / Air-gapped
On-premise / sovereign
Support
Dedicated engineering + 24/7
Execution
Attested runtime, measured boot, verified artifacts
High regulatory exposure
What it costs
Starting at $250,000 / year
Deploy the Clean Room →For regulated industries — healthcare, finance, legal, defense, insurance — where the audit trail isn’t a feature, it’s a legal requirement. The Clean Room is a physical or virtual appliance where Ontic supplies the containment, you supply the systems of record, and the system proves structurally that no unauthorized claim could have been produced.
- Clean Room appliance (physical or virtual, your hardware)
- Immutable, hash-chained audit provenance — every decision cryptographically chained to the previous one
- Air-gap capability — full stack runs with no external network dependency
- TPM-sealed secrets management — API keys, oracle credentials, and model configuration never exist in application memory
- Attested runtime with measured boot and verified artifacts
- Mechanical gate — opaque boundary the model cannot see or reason around
- End-to-end audit envelope: input state, matched rule, oracle evidence, gate decision, timestamp, and cryptographic hash
- Enterprise SLA for oracle registry updates and security patches
- Dedicated account team
How the tools work here
Every environment uses the same platform tools — the difference is how aggressively each tool enforces.