rustdesk/rustdesk

RustDesk is worth a look if you already run your own server or are willing to, and you want remote access to machines you control rather than another cloud dependency.

The problem

You need to get onto another machine — a parent's laptop, an office workstation, a headless box — and the usual path is installing a commercial client, creating an account on someone else's relay, and accepting whatever the vendor changes about it. That works, but the session runs through infrastructure you don't control, and every helper and every host needs the same client. RustDesk changes the middle step: point the client at a relay you run instead of the vendor's, and the same client handles screen sharing, input and file transfer. The result is a familiar remote-desktop workflow where the connection broker is yours.

What's different

The project is written in Rust and ships clients for Windows, Linux, macOS, Android and iOS, with desktop GUI builds on Flutter (the older Sciter GUI is marked deprecated). The README's build path is heavyweight by design: Rust plus a C++ toolchain, vcpkg for libvpx, libyuv, opus and aom, and platform packages for GTK, xcb, PulseAudio and GStreamer. That dependency list tells you what the client actually does — video encoding, audio, and input injection — rather than wrapping an existing screen-sharing library.

Self-hosting is the point. A relay you operate removes the third-party account from the loop and, per the README, is an alternative to TeamViewer. The trade-off is that you now own uptime and connectivity for your relay; an unattended host is only reachable if that service and its network path stay healthy. There is also a real licensing wrinkle: AGPL-3.0 covers the project, but the deprecated Sciter GUI is proprietary and was a recurring question in the 2022 HN thread, with the README and commenters pointing at the Flutter build as the replacement GUI licensing thread. If you redistribute binaries, check which GUI your build uses.

Who should try it

Good fit: someone with a small fleet — a few family machines or office desktops — who already runs a VPS and wants remote support without per-seat licensing. The self-hosted relay makes the project most useful in exactly that setup.

Poor fit: anyone who wants zero-infrastructure remote access and expects agents to update themselves. An HN commenter in February 2025 noted there was no auto-update, that manual updates still required starting the service, and that this makes broad deployment awkward auto-update complaint. A one-off personal connection with a vendor relay may still be simpler than operating your own.

Requirements and limitations

Building from source means a full desktop development environment: vcpkg-managed multimedia libraries, CMake, and the platform GUI/audio packages listed per distribution. The README also tells Sciter-built desktop users to download the Sciter dynamic library themselves, and the GUI situation is split between Flutter and deprecated Sciter project instructions. Official build documentation and a Docker path exist beyond the raw steps build docs.

On the operational side, running your own relay is ongoing work, not a one-time setup, and updates are something you arrange for hosts. Reports about screen scaling across different DPI settings suggest mixed-resolution fleets deserve a test before you commit scaling report. Performance claims against TeamViewer or NoMachine are not established here; comments asking for comparisons went largely unanswered in the supplied excerpts performance question.

HotRepo's take

HotRepo recorded 120,486 stars on 2026-08-14 and 127,102 on 2026-10-26, both daily-board observations project repository; the three sampled dates are too sparse to judge a trend. The project has existed since 2020-09-28, so it is not new — the dateable signal is simply interest on three board days. Before adopting it for a fleet, verify the update and relay-failover story for the exact build you plan to distribute.