Skip to content

Self-hosted remote desktop (RustDesk)

Remote support through your own server, with no firewall changes on the computers you connect to

We set up an open-source RustDesk server on your cloud host. Helping colleagues remotely and reaching office or shop computers all go through that one server, like a private line of your own. The computers you connect to only need internet access: they connect out to the server, so there is no need for a fixed IP or for opening inbound firewall ports. When two machines can reach each other they connect directly; when they cannot, your server relays the session. Sessions are encrypted end to end, with no limits on seats or connection hours.

A good fit when

  • You support colleagues or customers remotely and do not want sessions passing through a third party’s public servers
  • Office, shop or factory computers sit behind a firewall and need to be reachable after hours or while you travel
  • Your current remote desktop software charges per seat or per connection, and you would rather run your own server

Not a fit when

  • You only help family members now and then (RustDesk’s public servers are enough)
  • Your security policy does not allow remote control software to be installed

What you get

  1. 01Connection server: RustDesk’s ID and relay servers set up on your cloud host, with a key so only computers carrying that key can use it
  2. 02Clients: a Windows installer with your server address and key built in, ready to connect once installed; setup steps for macOS, Linux and Android
  3. 03Unattended access: office or shop computers set with a permanent password and start on boot, reachable with no one on site
  4. 04Connection tests: a real session from each site, confirming whether it connects directly or through the relay, with relay-only sites noted
  5. 05Handover guide: adding a computer, changing the permanent password, and what to check after the server restarts
  6. 06Looked after once live: server updates and security patches under a maintenance plan

Frequently asked

No. Both the controlled and the controlling computers connect out to your server, so internet access is all they need: no fixed IP, no port forwarding on the router. Only your cloud host has inbound ports open (TCP 21115–21117, UDP 21116), and we configure that.