The key terms around remote support, remote access and secure system access — explained briefly and clearly.
A technician joins the user's screen live, with their consent — typical for workstation support. In Termiverse via WebRTC right in the browser, no client to install.
Access to a device with nobody sitting in front of it — e.g. servers or workstations after hours. An always-on agent keeps the connection ready.
Permissions are granted through roles rather than per person. Each connection carries a right per role or user (READ_ONLY, CONNECT, ADMIN); the highest one applies.
Termiverse's billing unit: one channel = one connection or one monitoring target. The base plan includes 10 channels usable simultaneously, with more available to add.
A one-time token that lets an agent register itself with the right group during first install — no manual server configuration on the device.
A lightweight program on the target device that keeps an outbound connection to the server. That makes the device reachable without opening inbound ports.
A dedicated endpoint that makes SSH, RDP or VNC reachable to systems behind a firewall — with a target allowlist and no inbound port forwarding.
A network command that wakes a powered-off machine. Through the tunnel it can be triggered remotely, before you connect.
Access to sensitive systems is only possible after explicit approval by a second person. A dedicated approver role decides who grants it.
Recording a session for later replay — SSH as a terminal capture, RDP and VNC via guacd. An important record for audit and compliance.
A complete record of logins, sessions and permission changes — so it is traceable who accessed what, and when.
The Apache Guacamole server component that translates RDP, VNC and SSH into the browser. That is how graphical sessions run fully clientless.
A browser technology for real-time media. Termiverse uses it for attended screen access at low latency — with no extra software.
An SSH session that keeps running in tmux on the target server when the browser closes and resumes — including running programs — on reconnect.
A stored command you run with one click — globally or per connection, and optionally across several open SSH sessions at once.
Running the platform under your own brand: your logo, your colours and your own domain instead of a third-party vendor name.
Running the whole platform on your own infrastructure — full data sovereignty, with Termiverse on request and without a channel limit.
Graphical remote access to a machine's desktop. Termiverse shows it clientless in the browser (Guacamole-based), with no local RDP or VNC client.
A full SSH session right in the browser, with no local client. Termiverse uses xterm.js for it.
Reachability and status monitoring of connections and targets. A monitored target counts as a channel, just like a connection.
Start with the base plan or talk to us about the self-hosted option.