One workspace to connect to and control your infrastructure.

Start with reliable access and keep related work together

Remote work is often scattered across terminals, jump scripts, port forwards, file-transfer clients, monitoring pages and deployment flows. Runory organizes those jobs around one server session: run commands in Terminal, work with directories in Files, investigate in Dashboard and Incident views, then handle services and deployments without losing context.

Host groups, search and multiple tabs separate production, staging and development. Connection state is explicit, while terminal output streams directly to xterm instead of becoming persisted application state.

• Password, private-key and encrypted-key authentication
• Jump hosts, local tunnels and bastion access
• English and Chinese interfaces with light and dark themes

Connect status, action and evidence

Dashboard, operations panels and Incident Packs collect data over the existing SSH connection, so they do not require a resident Runory monitoring agent. Docker, PM2, Nginx, logs, Git deployments, SSL, backups and Cron are organized as business-specific actions; Website, Nginx, Docker, Disk and Service packs connect diagnostic evidence to repair plans.

Deployments and Fleet writes retain stages, per-target status and history. Structured writes use approval, verification and rollback plans where rollback is truly supported, rather than hiding remote execution behind a single button.

Cloud sync remains optional

You can use local host management, SSH, jump hosts, tunnels and the workspace without an account. When you opt into sync, host and group inventories are encrypted inside the Rust Core before an encrypted copy is uploaded. Passwords, passphrases, private keys, known hosts and terminal output stay out of sync data.

Conflicts are previewed before merging, and team spaces use organizations, roles and access policies. Server connections still originate in the local client; the web portal does not decrypt your server inventory.