Shortest path, lower latency
Every session starts on the Silux relay so it always connects. The viewer then offers a WebRTC data channel; once it opens, picture frames and your input move over it directly. On the same office network that means LAN latency.
Through NAT, with our own STUN
Each side learns its public address from the STUN responder built into the Silux relay (UDP 3478), so direct links also work across many home and office routers. No Google or other third-party servers are involved.
Never worse than the relay
If a firewall blocks the direct path, nothing changes: the relay keeps carrying the session. If the direct link drops mid-session, frames switch back to the relay at once and the picture repaints from a keyframe.
Same low bandwidth
The direct link carries the same SXTL1 tile stream, split into small messages that every browser accepts. Guests watching a session stay on the relay; the direct path is used while you are the only viewer.
Your choice
Security policy has a Direct connections switch. Turn it off and every session stays on the relay for networks that require it. A Direct badge shows when the picture is coming straight from the computer.
Frequently asked questions
Is Silux Connect peer-to-peer?
When the network allows it, yes: the picture and input go directly between the computer and the browser over WebRTC. Otherwise the session uses the Silux relay.
Do I need to open ports for direct connections?
No. Direct links use NAT traversal; if they can't form, the relay is used automatically.
Can I force all sessions through the relay?
Yes. Turn off Direct connections in Security policy.
Related features
No viewer, no upload: remote desktop that goes quiet when nobody watches
Connect by ID and code — the person at the computer decides
Show only the window you need — and send less
See how this compares on the feature matrix, or find Silux Connect in your country and city.