jumpservervswerbot
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| jumpserver | werbot | |
|---|---|---|
| Score | 77/100 | 36/100 |
| Rank in category | #1 of 19 in Identity & Auth | #36 of 40 in Authentication |
| GitHub stars | 31 970 | 172 |
| Stars, last 30 days | +211 | +3 |
| Stable releases, 12 months | 14 | 0 |
| Latest release | v3.10.24 · 27 Oct 2026 | — |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | Other |
| Main language | Python | Go |
Which one should you pick?
jumpserver scores 77/100 against 36/100 for werbot, so it is the safer default.
jumpserver ships more often: 14 stable releases in the past year, against 0 for werbot.
If you want the quickest setup, jumpserver is easier to run; werbot needs more configuration.
jumpserver is growing faster right now (+211 stars in 30 days).
Key differences
- License: jumpserver is GPL-3.0, werbot is Other.
- Language: jumpserver is written mainly in Python, werbot in Go.
- Features only jumpserver lists: Access control policies (ACL), Account discovery, Built-in AI assistant, Command and login audit logs and 10 more.
- Features only werbot lists: Agentless server connection, Audit Logging, Automated SSL certificates, Certificate-based authentication and 10 more.
jumpserver details →werbot details →