Store user data your own servers can’t read.

A zero-knowledge, post-quantum storage API. Your client encrypts with open-source @shieldfive/crypto; we store ciphertext and wrapped keys, never your keys.

Free tier: 100 MB per project · no card · EU-hosted

// in your client
import { xchachaV1 } from '@shieldfive/crypto'

const { blob } = await xchachaV1.encryptBytes(data, { contentKey })
await fetch('/api/v1/blobs', { method: 'POST', body })

// later, on the user’s device
const got = await fetch('/api/v1/blobs/' + id)
const plain = await xchachaV1.decryptToBytes({ blob, contentKey })

Four calls, one rule: plaintext never leaves the device

Step 1

Encrypt on the device

Your app seals the data before anything is sent.

Step 2

Store the ciphertext

We keep ciphertext and wrapped keys per project.

Step 3

Fetch and decrypt

Only the user’s device can open it.

What the API holds, and what it never sees

Stored with us
  • Ciphertext of each object
  • Wrapped keys, by project
  • Hashed API keys, shown to you once
Never sent to us
  • Plaintext
  • Unwrapped keys
  • Your users’ passwords

A breach of our storage exposes only ciphertext. A lost key means nobody can decrypt, including us: key custody is yours.

Questions

Cho García, founder of ShieldFive

Ask Cho

I answer every question myself, by email.

0 / 1000

Your address is used to reply, nothing else.

Does the API ever see plaintext?

No. The encryption happens in your client with @shieldfive/crypto, before the ciphertext is sent. The API receives and stores ciphertext + wrapped keys only — it never receives plaintext or unwrapped keys, and never decrypts.

What are the limits?

The MVP is a free developer tier with a hard byte quota (100 MB stored per project), EU-hosted, hashed API keys shown once. Usage-based billing for higher limits is on the roadmap.

What if a key is lost?

Because no key ever reaches us and nothing is stored in plaintext, a lost key means the ciphertext can’t be decrypted by anyone — including us. Key custody is the developer’s responsibility; that’s what makes it zero-knowledge.

Is there a separate SDK to install?

Today the “SDK” is the open-source @shieldfive/crypto library plus HTTP calls: POST /api/v1/blobs, GET /api/v1/blobs/:id and DELETE /api/v1/blobs/:id, each authed with your Bearer API key. A dedicated convenience SDK is planned but not required to build.

Your users’ data. Unreadable to everyone else.

Free tier · no card