S3 you
actually own.
Same SDKs you already use — boto3, aws-cli, rclone. This is the foundation the runtime sits on: your files, knowledge bases, run records, and memory all live here, sealed before upload and recorded against your account. Not a customer promise. A property of the system.
- photo-final-v3.jpg2.1 MBSealed
- dataset-2026-05.parquet118 MBSealed
- report-q1.pdf482 KBSealed
- logo-v2.svg24 KBSealed
Storage that's yours,
in and out.
Most storage products promise ownership in a marketing line. Kraterion makes it a property of the system — enforced by structure, not by trust.
You own the bytes.
Every object is recorded against your account, not ours. Cancel the service tomorrow — the files don't disappear. Keep them funded directly, or pull them out via any S3 client. We're a service, not a custodian.
Portable, both ways.
No proprietary import, no proprietary export. Point any S3 client in; pull every byte out at ~9× lower egress than AWS. Leaving costs nothing beyond standard egress — no exit tax, no migration window.
Every object is also encrypted before upload, with access you can revoke and a tamper-evident record of every action. See the security model.
Every action leaves a record.
Storage activity, access changes, knowledge runs, agent invocations — they all write to the same append-only log. Each row has a uniquely-IDed digest you can verify independently, without trusting us.
- 14:02:11UPLOADphoto-final-v3.jpgby you@acme-co.com · 2.1 MB · sealed9c4a8b21f0e7c2…
- 13:58:22ISSUEshare token · kr_share_test_92ac…scope support-docs · origin docs.acme-co.com4f1ab3a0e7c2f9…
- 13:55:07REVOKEshare token · kr_share_test_1a8b…access policy updated · enforced at t+0fa0012a4e7c2f1…
Same S3 surface.
Different spine.
Your S3 client hits a single gateway endpoint. Behind it, three concerns run in parallel — the encryption envelope, the storage layer, and the ownership + audit record — without you wiring any of them.
Files stay yours.
Cancel anytime — your bytes don't move. Any S3 client can pull them.
Keys stay yours.
Revoke and decryption stops. Enforced by structure, not policy.
Every artifact has a receipt.
Tamper-evident manifest digests you can verify against the chain.
Encrypted with Seal · stored on Walrus · owned on Sui — the three open primitives behind the single endpoint.
Same SDKs you already use.
Just change the endpoint.
Point a client at us.
One environment variable. The S3 commands you already write — PUT, GET, LIST, presigned URLs — work without modification.
import boto3
s3 = boto3.client(
"s3",
endpoint_url="https://s3.kraterion.com",
aws_access_key_id="...",
aws_secret_access_key="...",
)
s3.upload_file("photo.jpg", "my-bucket", "photo.jpg")No proprietary import.
No proprietary export.
Repoint your client and write new objects against the new endpoint, or run a one-shot sync from your old bucket. Leaving works exactly the same way — reverse the endpoint flags, pull every byte out via standard tools. No exit tax, no migration window.
rclone sync s3://old-bucket kraterion:my-bucket --progressPoint a client at us.
See for yourself.
One environment variable changes. Everything else stays the same.