RustDesk: remote desktop, self-hosting and Server Pro costs

RustDesk review: remote access, client permissions, your own ID and relay server, OSS versus Pro, annual pricing and the first connection.

What is RustDesk used for?

RustDesk connects to a remote computer for screen sharing, keyboard and mouse control, and file transfer. It can use the project's public infrastructure or an ID and relay server you operate. That makes it relevant both to occasional support and to teams that want to manage their own connection infrastructure.

Separate the desktop client from the server edition. Installing a client gives you the connection interface; a self-hosted server handles device discovery and relaying, while Server Pro adds management features.

RustDesk: key information
ItemDetails
PlatformsWindows, macOS, Linux, Android
TaskNetworking and tunnels
Download sourceUse the project’s official page and choose the build for your operating system.
Version and termsChecked 15 November 2026. Open-source client and Server OSS; Server Pro is a separate paid self-hosted product.

RustDesk interface and illustrations

The documentation screenshot shows your device ID and the field for connecting to another device. The settings menu contains security permissions, network/server configuration and display options. The second image below shows the server fields.

Download RustDesk from the official website

Use rustdesk.com to reach the official releases. Clients cover Windows, macOS, Linux and Android; capabilities and permissions vary by platform. Choose the package for the machine that will be controlled as well as the machine providing support.

For a first session, use two devices you control and an explicitly agreed connection. On macOS, grant the required screen-recording and accessibility permissions through system settings.

Getting started with RustDesk

  1. Download official clients for both devices and start them.
  2. On the receiving computer, review permissions for control, clipboard and file transfer.
  3. Obtain its ID through your agreed communication channel and enter it on the controlling device.
  4. Confirm the session on the receiving side or use the access method configured by its owner.
  5. Test a harmless task, check display scaling and close the connection.
  6. Enable unattended access only for a defined need; document who can use it and how that access will be removed.

Remote support and access to your own computer

A support technician can see an agreed problem on a user's desktop; a home user can reach a computer left running elsewhere. For an organization, the choice of server affects who maintains updates, relay capacity and access settings. Self-hosting brings those operational tasks to your team.

How your own RustDesk server works

Server OSS uses hbbs for ID/rendezvous and hbbr for relaying. Clients try to establish a connection; the relay carries traffic when a direct path is unavailable. A VPS therefore needs enough bandwidth for the sessions that actually use it.

Client network settings

Configure the ID server and its public key on clients; set relay and API fields as required by the chosen edition. The API field belongs to Pro deployments. Keep the server key and configuration in your deployment records.

Official RustDesk documentation: ID, relay and API server settings.
Official RustDesk documentation: ID, relay and API server settings.

OSS and Pro: licence and infrastructure costs

The checked pricing page is for self-hosted server licences, not hosted desktops. Pro is billed annually; the displayed monthly amount is a comparison figure. The server itself and its network traffic are additional operating costs.

RustDesk Server pricing checked 15 November 2026 · USD
EditionDisplayed monthly equivalentAnnual amountIncluded management
OSS$0$0 licenceCommunity server
Individual Pro$11.88$142.561 login user; 20 managed devices
Basic Pro$23.88$286.5610 login users; 100 managed devices

Which Pro features matter?

  • Individual includes the web console, address book, access control and audit log.
  • Basic adds features including OIDC, LDAP and custom client generation.
  • The web console and the browser-based remote-control client are separate features. The latter has an additional plan eligibility condition.

Permissions and day-to-day administration

Give a session only the capabilities needed for the task. Viewing a screen, transferring files and controlling input are different permissions. Keep unattended-access credentials separate from temporary support sessions, and remove access when a person or device leaves the workflow.

A practical team checklist

  • Keep the server and clients updated.
  • Record the devices that use a persistent access method.
  • Review clipboard and file-transfer permissions.
  • Check relay bandwidth before planning several simultaneous high-resolution sessions.

Limitations and data protection in RustDesk

The receiving device must be running and reachable. System permissions, login screens and display-server support depend on its OS and installation mode.

Remote-access software gives another person substantial control. Confirm the identity and purpose of support before accepting a connection.

Alternatives for related tasks

Remmina is useful when connecting to existing RDP, VNC or SSH services. Tailscale creates network reachability between devices but does not itself provide a remote desktop. RustDesk combines its own desktop client with an optional self-hosted connection service.

Documentation and images

Official sources, image credits and review methods

The review was prepared on the project documentation. The installation and independent testing of the distribution within this material was not carried out. The rights to the interface and the names are reserved for the respective rights holders.