JumpServer v5.0 Launches: Unified Client for SSH, RDP, K8s, DB & Web with AI Assist

Overview

JumpServer, an open-source bastion host and privileged access management platform with over 31,000 GitHub stars, has released version 5.0.0. The platform centralizes management of Linux servers, databases, Kubernetes clusters, and internal web portals, handling authentication, authorization, connection brokering, and full session auditing (command logs, file transfers, session recordings).

Key Features in V5

Unified Native Client for Multiple Asset Types

The new native client consolidates access to SSH, RDP, Kubernetes, databases, and web assets into a single asset tree. Previously, an operator might switch between three or four tools to log into a Linux server, query a database, and open an internal admin portal. Now all authorized resources appear in one interface, supporting search, connection, and session switching without leaving the client. The client also adds split-screen operation, a file workbench (upload local files and distribute the same file to multiple target servers), a script library for common inspection, deployment, and troubleshooting scripts, and direct SFTP server connections.

AI Assistance Inside SSH Sessions

V5 embeds AI helpers directly into daily workflows. Users can invoke an AI chat via a command inside an SSH session or open the client's AI assistant panel. Specific assistants include Script AI for generating inspection script drafts, SQL AI for writing database statements, and File AI for file transfer and management tasks. Because JumpServer already manages assets, accounts, permissions, and audit logs, future AI features plan to leverage this operational context for intelligent command recommendation, real-time risky-operation alerts, and automatic audit report generation.

Redesigned Terminal UI (KoKo TUI)

For command-line users, the KoKo TUI terminal interface has been overhauled. After login, assets can be browsed via an authorization tree, a type tree, or a favorites tree, and searched by name, address, or remark. Selecting an asset lets the user choose an account and protocol before connecting. Open sessions persist as tabs, allowing quick switching without exiting the terminal. The UI supports both keyboard and mouse, theme switching (dark/light), and language selection, preserving the familiar SSH-client entry point while improving asset discovery and multi-session handling.

Web Asset Access Without a Windows Jump Host

Operators can now connect to business systems, network device consoles, and other web assets directly from the client. The client auto-fills credentials; if the target site requires a CAPTCHA, the user completes the challenge in the rendered page. This eliminates the previous need for a dedicated Windows jump host and browser hop, treating web assets on par with servers and databases.

Deployment and Upgrade

Quick Online Installation

New installations require a clean 64-bit Linux server (minimum 4 CPU cores, 8 GB RAM, 100 GB disk). Run the official script:

curl -sSL https://github.com/jumpserver/jumpserver/releases/latest/download/quick_start.sh | bash

After completion, access the web console at http://<server-ip>:<port>. Default admin credentials are admin / ChangeMe; the password must be changed on first login. Then add assets, accounts, and authorization rules; users connect via the workbench.

Upgrade Guidance for Existing Users

Before upgrading, back up the database, configuration files, and session recordings. Follow the official upgrade documentation for step-by-step procedures.

Conclusion

JumpServer v5.0 establishes the foundation of a unified operations workbench, merging multi-protocol access, AI-assisted tooling, and an improved terminal experience. The real-world impact will depend on the delivery of planned risk-alerting and automated audit reporting features.