Passbolt vs Passky
| Tagline | Open-source password manager for teams with granular sharing and PGP encryption | Lightweight self-hosted password manager with a clean web UI |
| Category | Password Managers & Secrets | Password Managers & Secrets |
| Replaces | 1Password, LastPass, Dashlane | 1Password, LastPass, Dashlane |
| GitHub stars | 6.1k | 244 |
| Language | PHP | PHP |
| License | AGPL-3.0 | GPL-3.0 |
| Self-host difficulty | 3/5 Moderate | 2/5 Simple |
| Deploy options | Docker Docker Compose Kubernetes Manual | Docker Manual |
| Managed hosting | ||
| Last updated | 12 days ago | 10 months ago |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Passbolt
- Several features (SSO, directory sync, MFA policies, tags) are gated behind paid Pro/Cloud editions
- Relies on browser extensions; mobile app maturity lags 1Password/Dashlane
- Initial setup (GPG server keys, SMTP, HTTPS) is fiddly compared to consumer apps
- No personal/consumer focus — geared toward team credential sharing
Passky
- No emergency access or secure sharing between users on the same server
- Audit log and reporting features are basic compared to enterprise vaults
- Community and ecosystem are small; long-term maintenance is less certain
Bottom line
Choose Passky if you want the lower-effort setup; choose Passbolt for the larger community and ecosystem. Passbolt has seen more recent development. Open each guide below for deploy steps and the full feature gap.
Passbolt
Open-source password manager for teams with granular sharing and PGP encryption