Skip to main content
010 447 2445Contact
Arke Technologies home
Request a hardware quoteTalk to us
Arke Technologies home
A service-desk agent in a headset works at a desktop computer in a bright open-plan office.

RustDesk for business: self-hosted remote access explained

RustDesk is free, open-source remote desktop software that can run through servers an organisation hosts itself, so remote sessions stay under its control. This guide covers the RustDesk download, self-hosting, security and running costs for South African organisations, and why Arke Technologies runs its own remote support on RustDesk.

Join the Hesper early-access listRequest an IT assessment
Insights

RustDesk for business: self-hosted remote access explained

Last reviewed: September 2026, 11 min read

RustDesk is free, open-source remote desktop software that can run through servers an organisation hosts itself, so remote sessions stay under its control. This guide covers the RustDesk download, self-hosting, security and running costs for South African organisations, and why Arke Technologies runs its own remote support on RustDesk.

Last reviewed: September 2026, 11 min read

On this page

RustDesk in brief

  • Open source. The RustDesk client and its open-source server are published under the GNU AGPL-3.0 licence, with the code on GitHub (RustDesk, September 2026).
  • Cross-platform. The client runs on Windows, macOS, Linux and Android, where it can control other devices or be controlled; on iPhone and iPad it works as a controller only, because iOS does not allow those devices to be controlled remotely.
  • Self-hostable. Out of the box it connects through public servers run by the RustDesk project; a business can run its own ID and relay servers instead.
  • Encrypted. Sessions are end-to-end encrypted.
  • Free software, not a free service. Hosting, patching, access policy, logging and support still cost time or money.

What RustDesk is and how it works

RustDesk is remote desktop software. With the RustDesk client installed, an authorised person can see a computer's screen, control it, transfer files and chat, from another computer or a phone. It is written in the Rust programming language, hence the name, and developed in the open on GitHub, where anyone can read the code.

A connection relies on two server roles. The ID or rendezvous server (hbbs) registers each device's ID and brokers the connection; the relay server (hbbr) carries the session when two devices cannot connect directly, for example behind strict firewalls. When a direct connection is possible, traffic flows from device to device. Either way, the session is end-to-end encrypted with the NaCl cryptography library (RustDesk, September 2026).

Three support agents in headsets work at their desks in a quiet office.

Public servers or a self-hosted RustDesk server

The main business decision is who runs the servers (RustDesk, September 2026).

OptionHow it worksSuitsWatch for
RustDesk's public serversThe default client connects through ID and relay servers run by the RustDesk projectPersonal use and occasional helpShared infrastructure outside your control, with no service commitment to you
Self-hosted RustDesk Server OSSYour own ID and relay servers, with clients set to your server and its public keyIT teams that want control without a licence feeYou patch, monitor and back it up, and there is no central console for users or devices
RustDesk Server ProThe commercial self-hosted server, adding a web console, device groups, an address book, single sign-on, two-factor authentication, access control and logsOrganisations that need central administrationA subscription licence, tied to the ID server, on infrastructure you still run
A managed service on a provider's platformThe provider runs the servers, approvals and logs as part of its supportOrganisations that want remote support without running itWhere it is hosted, who can connect and what is logged

RustDesk download and installation, done safely

  1. Download from the source

    Take the RustDesk download only from the project's official website or its GitHub releases page. Fake download pages that imitate remote-access tools are a common way to spread malware.

  2. Choose the right package

    Installers exist for Windows, macOS and Linux, and there is an Android app. For company computers, use a package your device management tool can deploy.

  3. Point every client at your server

    Enter your ID server, relay server and public key in the client's network settings, or deploy a pre-configured client, so devices never fall back to public servers.

  4. Set access rules before rollout

    Decide who may connect to which devices, whether the user must accept each session, and which machines, if any, allow unattended access.

  5. Deploy at scale, not by hand

    Push the RustDesk install through Intune or another device management tool, and record it in your asset register; see device and IT asset management.

  6. Remove what you replace

    Uninstall old remote-access tools, so there is only one door to secure.

Self-hosting the RustDesk server

The open-source RustDesk server is light. It runs on a small Linux virtual machine or container, on premises (for example on Proxmox, VMware or Hyper-V) or in a cloud region. It needs a stable public address or DNS name, a handful of TCP and UDP ports in the 21115–21119 range open to your clients, and the server's public key distributed to every client, so that devices refuse a server impersonating yours (RustDesk, September 2026).

Treat it as production infrastructure: patch the host and the RustDesk server, monitor both roles, back up the key and configuration, and document the set-up. If the server is down, nobody can be helped remotely, and that is usually when help is needed most. Hosting it in South Africa keeps session brokering and relayed traffic in the country, which simplifies your POPIA records.

Is RustDesk safe? Security controls for business use

RustDesk is as safe as its source and its configuration. The encryption is sound and the code is open to inspection; the risks lie in who can connect, and how. For business use:

  • Self-host so that IDs and relays run on your servers, and distribute your server key to every client.
  • Give every technician their own account with two-factor authentication, never a shared password.
  • Require the user's approval for attended sessions, and limit unattended access to managed devices with a business reason.
  • Log every session: who connected, to which device, when and for how long. Review the logs monthly.
  • Patch clients and the server as releases arrive.
  • Train staff never to install remote-access software because a caller asks; support scams depend on it.
  • Treat screens as data. A remote session can expose personal information, so access must be authorised and recorded under POPIA. See what cyber security involves for the wider controls.

RustDesk licence, and the real cost of free remote access desktop software

