Kraterion
v 0.1 · private beta Coming soon
app.kraterion.com/krates
v0.1

Your krates

0xfa…122 krates · S3-compatible
krateobjectssizeaccesscreated
assets-prod4,812 objects24.6 GBteam-read-write18 days ago
portfolio.zip1 object2.4 GBprivate6 days ago
assets-prod-20 objects0 Bteam-writejust now
Stored on WalrusSealed by youOwned on Sui
Stored onWalrus, secured withSeal, coordinated onSui.via @mysten/walrus, @mysten/seal, @mysten/sui
Under the hood

Your bytes, end‑to‑end.

A request leaves your machine, gets sealed in our gateway, lands on Walrus, and is owned by you on Sui. Revoke our access anytime — the krate stays.

BrowserDashboard · zkLogin
S3 SDKaws-cli · boto3 · …
GatewayS3-compatible front door
Control planeBucket lifecycle
WorkerRenewals · event indexer
Postgres
Redis
WalrusEncrypted blob storage
SealDecentralised key servers
Sui MoveSharedBlob, owned by you
  1. You
    Browser or S3 SDKYour client
  2. Kraterion
    GatewaySealed in transit
  3. Chain
    SealDecentralised key servers
  4. Chain
    WalrusEncrypted blob storage
  5. Chain
    Sui MoveSharedBlob, owned by you
Upload — sealed, then storedDownload — verified, then unsealedBackground — renewals and chain events

Object storage
you actually own.

We're cooking something up. Same s3:// API, same aws s3 cp commands, same boring billing — one quiet difference underneath. Delete your account tomorrow; your krates are still yours — and only you hold the keys.