RustDesk Review

RustDesk is a remote-desktop application written in Rust, with a Flutter GUI on desktop (Sciter is deprecated). It runs on Windows, macOS, Linux, Android, and iOS, and offers file transfer, clipboard sync, international keyboard support, and TCP tunneling. The architecture is two server programs: hbbs is the ID and rendezvous server that clients register with and that attempts hole punching between peers, and hbbr is the relay used when a direct connection fails. The docs note that hole punching succeeds in most cases, so the relay is rarely used. You can use the public server, run your own, or write one using the rustdesk-server-demo project.

The OSS server is installed with a script, Docker Compose, or a .deb package, and all three install both hbbs and hbbr. The ports are TCP 21115, 21116 (plus UDP 21116), and 21118 for hbbs, including WebSocket, and TCP 21117 and 21119 for hbbr, with 21115 to 21117 being the minimum for signaling, relay, and NAT traversal. Behind an Nginx-style reverse proxy with WSS, 21118 and 21119 usually need not be exposed, and you can expose only TCP 443 and use WSS relay only, at the cost of losing direct peer-to-peer connections. Server Pro needs TCP 21114 for its API unless you serve it over HTTPS on 443. The pages we read do not give server hardware requirements. To build the client yourself you need a Rust and C++ toolchain, vcpkg with libvpx, libyuv, opus, and aom, and Flutter.

The README says it works out of the box with no configuration required, and the client behaves like other remote-desktop apps: enter an ID and password, then control or transfer files. Pointing clients at your own server means setting the ID server address and key in the client configuration. Server Pro adds a web console and API, OIDC, LDAP, 2FA, device management, access control, and multi-relay management. This section reflects the docs, pricing page, and repository; we did not run RustDesk ourselves.

• Self-hosted hbbs and hbbr servers, so sessions run on infrastructure you control
• Hole punching with relay fallback, and WSS support behind a reverse proxy
• File transfer, clipboard sync, TCP tunneling, and international keyboards
• Windows, macOS, Linux, Android, and iOS clients, plus a web client
• Pro: web console, OIDC, LDAP, 2FA, device groups, access control, and audit log
• Custom branding and a custom client generator on higher plans

• Real control over where remote sessions are routed, which proprietary services do not offer
• Direct peer-to-peer connections in most cases, so the relay carries little traffic
• Huge adoption and an active project, with about 126,000 stars
• Affordable management features through Server Pro for small teams

• You must run, secure, and update the servers, and expose several TCP and UDP ports
• Team management, SSO, and audit logging require the paid Server Pro, with support by email
• The README does not document known issues, and Wayland, VNC, and RDP appear only as topics rather than supported features with details
• Server Pro has no SaaS option and renews annually without auto-renewal, with a 14-day reminder
• AGPL-3.0 licensing applies to the open-source parts

The client and OSS server are free. RustDesk Server Pro is sold for self-hosting only (the pricing page says it is not a SaaS subscription) and billed annually: Individual is $11.88/month for 1 login user and 20 managed devices, Basic is $23.88/month for 10 users and 100 devices and adds OIDC (SSO), LDAP, cross-group access, and a custom client generator, and Customized plans start at $23.88/month plus $1.20 per extra user and $0.12 per extra device (Customized V2 adds $24 per extra concurrent connection). There is no non-profit or education discount, and trial licenses require contacting the vendor.

AnyDesk, TeamViewer, Splashtop, and Getscreen.me are commercial remote-access services that relay sessions through the vendor's infrastructure and charge per seat or device. RustDesk gives you similar remote control and lets you host the rendezvous and relay servers, so traffic and device metadata stay with you. The trade-off is operations and polish: you handle uptime and security, and enterprise support is lighter than at the big vendors.

• IT teams and managed service providers that want to host their own remote access
• Organizations with data-control or compliance requirements for remote sessions
• Individuals who want a free alternative to commercial remote-desktop apps
• Teams that want to white-label their remote-support client

• Teams that want a managed service with enterprise support
• Organizations that need SSO and audit logs but do not want to pay for Server Pro
• Anyone unwilling to maintain a public-facing server