Skip to content
Permafrost Docs

Dedicated deployments

No shared instance. Each team gets its own deployment at its own address. We run upgrades, renewals, backups and recovery.

What a deployment serves

Section titled “What a deployment serves”

How it’s upgraded

Section titled “How it’s upgraded”

One deployment at a time, tested before it reaches yours, with a way back for every release.

How it recovers

Section titled “How it recovers”
  • No acknowledged write is lost.
  • A failure costs minutes, with stored data and in-progress uploads intact. Requests in flight get an error; retry them.
  • Backed up, keys included.

A short interruption, not a seamless switch. No uptime figure yet.

If a request fails during recovery

Section titled “If a request fails during recovery”

Recovery takes a few minutes. Expect connection errors, timeouts or 5xx.

  • Retry connection errors, timeouts, 5xx, 408 and 429 with exponential backoff and jitter, for a few minutes before surfacing an error. Raise your S3 SDK’s retry setting (max_attempts / maxAttempts) rather than writing a loop.
  • Don’t retry other 4xx. They won’t change.
  • Retrying is safe for a PUT of the same bytes to the same key, and for GET, HEAD and ListObjects.
  • Multipart uploads survive. ListParts with the upload id, upload the missing parts, complete. On 404 NoSuchUpload, start over.

Getting one

Section titled “Getting one”

Write to hello@permafrost.live. After a short call about what you store and who your users are:

  1. We provision your deployment at its own address. A live walk-through is on request.
  2. You connect your identity system, or try an invite key first. → Connect your app
  3. You run the Quickstart against your endpoint.

Today: Sui testnet and Walrus testnet. Billing is a prepaid USDC balance, shown on the deployment page. Your own key service on request. Billed reads and a daily read cap are set by contract; both off by default.

At contract end, we delete your data on request and send a report, plus a certificate per custody object our statement. Walrus data that can’t be removed early is listed with its storage end date. Export first: take your data out.

Known and deliberate

Section titled “Known and deliberate”
  • Bucket names are visible across tenants of a deployment. Contents aren’t.
  • Auth: bearer token or S3 access key (SigV4, SigV4 pre-signed URLs; path-style, or virtual-hosted where enabled). No SigV2 or session tokens. → S3 compatibility

Permafrost runs on Sui testnet and Walrus testnet. Everything here describes a shipped testnet instance, not a production service.