Unattended remote control for MSPs: connect even when nobody is there

KairosLink remote control connects in seconds to any managed computer, straight from the web panel and with nobody on the other side, on Windows and on macOS. On Windows, the technician can see the logon screen, enter their credentials and keep working after the session change, with the connection encrypted end to end.

The MSP's real case: the locked PC and the customer who already left

Real maintenance happens outside the customer's hours: the machine was left locked or logged off, and the technician needs to get in with their administrator account. KairosLink shows the Windows logon screen, lets you type credentials remotely and keeps control after the session change. If the connection drops during a logoff or a reboot, the viewer reconnects on its own with automatic retries, without the technician starting over. On a Mac, remote control comes out of the same panel with the same viewer: the Mac asks once for the system permissions macOS requires (Screen Recording, Accessibility and Input Monitoring), and from then on the session works just like on Windows.

Connection in seconds, straight from the panel

No hunting for IDs or sharing passwords over chat. The technician clicks Connect on the computer, the panel generates a single-use token that expires in 60 seconds and the desktop viewer opens and connects automatically. Full-color screen, mouse, keyboard and two-way clipboard, with a toolbar to adjust quality, zoom, pick a monitor and send Ctrl+Alt+Del.

The connection negotiates its path in three steps

Before the first frame, the connection tries the possible paths between the technician and the computer and keeps the best one available. There are three, and they are always tried in this order:

• 1. LAN. If the technician and the computer are on the same network, the session goes over the local network and never leaves for the internet. Latency of 3 to 5 ms.
• 2. Direct peer to peer. If they are on different networks and the direct path is possible, the session goes point to point, with no intermediary. Latency of 21 to 26 ms.
• 3. Relay. Last resort, when NAT or the firewall will not let the direct connection through. Latency of 49 to 60 ms.

The relay is not the usual path: it is what keeps the connection from depending on how the customer's network happens to be built. A locked down corporate firewall or a NAT that will not cooperate do not leave the technician outside, because the third step is always there.

And the path is not a black box. The viewer toolbar shows which of the three the session ended up on, so the technician always knows whether they are on LAN, on direct peer to peer or on relay.

Gets through the firewalls that block other tools

Traffic travels encrypted over secure WebSocket on port 443, the same port any HTTPS website uses. That allows connections through corporate firewalls, mobile networks and internet providers that block the non-standard ports of traditional remote desktop tools. When the connection reaches the third step, the relay is in Sao Paulo, Brazil, with latency around 56 ms measured from Argentina.

Frequently asked questions