The RustDesk licence, the GNU AGPL-3.0, lets you use the software free of charge, including in a business. Its main obligation applies if you modify RustDesk and offer the modified version to others over a network: you must then make the source code of your version available to them. Server Pro is a separate commercial licence.

Free remote access desktop software still costs something to run:

CostWhat it covers
HostingA server or virtual machine, and bandwidth for relayed sessions
AdministrationPatching, keys, backups and monitoring of the server
Access controlAccounts, approvals and reviews of who can reach which device
Logging and auditKeeping session records and reporting on them
SupportThe technicians who use the tool, and the service desk behind them
Optional licenceServer Pro, if you need a central console

Inside a managed IT contract, these costs sit within the per-user fee. Published South African managed IT rates run from about R180 to R400 per user per month (matnet.co.za, September 2026), for a far wider scope than remote access alone.

RustDesk compared with subscription remote-access services

QuestionSelf-hosted RustDeskTypical subscription remote-access service
Where connections are brokeredOn your serversIn the vendor's cloud
LicenceOpen source, with an optional Server Pro subscriptionA subscription per technician or per concurrent session
Where session traffic is relayedWhere you host it, for example JohannesburgThe vendor's chosen regions
Who patches the serverYou, or your IT providerThe vendor
Central managementBasic in the open-source server; full in Server ProUsually included

How Arke Technologies runs remote support on RustDesk

We run our own remote-access platform, built on open-source RustDesk, with a management system we own (device groups, approvals and session logs), on our own servers in Johannesburg. Every remote session is approved and logged, and everyone with access to your systems is bound by confidentiality and our security controls. Monitoring checks each computer every 15 minutes and logs faults as tickets automatically. A library of standard repairs fixes common faults, and the riskier repairs need a recorded human approval before they run.

Clients receive this as part of managed IT services and remote IT support. Incidents are prioritised from P1 (critical outage) to P4 (low-impact request), with targets agreed in your SLA, and a monthly service review reports on sessions, tickets and changes. For boards, session logs are evidence of technology governance under King IV Principle 12, and our controls are aligned with ISO/IEC 27001. Arke Technologies (Pty) Ltd is a Level 1 B-BBEE contributor (135% procurement recognition; sworn affidavit available on request), and company documents, our CSD supplier number and SARS tax compliance status are available on request. Your devices, data and credentials stay yours: if you leave, we remove our client software, close our access and hand over documentation. To weigh the model, read managed IT vs in-house IT and what managed IT services cost.

Hesper: the same platform for IT teams and service providers

Hesper, our IT operations platform for managed service providers and in-house IT teams, packages the same approach: remote access built on open-source RustDesk with a management layer we own (device groups, approvals and session logs), monitoring every 15 minutes with faults raised as tickets, a library of standard automated repairs with the riskier ones gated by recorded human approval, and ticketing tied to SLA clocks. It was built first for our own managed service.

Hesper launches in November 2026, with pricing published at launch. Until then, join the early-access list or read about Hesper remote access.

Related services

Related guides

Get our guides by email

Plain, sourced guides for the people who decide on and buy technology, sent to your inbox.

Topics (optional)

Leave these clear to receive everything.

By signing up, you agree that Arke Technologies (Pty) Ltd may email you guides and updates. Every email includes an unsubscribe link. Read our privacy notice.

Frequently asked questions

Is RustDesk free for business use? Show answer

Yes. RustDesk's client and open-source server are free to use in a business under the GNU AGPL-3.0 licence, which adds obligations mainly if you modify the software and offer it to others. The costs lie in running it: hosting, patching, access control, logging and support, plus a Server Pro subscription if you need central administration.

Is RustDesk safe? Show answer

RustDesk is safe when it is downloaded from official sources and configured with care. Sessions are end-to-end encrypted and the code is open to inspection. The risks are operational: public servers you do not control, shared passwords, unattended access left open and unlogged sessions. Self-hosting, individual accounts, user approval and session logs address them.

Where should I download RustDesk? Show answer

Download RustDesk only from the project's official website or its GitHub releases page, and check the publisher before you install. Avoid download sites that imitate them, which are a known route for malware. In a business, deploy a client pre-configured with your own server and key through your device management tool, rather than letting staff install their own.

Does RustDesk need an account? Show answer

No, not for basic use: the client connects with a device ID and a password or the user's approval. Accounts, a shared address book and device groups come with RustDesk Server Pro or a management layer such as ours, which is what a business needs to control who can reach which device and to keep a record of every session.

Does RustDesk work on Android and iPhone? Show answer

Yes, with a difference. On Android, RustDesk can control other devices and be controlled, once the phone grants the permissions it asks for. On iPhone and iPad it works as a controller only, because iOS does not allow those devices to be controlled remotely. Windows, macOS and Linux computers can both control and be controlled.

Can we host a RustDesk server on Proxmox? Show answer

Yes. The open-source RustDesk server runs in a small Linux virtual machine or container on Proxmox, VMware or Hyper-V, or in a cloud region. Give it a stable public address, open the TCP and UDP ports it needs in the 21115–21119 range, distribute its public key to every client, and patch, monitor and back it up like any production server.

What is the difference between RustDesk Server OSS and Server Pro? Show answer

RustDesk Server OSS is the free, open-source server that registers device IDs and relays sessions. Server Pro is the commercial version: it adds a web console, device groups, a shared address book, single sign-on, two-factor authentication, access control, logs and a custom-branded client. Its licence is tied to the ID server, so extra relay servers need no separate licence.

Remote support you can audit

Tell us how your team supports devices today. We will show you how approved, logged remote access and monitoring would work under one SLA, or add you to the Hesper early-access list. Browse more insights and guides.

Join the Hesper early-access list