Learn how Passbolt and TeamPass 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
Repository age
Version
License
Self-hosted
Repository

Last 30 days
Last commit
Repository age
Version
License
Self-hosted
Repository

Both Passbolt and TeamPass 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.
Passbolt significantly outpaces TeamPass in community adoption with 6,149 stars compared to 1,831 stars on GitHub. This 3.4x difference suggests Passbolt has a much larger and more active community. In terms of developer contributions, TeamPass has 571 forks, indicating moderate developer engagement.
Passbolt is growing faster, adding 38 stars in the last 30 days (+0.6%) against adding 3 stars for TeamPass (+0.2%). Passbolt is both larger and pulling further ahead.
Both projects show recent activity, with Passbolt last updated 19 days ago and TeamPass 16 hours ago.
TeamPass has been in development longer, starting 15 years ago, compared to Passbolt which began 11 years ago. This 4.2-year head start suggests TeamPass may have more mature features and established processes.
The projects use different licenses: Passbolt is licensed under AGPL-3.0 while TeamPass uses GPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Password Managers.
Both Passbolt and TeamPass offer self-hosting capabilities, giving you full control over your data and infrastructure.