How it works

Your code makes one S3 call. Everything after it is run for you, and every step goes on a record you can check.

Admitted → stored → placed → on the record.

1 · Admitted

Each request is tied to a user or agent and held to the limits you set for it. A refused request is recorded like any other. witnessed → Metered access

2 · Stored

The answer comes back from the deployment. Your code never waits on a network or a chain.

3 · Placed

Each file goes where its placement says: kept local, held until it’s final, or sealed to Walrus. HEAD tells you where it is and what comes next. → Placement

4 · On the record

Sealed files get a receipt on Sui that anyone can check, with no account. verifiable Every write, read, delete and refusal is on the ledger: you check your entries against Sui without us, and hand them to whoever needs them. verifiable Deletion ends in a certificate. our statement

What you don’t have to build

Without Permafrost	With it
Auth, rate limits and quotas per user	Built in
A copy job to a network, and a fix for when copies disagree	One answer per file, then its placement
Renewals, a chain writer and a funded wallet	Run for you
An audit trail someone else can check	The ledger, on Sui

You make the S3 call. We run the rest.