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
6 days agoRepository age
11 yearsVersion
v5.17.0License
AGPL-3.0Self-hosted
YesRepository
passbolt_api
Last 30 days

Both Passbolt and TeamPass have their unique strengths and serve similar purposes effectively. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
Passbolt significantly outpaces TeamPass in community adoption with 6,187 stars compared to 1,863 stars on GitHub. This 3.3x difference suggests Passbolt has a much larger and more active community. In terms of developer contributions, TeamPass has 571 forks, indicating moderate developer engagement.
TeamPass is growing faster, adding 34 stars in the last 30 days (+1.9%) against adding 46 stars for Passbolt (+0.7%). TeamPass is the smaller project of the two, so it is closing the gap rather than extending a lead.
Both projects show recent activity, with Passbolt last updated 6 days ago and TeamPass 6 hours ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Bash, PHP.
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.