jumpservervsTeleport
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| jumpserver | Teleport | |
|---|---|---|
| Score | 77/100 | 76/100 |
| Rank in category | #1 of 19 in Identity & Auth | #4 of 40 in Authentication |
| GitHub stars | 31 967 | 21 104 |
| Stars, last 30 days | +208 | +121 |
| Stable releases, 12 months | 14 | 6 |
| Latest release | v3.10.24 · 27 Oct 2026 | v18.10.0 · 8 Jul 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | GPL-3.0 | AGPL-3.0 |
| Main language | Python | Go |
Which one should you pick?
jumpserver scores 77/100 against 76/100 for Teleport, so it is the safer default.
jumpserver ships more often: 14 stable releases in the past year, against 6 for Teleport.
If you want the quickest setup, jumpserver is easier to run; Teleport needs more configuration.
Key differences
- License: jumpserver is GPL-3.0, Teleport is AGPL-3.0.
- Language: jumpserver is written mainly in Python, Teleport in Go.
- Platforms only Teleport lists: AWS, Kubernetes.
- Features only jumpserver lists: Access control policies (ACL), Account discovery, Built-in AI assistant, Command and login audit logs and 10 more.
- Features only Teleport lists: Agentless mode, Cloud provider console access, Database Access, Just-in-Time (JIT) access and 9 more.
jumpserver details →Teleport details →