Cross-Platform SSH Done Right

·Marcus Lee

The Platform Challenge

Most SSH clients are built for one platform and then ported to others as an afterthought. The result is usually a great experience on the original platform and a mediocre one everywhere else. We wanted JumpTerm to feel native on every platform from the start.

On macOS, that means proper keyboard shortcuts, system menu bar integration, and support for the Secure Enclave on Apple Silicon for biometric vault unlock. On Windows, it means native terminal rendering, proper clipboard handling, and Windows Hello integration. On Linux, it means supporting both X11 and Wayland, packaging for major distributions, and respecting system themes.

Mobile as a First-Class Citizen

Mobile SSH is usually painful. Tiny keyboards, accidental disconnections, and apps that feel like afterthoughts. JumpTerm's mobile apps are designed around how people actually use SSH on their phones: quick checks on running processes, emergency fixes, and monitoring.

The mobile terminal includes a smart toolbar with common keys (Tab, Ctrl, Esc, arrow keys) that are hard to reach on a touch keyboard. Vault sync ensures your connections are always available, and tmux resume means you can check on a long-running process without losing state.

Shared Codebase, Native Feel

JumpTerm's core is written in Rust, which gives us memory safety, performance, and the ability to share cryptographic and sync logic across all platforms. The UI layer is platform-native: Swift on Apple platforms, Kotlin on Android, and a shared desktop shell for macOS, Windows, and Linux. This architecture lets us move fast while maintaining the native feel that each platform's users expect.