Kraterion runs AI agents on storage you own, and records every run

Cloud storage asks you to trust the provider. Cancel and the files can go. Get locked out and they are gone. The provider can read what it stores, and leaving means paying to copy everything out.

AI agents add a second layer of trust. They reason over that data, the same input can give a different output, and the trace usually lives in a vendor's database. You cannot prove what an agent read or how a past answer was made.

The build had its own limits. We had about 6.5 weeks from kickoff to the Sui Overflow 2026 deadline. Walrus prices storage per object, up front, which does not match the per-gigabyte bill developers expect. And in July, on the way to mainnet, Sui switched off the public interface our chain layer used, so we moved it to the newer one.

We kept everything a developer touches familiar: the S3 API, Google sign-in and an OpenAI-compatible endpoint. The chain sits only where promises used to live. Users never handle crypto tokens; the platform pays storage and transaction fees from a shared reserve.

Ownership is enforced by cryptography, not by a privacy policy. Each file is encrypted before it is stored, and decryption keys are only released while your on-chain bucket allows it. Revoking access is one transaction, after which the platform cannot read your files.

To make decentralized storage bill like normal storage, we pooled it: each project gets one storage pool, uploads use capacity and deletes free it. Every agent run records its inputs, retrievals, tool calls and output, stored on Walrus and anchored on Sui. We are open about limits too: the on-chain package is marked unaudited, and roadmap items say coming soon.