Provable third-party audits · concept

Auditor in a Box.Answers, not access.

A sealed, hardware-attested server that sits inside the lab. The lab loads its records, a verifier asks agreed questions, and only signed yes-or-no answers come out. The evidence never leaves the box.

How it works → Protections

How it works

Questions go in. Yes or no comes out.

The lab supplies its records once. The verifier's questions run through the box, and each one comes back as a single signed answer, aggregated over everything inside.

fig. 1 — one auditanswers illustrative

01 · Agree

Both sides fix the rules

The questions, the programs that answer them and what may be released are signed off before any data moves.

02 · Load

The lab controls what goes in and out

The lab chooses which records enter the box and which answers leave it. Nothing is pulled from its systems.

03 · Answer

Answers are cryptographically verifiable

Every answer is signed by the box and bound to the agreed question and program. Anyone can check it; any edit breaks the signature.

Inside the box

Two layers of protection.

Physical protection keeps anyone from reaching the data. Cryptography proves that nothing was changed.

Physical

Keeps hands off the data

On-board cameraFilms anyone who touches or opens the box

Sealed enclosureLocked steel case with seals on every seam

Tamper sensorsAny breach wipes the keys instantly

Air-gap readyRuns with no network connection at all

Cryptographic

Proves nothing was changed

Encrypted computeTrusted execution keeps data encrypted even in memory

Hardware keysSigning keys never leave a secure chip

AttestationProves exactly which code is running

Signed audit logAny edit to a result breaks the signature