Overview

Storage for apps that hold other people’s data. S3 in, your users’ existing sign-in, a stated home and span for every file, and receipts on Sui anyone can check.

Features

Feature	In one line
S3 and identity	The S3 API. Your users’ sign-in is the credential; each user is a tenant.
Shared spaces	A bucket one user owns and invites others into, with an optional age limit.
Encryption choices	Per bucket or file: our managed keys (default), your own key service, or your own encryption.
Data residency	Data stays in your region, archived there too if you want. Only fingerprints go public.
Placement	Per file: the deployment’s disk, held for a window, or Walrus.
Retention	Every object’s span recorded, watched and renewed.
Receipts	Fingerprint and version history on Sui.
Custody and deletion	Hold material for a user; delete it by destroying its key, with a certificate.
Leaving	Receipts on Sui point to your data on Walrus, findable without us.
Delegated access	A scoped, revocable grant for an agent or session key.
Agent space	Shared agent work with a referee and a recorded, fixed end.
Warranties	Your signed claims about an exact set of files, witnessed and kept current.
Public ledger	Every write, read, delete and refusal, rooted on Sui.
Metered access	Auth, rate limits and counting per request; per-tenant write and read limits; optional billed reads.
Deployment page	Usage, balance and holdings, for your team and each user.

Uploads and reads feel fast. That is the whole performance claim.

What it is not

• Not a database, model or memory system. It sits underneath them.
• Not a shared public service. Each team gets a dedicated deployment.
• Not storage without end. Bytes are kept for their stated span, renewed while the deployment runs. The receipt resolves on Sui regardless.
• Not user-facing. Users see outcomes: their data is theirs, deletions come with a certificate, records are checkable.