Use cases
Pick a compose path — step-up only through vault-backed chat — then follow its guide.
Use cases
You do not need every package. Pick the path that matches the product, then follow its compose guide.
| Path | What users get | Guide |
|---|---|---|
| A. Step-up only | Sudo / re-auth (password, TOTP) | Step-up only |
| B. Passkey login | Hardened WebAuthn login | Passkey login |
| C. Passkey + step-up | Login + passkey/TOTP/password elevate | Passkey + step-up |
| D. Vault | Blind MEK store + create/unlock UX | Vault composition |
| E. E2E chat | Sealed messaging on the vault identity | Chat composition |
Multi-node shared storage is orthogonal: Multi-instance.
Hard rule
Vault and E2E require the passkey composition. Elevate alone does not. Omit passkeys and you still get password/TOTP step-up.
Compose guides
Step-up only
Password / TOTP sudo — no passkeys, no vault
Passkey login
Hardened WebAuthn sign-in
Passkey + step-up
Shared counter for login and sudo
Vault composition
Blind store + createVaultClient
Chat composition
Vault identity seed → zero-e2e
Multi-instance
Shared stores and deploymentMode
Live demos on this host
Related
- Quick start — production-shaped full sketch
- Packages overview
- API & specs
- Checklist