RustDesk Review for MSPs and IT Teams
RustDesk reviewed for MSPs and IT teams: Server Pro prices as of October 2026, the 2026 CVEs and what they mean, a TeamViewer and AnyDesk comparison, and a hardening checklist.
Updated: October 2026
RustDesk keeps coming up as the free, open-source answer to TeamViewer and AnyDesk pricing, from MSP threads to in-house IT teams tired of per-seat licenses. It holds up well for anyone who can self-host and harden a server, and less well for support that has to produce audit trails. This review shows where that line sits, and what it takes to run RustDesk safely on company and client endpoints.
TL;DR
- What it is. Free, open-source remote desktop written in Rust, self-hostable across Windows, macOS, Linux, mobile and web.
- Cost. The self-hosted server is free; RustDesk Server Pro starts at $11.88 a month, billed annually, for a web console, address book and audit log.
- Security. End-to-end encrypted with NaCl, but no SOC 2, no independent audit, and defaults that need hardening. A batch of CVEs disclosed in March 2026 is a reason to keep every client on the current release.
- MSP fit. Strong for cost-conscious shops willing to self-host, weak for compliance-bound client support.
- IT team fit. Strong for unattended access to servers and empty PCs, which Quick Assist and Intune Remote Help don't cover. Single sign-on through OIDC or LDAP starts on Server Pro Basic.
What RustDesk Is
RustDesk is a remote access tool that lets you control another machine over the internet, the same core job as TeamViewer, AnyDesk, or a VNC session. You install a client, get a device ID and a password, and connect. The difference that pulls MSPs and IT teams in is the license and the hosting model. RustDesk is open source under AGPL-3.0, the client is free, and you can run the entire connection infrastructure on your own server instead of routing sessions through a vendor's cloud.
Purslane Tech Pte. Ltd., a company established in Singapore, develops it, and the code is public on RustDesk's GitHub, where the client repository has more than 127,000 stars. Version 1.5.0, released on 30 September 2026, is current as of October 2026.
The project is built in Rust with a Flutter UI, which is part of why it feels fast and light on resources. It runs on Windows, macOS, Linux, iOS, Android, the web, and Raspberry Pi, so a mixed client fleet isn't a problem. For a technician who needs to jump onto a workstation, fix a driver, and drop off, the free client does that with no account and no license check.
That breadth is why RustDesk dominates "open source remote desktop" and "self hosted remote desktop" searches. The harder question is whether the free version scales to support across a team, a company or a client base without creating a second job for whoever owns your stack.
Self-Hosting the RustDesk Server
The reason RustDesk gets recommended for self-hosting is its server architecture. Two components do the work: the ID/rendezvous server (hbbs) that registers devices and brokers connections, and the relay server (hbbr) that carries traffic when a direct peer-to-peer connection can't be established. Both ship in the free rustdesk-server package. Point your clients at your server's address, and your remote sessions stop touching RustDesk's public infrastructure.
Setup is straightforward if you're comfortable on a Linux box. The common path is a small VPS, Docker, and a few open ports (21115 through 21119 for the standard stack). Plenty of MSPs run it on Ubuntu, and "install rustdesk ubuntu" is a well-trodden search with solid community write-ups behind it. A basic rustdesk server setup can be live in under an hour for someone who's done it before.
Lawrence Systems walks through a self-hosted install, from the server to pointing clients at it:
The catch is what the free server doesn't give you. The OSS rustdesk-server is a relay and ID broker, not a management console. There's no central web dashboard, no user accounts, no address book sync, no device grouping, and no audit log. You get connectivity. Everything that turns connectivity into a managed service lives in RustDesk Server Pro, the paid tier.
For context on where a standalone remote access tool sits versus a full management platform, it helps to be clear on what an RMM does beyond remote control. RustDesk is the remote-control slice only. Monitoring, patching, scripting, and alerting aren't in scope.
Core Features That Matter for Remote Support
For day-to-day remote support, RustDesk covers the fundamentals. Unattended access lets you set a permanent password so you can connect without someone at the other end, the baseline for supporting servers and unmanned endpoints. File transfer works in both directions. There's a text chat for talking a user through something mid-session. NAT traversal handles most home and office networks without manual port forwarding, and TCP tunneling lets you reach services behind the remote machine.
Newer builds added two-factor authentication and one-time password support, which matters for any tool you're exposing to client environments. That closes a gap reviewers flagged for years, and version 1.4.7 added brute-force protection for one-time passwords.
Where the free version thins out is management. The address book, device groups, granular user permissions, wake-on-LAN, and session recording are largely gated behind Server Pro. For a single tech, the free feature set is enough. For a team supporting many clients, those missing pieces keep remote access organized and auditable, and they're exactly what you'll end up paying for. Tekpon and SourceForge reviewers echo the same pattern: easy to start, capable on the basics, lighter than commercial tools once you need centralized control.
RustDesk Pricing: Free OSS vs Server Pro
RustDesk's pricing is its strongest argument and the source of the most confusion. The open-source self-hosted server is free, full stop. The paid product is RustDesk Server Pro, which adds the management layer to your own hosting. Plans are billed annually with no monthly option, and extra capacity costs $1.20 per user and $0.12 per device, as listed in October 2026.
| Plan | Price (billed annually) | Users | Devices | Notes |
|---|---|---|---|---|
| OSS self-hosted server | Free | Unlimited | Unlimited | Relay + ID broker only, no console |
| Server Pro Individual | $11.88/month | 1 | Up to 20 | Web console, address book, audit log, 2FA |
| Server Pro Basic | $23.88/month | Up to 10 | Up to 100 | Adds OIDC and LDAP sign-in, custom client generator |
| Customized | From $23.88/month | Basic plus $1.20 per extra user | Basic plus $0.12 per extra device | Scale beyond Basic limits |
| Customized V2 | From $23.88/month | Set per order | Set per order | Limited concurrent connections at $24 per extra connection; devices over the limit stay active |
RustDesk is one of the cheapest credible remote access options on the market, and even the Pro tiers undercut per-seat commercial licensing by a wide margin. A team managing up to 100 devices pays $23.88/month, or $286.56 a year, for Pro Basic plus the cost of a small VPS. The browser-based web client comes only on licenses where 10 times the users plus the devices adds up to 400 or more, such as 10 users and 300 devices.
What the price tag leaves out is labor. You host the server, patch it, monitor uptime, and own the whole thing when a connection breaks at 9 a.m. Monday. Free software, paid time. For a quick read on how standalone tool costs stack up against consolidated platforms, the breakdown in this IT operations tooling comparison is a useful reference point.
Is RustDesk Safe? The Security Reality
Short answer: yes for internal and client support, when you self-host the server, keep every client on the current release and harden the defaults below. It's a harder sell where a client or an auditor asks for a SOC 2 report.
RustDesk encrypts sessions end-to-end using NaCl (libsodium), the same well-regarded cryptographic library behind a lot of modern secure software. When you self-host, session data stays on infrastructure you control rather than a third-party cloud, a stronger privacy posture than commercial tools that broker every session through their own servers.
The qualifiers are where MSPs and IT teams need to pay attention. By default, an unhardened self-hosted server can store the public key in cleartext, and a custom-built client can connect to a server that hasn't been locked down. That's fine for a hobbyist and a real problem for a team touching client or company endpoints; the defaults assume you know what you're doing.
Then there's the antivirus friction. Microsoft Defender, ESET, and other AV engines routinely flag RustDesk binaries as potentially unwanted programs. It isn't malware detection; remote access tools get abused by scammers, so AV vendors treat them with suspicion. For an MSP, that means whitelisting RustDesk across every client AV policy, and re-whitelisting when a new version trips a fresh signature. Multiply that by your client count and it's recurring overhead. An in-house team has one policy to maintain, but the re-whitelisting after each release still lands on someone. The RealVNC writeup on RustDesk safety covers the same default-configuration and AV concerns.
Two more items belong on the risk ledger. RustDesk has no SOC 2 report and no independent third-party security audit, which is a hard stop for clients in regulated industries that require vendor compliance documentation. And while the developer is established in Singapore, community threads keep raising the project's links to China, which some organizations treat as a supply-chain and governance question, fair or not. None of this makes RustDesk unsafe for internal or low-stakes use. It does make it a harder sell for client-facing support where someone will eventually ask for an audit trail you can't produce.
RustDesk CVEs in 2026
On 5 March 2026, researcher Erez Kalman published findings against RustDesk Client up to 1.4.5 and Server Pro up to 1.7.5, with proof-of-concept code. They became a batch of CVEs, and the Western Australian government's security operations centre rated six of them critical in an advisory four days later.
The record moved after that. An update to the write-up on 22 June 2026 withdrew the insecure TLS fallback finding, limited the deep-link password and config findings to mobile options that are off by default, and lowered CVE-2026-30783 to medium. RustDesk 1.4.7, released on 2 June 2026, stores new permanent passwords so they can't be recovered, limits one-time-password guessing and fixes a file-transfer path traversal.
| CVE | What it covers | Status, October 2026 |
|---|---|---|
| CVE-2026-30783 | The client can drop its API channel and ignore admin commands and access policies | Lowered to medium, CVSS 4.0 score 4.8 |
| CVE-2026-30784 | A related claim about a rogue signaling server | Withdrawn |
| CVE-2026-30789 | The login handshake allows offline password guessing | Kept at medium, 5.7 |
| CVE-2026-30790 | A captured login can be replayed against the server | Rejected |
| CVE-2026-58056 | A file-transfer-only session can send keyboard and mouse input and capture the screen | High, CVSS 4.0 score 7.2. NVD listed no fixed version when it was published on 28 June 2026 |
For all of them, the response starts the same way: keep clients on the current release, run the API server on HTTPS, and leave the allow-* options off. For CVE-2026-58056, also limit who gets file-transfer access until the release notes name a fix.
RustDesk for MSPs and IT Teams: Where It Fits
RustDesk was built as a remote desktop tool, not as a multi-tenant MSP platform or an endpoint manager. An MSP feels that in client separation, and an in-house team feels it in deployment and sign-in.
For MSPs: Client Separation and the Rest of the Stack
The free OSS version has no real client separation. Every device sits in one flat space with no native way to wall off Client A's endpoints from Client B's, no per-client permission boundaries, and no tenant-aware audit. Server Pro adds device groups and permissions, which gets you closer, but you're building tenancy out of grouping features rather than a system designed for it. For a shop with strict client isolation needs, that's a real limitation.
There's also no native PSA or RMM. RustDesk doesn't tie a session to a ticket, doesn't log time against a client, doesn't push patches, and doesn't monitor anything. It's the remote-control hop and nothing else, so an MSP running it adds a separate RMM and PSA: another tool to maintain, another set of credentials, another thing that breaks on its own. A bundled remote access feature inside an RMM, like the kind covered in this Datto RMM review, trades RustDesk's price for tighter integration with the rest of the support workflow.
This is the structural trade-off behind tool sprawl: RustDesk for remote access, something else for RMM, something else for PSA, each with its own login, billing, and failure mode. The alternative is consolidation. OpenFrame from Flamingo, open and AI-native infrastructure for IT and security, puts remote access, RMM and a native PSA in one system with no vendor lock-in, so the remote session, the ticket and the device record live in the same place instead of three. It costs $1 per device per month with 10M AI tokens included, after a 14-day free trial. Which is right depends on whether you're optimizing for a low software bill or for fewer moving parts.
For In-House IT Teams: Unattended Access and Single Sign-On
An in-house team supports one company, so client separation isn't the problem. The questions are how RustDesk gets onto every machine, how technicians sign in, and what it adds to the tools Microsoft already includes.
Deployment is the easy part. RustDesk ships an MSI with silent-install options, so it rolls out through Intune, Group Policy or any MSI-based deployment tool, and the custom client generator on Server Pro Basic bakes your server address and key into the installer. Basic is also the tier with OIDC and LDAP, so technicians sign in through Entra ID or another identity provider instead of shared passwords.
Then compare it with what you own. Windows Quick Assist is free, Intune Remote Help costs $3.50 per user per month, and Microsoft started folding Remote Help into Microsoft 365 E3 and E5 in July 2026. On Windows, both need someone at the keyboard. RustDesk's case for an IT team is unattended access to servers, kiosks and empty office PCs, through a relay you host yourself. Our Intune review covers where Remote Help stops.
Hardening RustDesk for Client-Facing Support
If RustDesk is going onto client or company endpoints, the defaults aren't enough. The community consensus across r/sysadmin and r/selfhosted threads is consistent: it's safe when configured properly, risky when run as-is. Before rollout, work through the basics.
- Lock the server to your own key. Run a self-hosted server with an encrypted key configuration so arbitrary custom clients can't register against it, and rotate that key if it's ever exposed.
- Force 2FA and strong permanent passwords. Enable two-factor authentication, require one-time passwords for attended sessions, and never ship a default or reused unattended password to client endpoints.
- Whitelist deliberately and document it. Add RustDesk to each client's AV and EDR allowlist by hash and path, keep a record of which version you've cleared, and re-verify after every update so a new binary doesn't silently break access.
- Stay on the current release. Version 1.4.7 fixed the one-time-password guessing and file-transfer path traversal issues, and 1.5.0 is current as of October 2026. Keep the allow-* options, such as the deep-link password and insecure TLS fallback, switched off, and run the API server on HTTPS.
That's the floor, not the ceiling. You'll also want firewall rules limiting who can reach the server and a logging setup (Pro) to answer "who connected and when." None of it is exotic, but all of it is work a managed commercial tool does for you out of the box.
How RustDesk Compares
Set against TeamViewer and AnyDesk, RustDesk trades polish, session recording, and audit artifacts for self-hosting, data ownership, and a much lower bill. Set against a consolidated platform like OpenFrame, which pairs native PSA and RMM with remote access, RustDesk covers one job rather than the stack, so the comparison is really about how many tools you want to run.
For the full side-by-side across MeshCentral, TacticalRMM, ScreenConnect, AnyDesk, TeamViewer, and Splashtop, see our RustDesk alternatives comparison.
RustDesk vs TeamViewer vs AnyDesk
As a TeamViewer or AnyDesk alternative, RustDesk wins on license and hosting and gives up compliance paperwork. Here's how the three compare as of October 2026.
| RustDesk | TeamViewer | AnyDesk | |
|---|---|---|---|
| License | Open source, AGPL-3.0 | Proprietary | Proprietary |
| Where sessions connect | Your own server, or RustDesk's public servers | TeamViewer's cloud | AnyDesk's cloud, or your own appliance on the Ultimate plan |
| Free use | Any use, including business | Personal, non-commercial use only | Personal use only |
| Paid plans | Server Pro from $11.88/month, billed annually | From about $24.90/month, billed annually | Per-user plans; Ultimate is quote-only |
| Security events | March 2026 CVE batch, covered above | June 2024 breach of its corporate network, which TeamViewer said didn't reach the product | January 2024 breach of production systems, followed by a code-signing certificate rotation |
| Fits | Teams that can self-host, harden and patch | Mixed and legacy device estates | Weak connections and aging hardware |
TeamViewer's tiers cap concurrent sessions, which changes the math for a team of several technicians. Our TeamViewer review walks through each plan.
How Users Rate RustDesk
On the review platforms, RustDesk sits middling. It holds a 3.1 out of 5 on Trustpilot across 9 reviews and 2.3 out of 5 on SourceForge from 3 reviews, as of October 2026. We found no G2 or Capterra product listing in June 2026, which is common for free open-source tools that don't run vendor review campaigns. The small sample sizes make those scores signal-light, so weight community sentiment from r/msp and r/sysadmin over the star averages.
The self-hosted shortlist, argued by people running these tools in production:
Who RustDesk Fits and Who Should Pass
RustDesk fits the cost-conscious, technically capable MSP or IT team that's comfortable on Linux, willing to self-host and harden, and working where strict compliance documentation isn't a contract or audit requirement. For a solo operator, a small shop or a lean IT department that wants to stop paying per-seat licensing and is happy to own the infrastructure, it's one of the lowest-cost options in the category. The free client plus a $23.88/month Pro server covers a lot of ground.
Who should pass: any MSP or IT team that needs SOC 2 or audit artifacts for client contracts or auditors, teams without the Linux skills or time to run and harden a server, and shops that want remote access wired into ticketing, time tracking, and monitoring without maintaining a separate tool to glue it together. If the hidden labor of hosting, whitelisting, and tenancy workarounds costs more than you're saving on licenses, the math stops working.
RustDesk is a focused tool, and the license costs nothing. Free to download and free to operate are different numbers. For the right MSP or IT team it's a smart line item. For the wrong one it's a part-time job wearing a software license.

Content Marketing Lead
Ohayo! I run content, SEO, social, and community at Flamingo. Before IT, I worked as a correspondent for Ukraine's Public Broadcasting Company and have a Master's in journalism.
Related Content
Frequently Asked Questions
/blog/rustdesk-review