Your data.
Your logs.
Your exit.
Files, run records, and memory are encrypted before they leave you and stored in a project you own. We can't read them, we can't alter them, and you can revoke our access in one step.
Same files. Different perimeter.
They hold the keys.
- AKIA7C4D8E1C…3Fread-onlyactive
- AKIA92AC6712…A1read-writeactive
- AKIA1A8B4C5D…99adminactive
Manual process · SLA 2-5 business days
- Keys live inside the provider boundary.
- Revoke is a support ticket, not a property.
- Exit means copying everything out — at $0.09/GB egress.
You hold the keys.
- kr_test_3f4d8e1c…a2read-onlyactive · revoke
- kr_test_92ac6712b1…7cread-writeactive · revoke
- kr_share_test_1a8b4c…99agentactive · revoke
Keys stop being issued immediately — by structure, not policy.
- Keys live with you. Plaintext never crosses the wire.
- Revoke is a policy property — enforced, not promised.
- Exit through any S3 client — at ~9× lower egress than AWS.
What ownership
actually means here.
You can leave anytime.
Files are stored as plain bytes addressed by a stable ID. Any S3-compatible client can pull them. You don't need our tools to leave us.
Sealed before it leaves you.
Files are encrypted on your device before they ever reach the platform. The platform sees only encrypted bytes.
Revocable access — enforced, not promised.
When you remove access, the decryption keys stop being issued. The ciphertext sitting on disk becomes unreadable to the revoked party.
A verifiable audit log.
Every artifact — upload, indexing run, agent answer, citation — is bound to a uniquely-IDed, version-tracked record. Anyone can independently verify the history.
Plaintext never leaves
the laptop.
Encrypted before it leaves you.
Encryption happens on your device. We store only what we can't read.
- 1Data keyGenerated on your device — encrypts the file
- 2Key wrapWraps the data key so only policy can release it
- 3PolicyYour access policy gates the key
Sealing is handled by Seal; the access policy that releases the keys is enforced on Sui — so revoking access is a property of the system, not a support request.
Policy is the gate. Not a promise.
When you revoke access, the system stops issuing the keys needed to decrypt. Existing ciphertext doesn't have to be deleted to be unreadable to a revoked party.
Who can decrypt; under what conditions.
Independent servers check the policy on every request.
Authorized clients receive key shares; unauthorized clients receive nothing.
Remove access — key servers stop issuing shares. Existing ciphertext stays unreadable.
A tamper-evident history.
Every artifact has a uniquely-IDed, version-tracked record. The history is independently verifiable.
Plain English.
TLS 1.3 with modern cipher suites.
Server-side access logs retained for 90 days.
In progress — on the roadmap.
Not currently suitable for regulated personal data (HIPAA / PHI).
Building toward EU AI Act, GDPR, or ISO 42001? See how Kraterion fits AI governance.
Storage that earns trust
by structure, not promise.
Sealed before upload. Revocable by policy. Verifiable end-to-end.