Can RustDesk Scale to 200,000 Devices?

RustDesk internal telemetry recorded more than two million online endpoints on one public-server host with a 12-core CPU and 32 GB of RAM on July 7, 2026.

Two caveats define its scope. First, “online endpoints” means devices reported online at that moment, not two million simultaneous remote-control sessions. Second, it is an internal production observation, not an independently audited benchmark or a Server Pro guarantee — there is no public dashboard or downloadable dataset, and a Server Pro deployment carries different database writes, audit activity, console use, policy processing, and relay traffic. Treat the figure as first-party context for sizing, and validate any target against your own workload.

The short answer

Yes — 200,000 online devices is a credible planning target. The observation above sat an order of magnitude higher on a single 12-core, 32 GB host, so the ceiling is not the constraint; the real work is validating your specific workload, which the rest of this article breaks down.

In detail

Scale questions are among the most common we hear from IT teams migrating off TeamViewer or AnyDesk, especially those planning fleets in the tens or hundreds of thousands. The answer depends on how many devices stay online, how often their state changes, how many remote sessions run at once, and how much traffic uses the relay.

For a Server Pro rollout, validate the parts the public-server figure does not cover. Caching and database write performance matter as devices come and go. Relay bandwidth and CPU depend on the number, duration, resolution, and codec of simultaneous relayed sessions. Console queries, audit retention, device groups, policies, and integrations add load that endpoint presence alone does not measure. Capture your intended online count, connection churn, simultaneous direct and relayed sessions, database retention, and administrative activity in a representative load test.

High availability and load balancing deserve the same treatment. For very large fleets they are worth designing in, but the specifics — relay redundancy, database failover, and how sessions are distributed — should be validated with RustDesk rather than assumed as out-of-the-box defaults.

Then confirm licensing: at this scale RustDesk uses per-user and per-device models, so verify the exact tier for your fleet at rustdesk.com/pricing.

Who asks this

Fleet architects planning multi-year rollouts — at enterprises, large MSPs, and public-sector IT programs — put this near the top of their diligence list. These buyers are usually leaving a commercial tool for cost or data-sovereignty reasons and need confidence that a self-hosted platform will grow with them rather than hit a wall mid-contract.

Related questions

• Concurrent-connection limits and licensing for large device counts: see RustDesk pricing.
• Can I migrate an existing TeamViewer or AnyDesk fleet to RustDesk?

Planning a large-scale rollout? Reach out to the RustDesk team to size a self-hosted deployment for your device count, performance requirements, and growth timeline.