# flare-encrypt

> The smallest secrets manager you can fully own: a Cloudflare Worker, one D1 database, and a master key you hold — deployed to your own Cloudflare account with `wrangler deploy`. Secrets are protected by a three-tier AES-256-GCM envelope (per-environment KEK (wrapping key) → per-tenant DEK (data key) → ciphertext) whose mandatory encryption context (AAD) makes a ciphertext copied from one tenant's row into another's fail to decrypt.

flare-encrypt ships an embeddable `@fractalboxdev/flare-encrypt-sdk` crypto library (Web-Crypto only, zero runtime dependencies) plus a deployable Worker + D1 store to graduate to for cross-project sharing, audit, and CLI injection. The store is also a signing oracle: server-side Ed25519 signing keys whose private key is generated in-store, wrapped under the KEK, and never returned over the API — sign-only tokens get signatures, and verifiers need only the public key. The one thing every alternative lacks is the combination of operator-held keys, a portable D1 store, per-tenant crypto isolation, and any-runtime injection.

## Site

- [Overview](https://flare-encrypt.fractalbox.dev/): the BYOC thesis, the three-tier envelope, the four properties, honest positioning, and the layered packages
- [Visualizer](https://flare-encrypt.fractalbox.dev/visualizer): interactive explainers of the envelope, cross-tenant placement integrity, the freshness anchor, and crypto-shred, plus a token-gated live store panel (lists secret names and versions and the audit hash-chain status; never secret values)

## Documentation

- [Documentation overview](https://flare-encrypt.fractalbox.dev/docs): what flare-encrypt is, the four properties, a quickstart, and the layered packages
- [Cryptography](https://flare-encrypt.fractalbox.dev/docs/cryptography): the three-tier envelope, GCM parameters, the frozen canonical AAD serialization, versioning, rotation, crypto-shred, error taxonomy
- [API reference](https://flare-encrypt.fractalbox.dev/docs/api): the `@fractalboxdev/flare-encrypt-sdk` library API and the deployed store HTTP API under `/v1`
- [OpenAPI 3.1 document](https://flare-encrypt.fractalbox.dev/openapi.json): the generated machine-readable contract for the store `/v1` API — every route with its capability, request/response schemas, base64 encodings, and the closed error envelope; verified against the worker's route table in CI
- [Signing keys](https://flare-encrypt.fractalbox.dev/docs/signing): server-side Ed25519 signing keys — the sign oracle API, sign-only and key-pinned tokens, key rotation, and the never-exported private key
- [Data model](https://flare-encrypt.fractalbox.dev/docs/data-model): the D1 schema, the two version axes, the freshness anchor, and the hash-chained audit log
- [Deployment & CLI](https://flare-encrypt.fractalbox.dev/docs/deploy): deploy to your own account, KEK custody, the rotation runbook, break-glass offline decrypt, the `fe` injector, and the `fe key` signing verbs with the offline custody drill
- [Security model](https://flare-encrypt.fractalbox.dev/docs/security): what each layer defends and does not, and the assumed-control boundary

## Source

- [GitHub repository](https://github.com/fractalboxdev/flare-encrypt)
- [npm — @fractalboxdev](https://www.npmjs.com/org/fractalboxdev)