Cryptographic proof for digital artifacts.
No blockchain. No ledgers. WTF?
Proof should be a property of creation, not verification.
How it works
Three steps, one proof. Your file never leaves your device.
Drop your artifact
Drag any file into ProofStudio. It's hashed locally in your browser — nothing is uploaded.
Commit
The hash is sent to a trusted execution environment where it's bound to a nonce, counter, and timestamp.
Receive proof
You get back a portable proof object — a signed JSON that demonstrates this artifact existed in this exact form at this moment.
Portable, verifiable proof
Every proof is a self-contained JSON object. It includes a content hash, commit metadata, a cryptographic signature, and an optional hardware attestation report. Anyone can verify it independently.
{
"version": "occ/1",
"artifact": {
"hashAlg": "sha256",
"digestB64": "u4eMAiu6Qg..."
},
"commit": {
"nonceB64": "gTME79qH3f...",
"counter": "277",
"time": 1741496392841,
"epochId": "a1b2c3d4..."
},
"signer": {
"publicKeyB64": "MFkwEwYH...",
"signatureB64": "MEUCIQD..."
},
"environment": {
"enforcement": "measured-tee",
"attestation": {
"format": "aws-nitro"
}
}
}Prove anything
Any file or computation result that needs verifiable proof of existence and integrity.
AI Outputs
Prove model responses, generated images, and predictions came from a specific boundary at a specific time.
Software Builds
Prove a build artifact was produced by a specific CI/CD pipeline inside a measured environment.
Media & Journalism
Prove a photo or document existed in its current form at a specific moment — before edits, before distribution.
Scientific Data
Prove sensor readings and instrument output existed at capture time with sequence integrity.
Compliance & Audit
Produce tamper-evident records where any modification breaks the proof chain.
Agent-to-Agent
Pass proofs between systems so each can verify data integrity without trusting the transport.
OCC — Origin Controlled Computing
ProofStudio is built on the OCC protocol — a cryptographic proof system where proof is produced by the commit event itself. If the proof exists, the commit happened. If it doesn't, it didn't.
Read the protocol documentation →Try it now
Drop a file, get a proof. Runs in your browser, verifiable by anyone.