DesktopWhat you need to know
Traditional remote desktop setups can require a publicly reachable computer, a VPN, or router rules that forward incoming traffic. DesktopBee is built around a relay model: the Windows application connects outward to DesktopBee Cloud, and the viewer connects to the same service. This can simplify planned support sessions across home and office networks.
What port forwarding normally does
With a direct inbound remote desktop server, a router rule may be needed to send traffic from the internet to a specific machine. Exposing remote access directly can create security and maintenance concerns if it is not carefully protected and updated.
How the DesktopBee relay is different
The host starts an outbound connection to DesktopBee Cloud rather than waiting for unsolicited inbound connections. A browser or other Windows client makes its own connection to the relay. The relay helps establish an authorized session after the viewer provides the code and receives host approval.
What you still need
Both sides need usable internet access and a network that permits the relevant outbound connections. Corporate firewalls, proxies and endpoint restrictions can still block the service. A relay does not guarantee that every captive or restricted network will work.
Security trade-offs to understand
Convenience is not the same as end-to-end security. DesktopBee currently uses TLS between participants and the relay, but the relay is not yet end-to-end encrypted. The current version also requires host consent and does not support unattended access. Assess those limitations before using it for a particular job.
Frequently asked questions
Must I open Remote Desktop Protocol (RDP) ports?
No inbound RDP port-forwarding is required for the intended DesktopBee Cloud workflow.
Does it work behind any firewall?
Not necessarily. Some managed networks block WebSocket or other outbound traffic needed by the service.
Is relay access equivalent to a VPN?
No. DesktopBee is designed around individual remote desktop sessions, not a general-purpose private network.