Remote desktop without surrendering the server
RustDesk is easy to understand because it solves a familiar problem. Install it on two devices, enter the remote device ID and password, then view and control the screen. Sessions support keyboard and mouse input, clipboard sharing, file transfer, audio, multiple displays, and TCP tunneling. Direct connections are attempted first; a relay carries traffic when network address translation or firewall conditions prevent peer-to-peer access.
The distinguishing feature is control over that connection layer. You can use RustDesk's public rendezvous and relay servers with no setup, or point clients at your own RustDesk Server. The client is AGPL 3.0, and the separate free server supplies the two essential services: hbbs for IDs, rendezvous, and signaling, and hbbr for relayed traffic. This is a more complete proposition than a VNC viewer because discovery, traversal, relaying, and cross-platform clients arrive as one system.
Release 1.4.9 provides packages for Windows, Ubuntu, macOS, Android, Flatpak, iOS, and more Linux formats. F-Droid and Flathub are also linked. Downloading a binary is far easier than building from source.
Self-hosting is small, but not automatic
The recommended server path is Docker Compose. Two containers share persistent data and typically use host networking on Linux. A basic server needs little CPU or memory, so a small VPS or Raspberry Pi can be enough. After first boot, the administrator gives clients the hbbs address and the generated public key. The relay address can usually be inferred.
Networking is the real setup cost. The documentation lists TCP ports 21115 through 21119 for various services and UDP 21116 for ID registration and heartbeat. The relay uses 21117, while web clients need 21118 and 21119. If direct connection fails, screen traffic crosses your relay, so the low server compute requirement does not mean negligible network cost. The docs estimate a broad range depending on resolution and screen changes, making bandwidth and egress the capacity question to watch.
There is also a concrete proxy warning. The WebSocket services trust X-Real-IP and X-Forwarded-For when deciding the client address, but do not validate those headers. If those ports are reachable directly, a caller can spoof an address, undermine IP-based blocking or rate limits, and falsify logs. The official advice is to expose them only through a reverse proxy that sets the headers and block direct access, or keep them closed when the web client is unnecessary.
Client configuration scales acceptably for a small deployment. Settings can be entered manually, exported and imported, or applied with a command-line config string. The documentation includes PowerShell, batch, MSI, macOS, and Linux deployment routes. Larger organizations should notice where the free server stops: the web console, API, OIDC, LDAP, 2FA, device management, and custom client generator are positioned as Server Pro features. The free edition controls the transport; it is not a full remote-monitoring and management suite.
The client is mature, not uniform across platforms
RustDesk's hardest problems live at operating-system boundaries. Screen capture, input injection, display scaling, audio, clipboard access, login screens, and permissions behave differently on every platform. The open issue list shows that breadth clearly.
Wayland users face the most visible caveat. A current 1.4.9 report documents pointer coordinates being scaled against the full XWayland root instead of the captured monitor, causing large drift on a rotated multi-monitor setup. Other current reports cover a smaller resolution being encoded into an old canvas, a missing screen picker that presents two monitors as one, and a new DRM capture path that still cannot serve a Wayland login screen. These are specific configurations, not proof that all Linux sessions fail. They are enough to require a real test of each desktop environment, display arrangement, scaling factor, and unattended-login scenario before a rollout.
The iPad story also needs qualification. One 1.4.9 report says Magic Keyboard two-finger scrolling works briefly, then moves the remote canvas rather than the macOS content. Another long-running report describes mixed touch and mouse behavior with an external keyboard and trackpad. A tablet can be a useful emergency client, but buyers expecting laptop-like input should test their gestures and pointer mode.
Building it yourself is the difficult route
The main README's source instructions lag behind the easiest user path. It says the desktop can use Flutter or deprecated Sciter, then teaches Sciter because it is easier. Building requires Rust and C++ environments, vcpkg, video and audio libraries, platform development packages, recursive submodules, and a separately downloaded Sciter library for that route. The Docker builder reduces host variation but still needs source caches and produces local artifacts rather than an installer pipeline.
Contributors working on the current Flutter client should follow the CI workflow and dedicated build documentation rather than assume cargo run reproduces an official release. That complexity is understandable for software spanning capture, codecs, input, services, mobile apps, and several operating systems. It does lower the score for anyone who needs audited in-house builds.
Active enough to trust, busy enough to test
The repository was pushed on August 8, 2026, and release 1.4.9 arrived on July 6. Issues were updated through August 7, while recent commits and release notes cover audits, file transfer, Wayland, Android, FUSE, installers, and clipboard behavior. GitHub's combined open count includes issues and pull requests; the separate open issue search returned 78 reports. RustDesk is not coasting on its large star count.
For most personal and small-team use, the recommendation is straightforward: try the official client, then add the free server if controlling the rendezvous and relay layer matters. For fleets, compare Server Pro with MeshCentral or an existing RMM before writing your own administration layer. On Linux Wayland and iPad, require a device-specific acceptance test. RustDesk offers rare freedom in a category dominated by accounts and subscriptions, but remote input is too environment-sensitive to buy on reputation alone.