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

Both storage-p and Firefox keep secrets safe, but they take different routes. storage-p is a self-hosted, zero-knowledge vault you operate yourself; Firefox is a browser's built-in password feature. Here is a factual side-by-side.

At a glance

Hosting: storage-p runs self-hosted on your own server; Firefox is a local, device-based app.
Encryption: storage-p is zero-knowledge — your key is derived in the browser with Argon2id and the server only ever stores XChaCha20-Poly1305 ciphertext.
Beyond passwords: storage-p also stores SSH/TLS keys, API keys and TOTP, and generates Ed25519 SSH keys and self-signed certificates client-side.
Integrations: storage-p issues scoped API tokens whose every read can require your in-app or Telegram confirmation.
Firefox does not offer a self-hosted server, so your data lives with the vendor; storage-p you run and own end to end.
Both are open about their internals: Firefox is open-source, and storage-p is self-hostable with a transparent, documented crypto design.

The core difference

Firefox is handy for filling website logins, but it is tied to the browser and stores little beyond passwords. storage-p is a dedicated, portable vault for passwords, SSH/TLS keys, API keys and TOTP, synced across devices without ever exposing 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 Firefox may fit better

If you only need to autofill logins inside Firefox and want zero setup, it is the most frictionless option.

Switching from Firefox

Moving is straightforward: Firefox can export your entries to a CSV file, which storage-p imports as a generic CSV. See the step-by-step migration guide linked below.