Teampass vs Vaultwarden
Both are self-hosted password managers projects. This page compares how well each one is actually maintained — the part you cannot see from a feature list.
| Teampass | Vaultwarden | |
|---|---|---|
| Health score | 86/100 | 65/100 |
| Commits (11 mo) | 2381 | 169 |
| Commits (last 3 mo) | 933 | 31 |
| Stars | 1.8k | 68k |
| Latest release | 19 Sept 2026 | 13 Sept 2026 |
| Licence | GPL-3.0 | GPL-3.0 |
| Built with | PHP | Rust, Docker |
| Typical RAM | 1 GB | 2 GB |
Teampass
Password manager dedicated for managing passwords in a collaborative way. One symmetric key is used to encrypt all shared/team passwords and stored server side in a file and the database. works on any server Apache, MySQL and PHP.
High commit volume, frequent releases and growing activity.
Commit activity more than 92% of tracked projects; popularity more than 47%. How this is calculated.
Commits, last 11 months
Vaultwarden
Lightweight Bitwarden server API implementation written in Rust.
Maintained, but at a slower pace than the leaders in its category.
Commit activity more than 40% of tracked projects; popularity more than 98%. How this is calculated.
Commits, last 11 months
How to read this
Everything above is measured, not opinion: commit counts and release dates come from the public repositories, and the health score ranks each project against all 1352 projects we track. Read the full method.
What this comparison deliberately does not do is tell you which has the better feature set. Maintenance health tells you which project will still be receiving security fixes in two years. Decide that first, then compare features on the projects that survive the filter.
See every option in this category: self-hosted password managers.