storage-p vs Bitwarden: zero-knowledge & self-hosted

At a glance

1. Hosting: storage-p runs self-hosted on your own server; Bitwarden is a managed cloud service.
2. Encryption: storage-p is zero-knowledge — your key is derived in the browser with Argon2id and the server only ever stores XChaCha20-Poly1305 ciphertext.
3. Beyond passwords: storage-p also stores SSH/TLS keys, API keys and TOTP, and generates Ed25519 SSH keys and self-signed certificates client-side.
4. Integrations: storage-p issues scoped API tokens whose every read can require your in-app or Telegram confirmation.
5. Both Bitwarden and storage-p can be self-hosted; storage-p keeps the database encrypted at rest with SQLCipher on top of client-side encryption.
6. Both are open about their internals: Bitwarden is open-source, and storage-p is self-hostable with a transparent, documented crypto design.

The core difference

Your vault lives on Bitwarden's servers under their control; with storage-p you hold the keys and can run it on your own infrastructure, so a vendor breach, outage or policy change never exposes your plaintext.

Where storage-p stands out

The server never sees your master password or plaintext — encryption, decryption, key generation and the security audit all run on your device. You can store and generate SSH/TLS material, share via burn-after-read links or end-to-end sealed-box, and grant integrations narrow, auditable access instead of all-or-nothing exports.

When Bitwarden may fit better

If you want a fully managed service with vendor support and the most polished browser and mobile autofill, Bitwarden may suit you better — you trade self-custody for convenience.

Switching from Bitwarden

Moving is straightforward: Bitwarden can export a Bitwarden-format JSON, which storage-p imports directly. See the step-by-step migration guide linked below.