Administer Linux and Windows servers and virtual machines entirely from afar. Termiverse bundles SSH terminal, RDP and VNC in a browser-based interface and organises every connection by your existing inventory groups — without a locally installed client and without inbound port forwarding.
Anyone looking after many servers soon depends on a chain of VPN, jump host and locally maintained SSH configs. Windows systems need a separate RDP client, Linux another terminal. Who may access what is rarely defined centrally, but scattered across individual key files. And if the connection drops during a long maintenance run, the session and its progress are lost. That costs time and makes every audit trail harder.
Deploy the agent once via an enrollment token — as a Windows service or on Linux. Servers behind a firewall or NAT connect outbound over TLS, with no inbound port forwarding and no VPN.
All servers and VMs appear in the grid, sorted by your inventory groups. One click starts an SSH terminal, RDP or VNC — role-based access (RBAC) checks the permission per group first.
You work in the terminal or on the remote desktop. SSH sessions keep running as a persistent tmux session even when the browser closes; every session lands encrypted in the audit log and can be recorded.
Full SSH sessions right in the browser — no locally installed client.
Graphical remote-desktop access to Windows and Linux systems from the same interface.
Connections appear by your existing inventory groups; permissions are granted per group (RBAC). Every access is traceable as a session recording.
VPN dial-in and a jump host for every access, one client for RDP, another for the terminal, scattered SSH keys — and a dropped connection takes the running maintenance job down with it.
One deck for SSH, RDP and VNC in the browser. No VPN, no port forwarding, access behind the firewall via the tunnel — persistent tmux sessions keep running, every access governed by RBAC and traceable in the audit log.
A database server behind the firewall is due for a big update overnight. The administrator opens Termiverse in the browser, connects via SSH through the firewall tunnel — without a VPN — and starts the update in a tmux session. When the laptop goes to sleep and the browser closes, the session keeps running on the server undisturbed. In the morning the admin reattaches to the same session, checks the log and closes the ticket. The full recording later serves as evidence for the audit.
Start with the base plan or talk to us about the self-hosted option.