jumpservervsOAuth2 Proxy
Two self-hosted Identity & Auth projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| jumpserver | OAuth2 Proxy | |
|---|---|---|
| Score | 77/100 | 75/100 |
| Rank in category | #1 of 19 in Identity & Auth | #3 of 19 in Identity & Auth |
| GitHub stars | 31 970 | 15 381 |
| Stars, last 30 days | +211 | +223 |
| Stable releases, 12 months | 14 | 11 |
| Latest release | v3.10.24 · 27 Oct 2026 | v7.15.6 · 5 Nov 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | MIT |
| Main language | Python | Go |
Which one should you pick?
jumpserver scores 77/100 against 75/100 for OAuth2 Proxy, so it is the safer default.
jumpserver ships more often: 14 stable releases in the past year, against 11 for OAuth2 Proxy.
Key differences
- License: jumpserver is GPL-3.0, OAuth2 Proxy is MIT.
- Language: jumpserver is written mainly in Python, OAuth2 Proxy in Go.
- Platforms only OAuth2 Proxy lists: Go Install, Helm.
- Features only jumpserver lists: Access control policies (ACL), Account discovery, Built-in AI assistant, Command and login audit logs and 10 more.
- Features only OAuth2 Proxy lists: Configuration validation, Custom Templates, Email and group access control, Health check endpoints and 9 more.
jumpserver details →OAuth2 Proxy details →All Identity & Auth projects →