Our take
- Activity
- 77
- Community
- 84
- Issues
- 92
- Pull requests
- 81
+181 stars in the last 30 days
- Merges more pull requests than 91% of the projects we track
- Closes issues faster than 81% of the projects we track
- More contributors than 78% of the projects we track
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
31,961Forks
5,823Change since Nov 14, 2026: +2 stars·0 forks
Overview
JumpServer is a privileged access management (PAM) platform that provides a unified workspace for connecting to and managing privileged access across infrastructure and applications. It addresses the challenge of giving teams controlled access to varied systems through separate connection methods and tools.
The project is composed of multiple services for the platform, web interface, terminal, protocol connections, and AI capabilities. It is aimed at organizations that need a central access layer for IT and DevOps workflows, rather than a standalone SSH client.
Key Features
- Centralized access to SSH and RDP systems, Kubernetes, databases, websites, RemoteApp, and VirtualApp.
- Web interface and web terminal, with a native client listed among the project components.
- Protocol connector and proxy components for access to managed systems.
- Web-based database connector.
- AI component included in the core project lineup.
- Separate installer and web gateway projects support deployment and delivery.
- Additional enterprise components cover Windows and Linux application access, RDP, database, and VNC proxying.
Use Cases
- IT teams can provide staff with a common access workspace for servers and other managed assets.
- DevOps teams can reach Kubernetes environments and infrastructure through a centralized access platform.
- Organizations managing multiple database systems can use the web database connector as part of their access workflow.
- Teams that need remote desktop or application access can evaluate the listed RDP, VNC, and application connector components, noting that several are enterprise components.
Getting Started
The README recommends a clean 64-bit Linux server with at least 4 CPU cores and 8 GB of RAM. Start the quick installer with:
curl -sSL https://github.com/jumpserver/jumpserver/releases/latest/download/quick_start.sh | bash
See the README and official documentation for setup details.
Alternatives
- tabby-web: Tabby Web provides browser-based terminal access and client configuration sync, while JumpServer adds broader privileged-access controls across servers, databases, and other resources.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| jumpserver | Python | GPL-3.0 | 31.7k | Not checked yet |
| tabby-web | Python | MIT | 1.5k | Quiet |
Considerations
- The documented quickstart has a substantial baseline requirement: 64-bit Linux, 4 CPU cores, and 8 GB of RAM.
- The quickstart command downloads and runs a shell script, so review the installer and deployment guidance before using it in a production environment.
- The README lists enterprise components alongside core projects, and some enterprise components are marked private. Check component availability and edition requirements for the protocols and applications you need.
- The repository uses GPL-3.0, which may affect how you distribute or integrate the software.
- The quickstart credentials shown in the README use a default password. Change it during initial setup.
Found this useful?
Share it with someone who would like jumpserver.