RustDesk

RustDesk is an open-source remote desktop application that does what commercial screen-sharing tools do, with one structural difference: the servers that introduce two peers and relay traffic between them can be run by you instead of by a vendor. The client is written in Rust and is published for Windows, macOS, Linux, Android, iOS and the web, with the source released under the GNU AGPL version 3. The practical consequence is that remote control, file transfer and unattended access do not have to pass through a third party's infrastructure if you would rather they did not.

Establishing a connection

On first launch the client displays an identifier for the machine and a one-time password, and it is ready to accept a session as soon as someone on that machine confirms it. From the other side you type the identifier, supply the password, and the remote desktop opens in a window with options for input, display selection, clipboard sharing and file transfer. Sessions can also be started the other way, with the controlling machine offering its screen. Because the same client acts as both ends, there is no separate server installation on the machines being helped, which is what makes it practical for supporting relatives or colleagues over a phone call.

Unattended access and the address book

Setting a permanent password turns a machine into one that can be reached without anyone present to approve the session, which is the feature that makes RustDesk useful for a small office or a home lab you administer from elsewhere. Saved peers can be kept in an address book and grouped, so a machine does not have to be remembered by a numeric identifier. Unattended access deserves the same caution as any remote administration channel: it is a permanent key to the machine, and it should be protected by a strong password and by limiting which networks the client is willing to accept connections from.

Self-hosting and what it changes

By default clients register with public rendezvous and relay servers run by the project, which is convenient and shared with everyone else using them. The alternative is to run the two server components yourself - the ID and rendezvous service and the relay service - typically as containers on a small virtual machine, then point each client at that address. Self-hosting brings the metadata under your control, usually improves latency because the relay sits near the machines involved, and enables end-to-end encryption with a key you generate and distribute to your own clients. Note that RustDesk Server Pro is a separate commercial product; the free server components are what the open-source project publishes.

Honest limits

Remote control depends on the desktop session agreeing to be controlled. On Wayland, capture goes through a desktop portal, so the user may be prompted to approve screen sharing and remote input can be restricted by the compositor in ways the application cannot override. Session quality depends on the relay's proximity and on the uplink of the machine sharing its screen; a long path through a distant relay is visible as latency. Availability of some conveniences, including address book synchronisation and access controls, depends on which server build you connect to. What the free client does not provide is a managed fleet platform: central policy, mass deployment, auditing and single sign-on are not part of it.

Where another product fits better

An organisation that must demonstrate compliance, produce access reports and roll the client out to thousands of machines should look at commercial remote monitoring and management suites, which exist for exactly that. Someone who wants zero configuration and vendor support may prefer a hosted service. If the goal is only to view a screen without installing anything on the far side, a browser-based tool will be less invasive. RustDesk is strongest for people who want capable remote access and prefer to own the servers that make it work.