jumpservervsWarpgate
Two self-hosted Teleport alternatives, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| jumpserver | Warpgate | |
|---|---|---|
| Score | 77/100 | 75/100 |
| Rank in category | #1 of 19 in Identity & Auth | #11 of 78 in Security |
| GitHub stars | 31 970 | 8 274 |
| Stars, last 30 days | +211 | +207 |
| Stable releases, 12 months | 14 | 35 |
| Latest release | v3.10.24 · 27 Oct 2026 | v0.30.4 · 3 Nov 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | Apache-2.0 |
| Main language | Python | Rust |
Which one should you pick?
jumpserver scores 77/100 against 75/100 for Warpgate, so it is the safer default.
Warpgate ships more often: 35 stable releases in the past year, against 14 for jumpserver.
If you want the quickest setup, Warpgate is easier to run; jumpserver needs more configuration.
Key differences
- License: jumpserver is GPL-3.0, Warpgate is Apache-2.0.
- Language: jumpserver is written mainly in Python, Warpgate in Rust.
- Platforms only Warpgate lists: Helm.
- Features only jumpserver lists: Access control policies (ACL), Account discovery, Built-in AI assistant, Command and login audit logs and 9 more.
- Features only Warpgate lists: Access tickets, Admin web UI, Browser-based SSH / RDP / VNC access, Brute-force login protection and 10 more.
- Both offer: Role-based Access Control.
jumpserver details →Warpgate details → All Teleport alternatives →