Profiles and credentials stay separate
ServerProfile contains display and connection metadata only; the local Credential Vault owns passwords, passphrases and private-key content.
SSH, JUMP, TUNNELS AND REMOTE FILES
Organize servers with host groups and multiple sessions, work in an interactive PTY, and open an independent SFTP Channel on the same connection. When needed, use a single-hop jump host, a loopback TCP tunnel, or JumpServer / Teleport / Boundary bastion access. Unknown hosts require explicit trust; changed host keys block the connection.
AccessDirect / jump / tunnel
TerminalInteractive PTY
VerifyHost key required
Core capabilities
ServerProfile contains display and connection metadata only; the local Credential Vault owns passwords, passphrases and private-key content.
Single-hop jumps verify both ends independently. Local tunnels bind only 127.0.0.1, start and stop explicitly, and never occupy a terminal tab.
SFTP uses an independent Channel on the authenticated Transport for browsing, uploads, downloads, directories, renames and deletes.
In detail
Create custom groups, search names and addresses, and move quickly between environments. Authentication supports passwords, file-based keys and passphrases for encrypted keys. On mobile, imported keys use opaque key IDs instead of assuming arbitrary desktop paths are available.
A single state model describes idle, connecting, verifying-host, authenticating, opening-shell, connected, disconnected and error, so the interface can tell you what is happening without conflicting indicators.
A target profile can reference one direct profile as a single-hop jump: authenticate A, open direct-tcpip to B, then verify and authenticate B independently before exposing only B's normal ServerSession. Local TCP tunnels save rules, start explicitly and probe reachability when needed; reverse forwarding, SOCKS and public sharing stay out of scope.
JumpServer, Teleport and Boundary providers authenticate and select targets through a unified access framework, then return to the existing Terminal / SFTP / Agent boundaries instead of inventing another shell path.
For an unknown host, choose Trust Once, Trust & Remember or Cancel. When an established host key changes, Runory blocks the connection. Known hosts and credentials live in the Rust Core; the React interface cannot bypass verification or read a remembered password in plaintext.
The interactive PTY supports resize, copy, paste, search and CJK output. Files provides breadcrumbs, refresh, metadata and a transfer queue. Terminal and SFTP share a ServerSession while retaining separate Channel lifecycles.
Frequently asked questions
Yes. A passphrase can be submitted for the current connection without being stored in ServerProfile.
No. Both A and B on a jump path are verified and authenticated independently; a changed key on either end blocks the connection.
The SFTP Channel belongs to the existing ServerSession and uses the same SSH Transport and authentication context.