Learn how Psono and Vaultwarden differ in their key features, development activity, technology stack and community adoption, so you can decide which of these password managers is best for you.
Last 30 days
Last commit
5 hours agoRepository age
10 yearsLicense
Apache-2.0Self-hosted
YesRepository
psono-server
Last 30 days
Last commit
17 hours agoRepository age
9 yearsVersion
1.37.4License
AGPL-3.0Self-hosted
YesRepository
vaultwarden
Both Psono and Vaultwarden have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, maturity, licensing and features when making your decision.
Vaultwarden significantly outpaces Psono in community adoption with 69,685 stars compared to 104 stars on GitHub. This 670.0x difference suggests Vaultwarden has a much larger and more active community. In terms of developer contributions, Vaultwarden has 3,369 forks, indicating strong developer engagement.
Vaultwarden is growing faster, adding 1,490 stars in the last 30 days (+2.2%) against adding 1 stars for Psono (+1%). Vaultwarden is both larger and pulling further ahead.
Both projects show recent activity, with Psono last updated 5 hours ago and Vaultwarden 17 hours ago.
Psono has been in development longer, starting 10 years ago, compared to Vaultwarden which began 9 years ago. This 1.4-year head start suggests Psono may have more mature features and established processes.
The projects use different licenses: Psono is licensed under Apache-2.0 while Vaultwarden uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Password Managers.
Both Psono and Vaultwarden offer self-hosting capabilities, giving you full control over your data and infrastructure.