Manage VMs by project, not by host list
SSH, SFTP, encrypted credentials, and agentless monitoring in one desktop app for agencies and MSPs.
The hard part is not opening an SSH session
Any tool can open SSH. The hard part starts when you manage infrastructure for many customers: which host belongs to whom, where passwords live, and what to send at month-end.
A flat host list with no clue which customer owns each machine.
Projects, tagged VMs, and the right machine in two clicks.
Passwords in a shared Excel file.
An AES-256-GCM vault keyed with Argon2id.
A customer asks what you did this month.
One self-contained HTML monthly report, ready to send.
Enough to replace the tool sprawl
Every feature has its own guide.
Projects & VMs
Group servers by customer or environment, with tags that make the right VM easy to find.
View guide →Multi-tab SSH terminal
Run multiple SSH sessions in one window, with a real PTY for vim, htop, and tmux.
View guide →Encrypted password vault
Keep passwords and SSH keys in an AES-256-GCM vault protected by your master password.
View guide →Agentless monitoring
Collect CPU, RAM, disk, network, and process data through one read-only SSH command.
View guide →Alerts & drift detection
Spot unreachable VMs and meaningful changes in security-related server configuration.
View guide →Monthly customer reports
Generate a self-contained HTML file with the month’s metrics and events, ready to send.
View guide →SFTP file transfer
Move files between your machine and a VM without maintaining a separate transfer tool.
View guide →Import from ~/.ssh/config
Bring existing hosts, ports, and users into a project instead of entering them again.
View guide →Keyboard first
Use the command palette and shortcuts to reach projects, VMs, and common actions quickly.
View guide →Customers will ask what this tool runs on their servers
One fixed, read-only sh command, shown verbatim in the app.
View the complete probe command →LC_ALL=C; export LC_ALL
echo '@@VMOPS:uptime@@'; cat /proc/uptime
echo '@@VMOPS:load@@'; cat /proc/loadavg
echo '@@VMOPS:cpu@@'; grep '^cpu ' /proc/stat
echo '@@VMOPS:mem@@'; grep -E '^(MemTotal|MemFree|...)' /proc/meminfo
echo '@@VMOPS:net@@'; cat /proc/net/dev
echo '@@VMOPS:disk@@'; df -P -k
echo '@@VMOPS:procs@@'; ps -eo pcpu,pmem,comm --sort=-pcpu
echo '@@VMOPS:ports@@'; ss -H -tuln
echo '@@VMOPS:users@@'; cut -d: -f1,3,7 /etc/passwd
echo '@@VMOPS:keys@@'; ... authorized_keys
echo '@@VMOPS:sudoers@@'; cat /etc/sudoers ...
echo '@@VMOPS:auth@@'; journalctl -u sshd ...
echo '@@VMOPS:end@@'You hold the keys to someone else's infrastructure
The password vault uses two layers of keys and has no cloud sync.
Read the full security model- AES-256-GCM
- Authenticated encryption with a random nonce for every blob.
- Argon2id
- 64 MiB memory, 3 passes.
- Two-layer keys
- Changing the master password rotates the data key.
- OS keychain
- Only the data key is remembered, never the password.
- Zeroize
- Plaintext secrets live briefly in memory.
- TOFU host key
- Warns when a server key changes.
Frequently asked questions
Is my customer data sent to any server?
No. Data stays on your machine, and the app has no cloud synchronization.
Do I need to install an agent on servers?
No. Monitoring uses one SSH connection and one fixed read-only command.
Does the application open any extra ports?
No. It uses the server’s existing SSH connection.
What if I forget the master password?
There is no recovery mechanism. The master password is never stored anywhere.
Can I use my existing ~/.ssh/config file?
Yes. Import its hosts, ports, and users into a project instead of entering them manually.