This comparison is for sysadmins, small MSPs and home-lab owners who want to self-host remote access and are deciding between MeshCentral and RustDesk with its own RustDesk Server. The short answer: MeshCentral is a web console plus agents, built for managing a fleet of machines from a browser. RustDesk is a desktop client with ID-based connections, built for quick support sessions, and the server behind it only brokers connections. Both are free and open source, and both are allowed for business use. We have not benchmarked either tool, so anything about speed, latency or load is marked “Not tested yet”.
MeshCentral vs RustDesk at a glance
| Question | MeshCentral | RustDesk (client + OSS server) |
|---|---|---|
| Licence | Free, open source, Apache-2.0 | Free, open source, AGPL-3.0; Server Pro is a separate commercial edition |
| Current version (our catalogue) | 1.2.6 (24 September 2026) | Client 1.4.9 (6 July 2026); OSS server 1.1.16 (20 July 2026) |
| Technician side | Any modern browser, nothing to install | RustDesk desktop or mobile client (plus a web client with extra server ports) |
| Managed side | MeshAgent service on Windows, Linux, macOS or FreeBSD | RustDesk client; Windows, macOS, Linux and Android can be controlled, iOS is controller only |
| Server platform | Node.js 20 or newer on Windows, Linux, macOS or FreeBSD, or Docker | Linux (amd64, arm64, armv7, i386), Docker or Windows x64; no macOS server build |
| Management | Device groups, users and user groups, per-device rights, two-factor authentication, events log | OSS: connection brokering only. Web console, users, access control and audit logs need Server Pro |
| Extras | Terminal, file manager, power actions, Intel AMT, MeshCentral Router for TCP tunnelling | File transfer, TCP tunnelling, terminal, privacy mode on supported Windows hosts |
| Speed and latency | Not tested yet | Not tested yet |
The core difference: console versus client
With MeshCentral you open your own server in a browser, log in, pick a device and use its Desktop, Terminal or Files tab. The server holds the device list, the groups and the permissions, and every managed machine runs the MeshAgent as a service. Nothing is installed on the technician side, which is convenient when you work from a borrowed laptop.
With RustDesk you install the same client on both ends. A machine shows a numeric ID, and you connect to that ID with a one-time or permanent password. A self-hosted server only helps clients find each other (hbbs) and relays traffic when a direct path is not possible (hbbr). It does not keep an inventory of your fleet. That is the job of Server Pro, which is commercial.
In practice this decides the choice. If you think in terms of “my office PCs, grouped by site, with a few technicians who each see only some of them”, MeshCentral already has that model. If you think in terms of “a user calls, reads out a number, I fix the problem”, RustDesk is closer to how the work actually flows.
Setup effort and ports
MeshCentral is installed with npm (npm install meshcentral, not as root), or from the official Docker images. It starts in LAN-only mode, where agents find the server by multicast. For laptops outside the office you give the server a DNS name in meshcentral-data/config.json, usually with Let’s Encrypt, and reissue the agent installers, because agents carry the server address. The usual ports are 443 for the web UI and agents and 80 for redirects and certificate issuing, plus 4433 if you use Intel AMT CIRA. Our self-hosted remote access guide covers where this fits next to other options.
RustDesk Server is two small daemons. The official documentation lists TCP 21115 (NAT type test), TCP and UDP 21116 (registration and hole punching), TCP 21117 (relay), TCP 21118 and 21119 (WebSocket for the web client) and TCP 21114 (HTTP API, Pro only). Ports 21115 to 21117 are the minimum. Clients then need your host name and the server’s public key, which you can export as a config string and push to every machine during deployment.
| Setup step | MeshCentral | RustDesk Server |
|---|---|---|
| Server software | Node.js and npm, or Docker | Docker Compose or Linux packages |
| First secret | First account becomes administrator; create it before the server is reachable from the internet | Key pair generated on first start; clients need the public key |
| Public exposure | DNS name, TCP 443 and 80 | TCP 21115 to 21117 and UDP 21116 |
| Client rollout | Download agent installer per device group from your server | Install client, apply config string with the server address and key |
| Data to back up | meshcentral-data folder and the database | Server data directory with the key pair |
Who can do what
MeshCentral separates users, user groups and device groups, so you can give one technician full control of one group and view-only rights elsewhere. It also supports two-factor authentication and a local events log. This is the main reason it appears in MSP-style setups.
The free RustDesk server has no accounts at all: anyone who knows an ID and its password, and who can reach your server, can connect. Access control, audit logs, LDAP or OIDC login and a web console are listed by the project as Server Pro features. If you need to prove who connected to what, plan for Server Pro or pair RustDesk with other controls. Whichever tool you choose, work through the remote access security checklist.
Platforms and special cases
- Intel AMT: MeshCentral supports Intel AMT out-of-band management, so you can reach vPro machines whose operating system is down. RustDesk has nothing comparable.
- Phones: RustDesk has Android and iOS apps; the iOS app can only control other devices. For MeshCentral the technician console is a browser; mobile use is Not tested yet.
- Tunnelling RDP or SSH: both can forward TCP ports through the remote session (MeshCentral Router, RustDesk TCP tunnelling), so you do not need to expose RDP.
- Wayland and macOS permissions: RustDesk is more predictable on X11 Linux sessions, and on macOS it needs Accessibility and Screen Recording permissions. These are client-side details to plan for when you roll it out.
- Disconnected servers: MeshCentral downloads its agent installers from GitHub on first start (about 120 MiB). A server without internet access needs them copied in by hand.
Limitations of each
MeshCentral: the configuration file has many options and few guard rails, the web interface is functional rather than polished, releases are frequent, and there is no vendor support contract. Remote desktop is meant for support work, not graphics-heavy use.
RustDesk: the open-source server does not manage users or devices, public servers can be busy, there is no built-in ticketing or session recording workflow, and the client is also abused by scammers, so users should never give an ID and password to an unsolicited caller.
For both, you own the server: TLS, backups, updates and uptime are your responsibility. We have not tested how many devices a given VPS can carry. Not tested yet.
How to choose
- Do you need an inventory and per-technician rights? Yes: MeshCentral. No: either works.
- Do users call you for ad-hoc help? RustDesk’s ID and one-time password flow is simpler, and on Windows it can run without installation as a temporary session.
- Do you need to reach unattended servers or kiosks? Both can do it; MeshCentral adds device groups and Intel AMT, RustDesk adds a simple permanent-password service.
- How much do you want to harden? RustDesk Server exposes only its relay and registration ports; MeshCentral exposes a full web application, so keep it patched and protect it with two-factor authentication.
- Mixed fleet? Many teams run MeshCentral for the managed fleet and RustDesk for ad-hoc help. Both are free, so you can pilot them side by side. If the browser-only gateway model appeals, look at Apache Guacamole too.
For a wider comparison of free tools, see best free remote desktop software.
FAQ
MeshCentral vs RustDesk: which is better?
Neither wins in general. MeshCentral is better for managing groups of machines from a browser with per-user rights. RustDesk is better for quick ID-based support sessions with a desktop client.
Is MeshCentral or RustDesk free for business use?
Yes for both. MeshCentral is Apache-2.0 and RustDesk, including the open-source server, is AGPL-3.0. Only RustDesk Server Pro is a separate commercial product.
Which one should I self-host?
Both can be self-hosted. MeshCentral runs on Node.js (or Docker) and needs ports 443 and 80. RustDesk Server runs two small services and needs the 21115 to 21117 range. Pick based on the management model described above, not on server size.
MeshCentral vs RustDesk vs Guacamole?
Guacamole is a clientless gateway to RDP, VNC and SSH servers that already exist; it does not install an agent. MeshCentral installs an agent and manages devices. RustDesk is a peer-to-peer style client with optional servers.
Is RustDesk or MeshCentral faster?
We have not measured it, so we will not guess. Not tested yet. Results depend on the route, relay location and settings such as codec and quality, so try both on the same pair of machines.
Can I use RustDesk without a server?
Yes. By default the client uses the project’s public servers, and direct IP access works on a LAN or over a VPN. For business use, running your own server is the safer choice.
Last updated: 26 October 2026 · CtrlRemote editorial team. Licence, version and platform details are checked against each developer's official documentation.