The two camps
Remote-desktop software falls into two architectural camps:
- Cloud relay (TURN-centric): screen data goes from the host to a cloud server, which forwards it to the client. Both endpoints connect “outward” to the vendor, who handles the routing.
- Peer-to-peer (P2P): host and client open a direct tunnel — usually via UDP hole punching through NAT routers. Screen data flows directly, with no middleman.
In practice the lines are blurry — almost every P2P tool has a TURN relay as a fallback for the ~5% of connections where direct P2P fails (symmetric NAT, restrictive corporate firewalls).
What changes with P2P
Latency. For a direct P2P connection from Bern to Zurich, the latency is roughly the fibre round-trip plus 1-2 ms encoding overhead — typically 5-15 ms. With a cloud relay in Frankfurt the detour adds up: 30-50 ms. Clearly noticeable in mouse control.
Endpoint bandwidth load. With P2P, each side carries exactly its own up- and download cost. With a cloud relay, the data stream doubles on the vendor side, which is often monetised through throttling or data caps in free plans.
Privacy. The biggest difference. With P2P the vendor sees at most that a connection happens (for billing), but not what is transmitted. With a cloud relay every frame passes through third-party infrastructure — even if encrypted, the vendor has metadata + timing information.
When cloud relay still makes sense
P2P isn’t always the right answer:
- Symmetric NAT: some mobile carriers and corporate firewalls don’t allow UDP hole punching. A relay MUST step in.
- Multi-party sessions: more than two participants (training, screen presentations) are simpler over a central server than over N×(N-1)/2 P2P tunnels.
- Compliance recording: if every session has to be recorded for audit, the recording sits on the relay server.
Hybrids are the rule
Most current tools are hybrid:
- WinDesk: P2P-first, Swiss TURN relay as fallback. ~95% of connections direct P2P.
- AnyDesk: P2P-first, similar.
- TeamViewer: more cloud-centric, more routing through Frankfurt servers (default).
How to test
In your tool: start a session, look at the connection status — almost every tool shows whether the connection is “direct” or “relayed”. If always relayed: check NAT configuration or move to a more P2P-capable tool.
Conclusion
If privacy, latency and bandwidth efficiency matter: pick a P2P-first tool. If multi-party sessions or compliance recording are critical: a cloud-centric tool may fit better. For 90% of IT-provider and SME use cases, P2P is the right approach.
WinDesk is P2P-first with a Swiss relay fallback. Free plan with no account: windesk.ch/en/download.