mirror of
https://github.com/rustdesk/doc.rustdesk.com.git
synced 2026-07-12 17:53:45 +00:00
fix review
This commit is contained in:
rustdesk
+11
@@ -22,3 +22,14 @@ yarn-error.log*
|
||||
public/
|
||||
.DS_Store
|
||||
hugo.toml
|
||||
|
||||
# local agent tooling
|
||||
.agent/
|
||||
.agents/
|
||||
.claude/
|
||||
.omx/
|
||||
v3/.agent/
|
||||
v3/.agents/
|
||||
v3/.claude/
|
||||
v3/.omx/
|
||||
v3/docs/superpowers/
|
||||
|
||||
@@ -100,7 +100,9 @@ The `Individual` plan does not have this feature.
|
||||
4. Click `OK`.
|
||||
|
||||
## Viewing Logs
|
||||
On the left hand side click on `Logs`.
|
||||
On the left hand side click on `Logs`. The console lists the connection, file-transfer, alarm, and console-operation (audit) logs; you can also query and export them through the `audits.py` API.
|
||||
|
||||
Server Pro includes **built-in audit-log rotation**, so these audit logs are bounded rather than growing indefinitely — helpful for storage-limitation and data-retention requirements.
|
||||
|
||||
## Setup Emails
|
||||
Gmail in this example
|
||||
|
||||
+8
-1
@@ -21,4 +21,11 @@ pnpm-debug.log*
|
||||
|
||||
pnpm-lock.yaml
|
||||
|
||||
.astro
|
||||
.astro
|
||||
|
||||
# local agent tooling
|
||||
.agent/
|
||||
.agents/
|
||||
.claude/
|
||||
.omx/
|
||||
docs/superpowers/
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-06T12:17:00Z
|
||||
lang: en
|
||||
translationKey: anydesk-alternative-self-hosted
|
||||
draft: false
|
||||
@@ -13,6 +13,18 @@ tags:
|
||||
- alternative
|
||||
- self-hosting
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Is RustDesk a good alternative to AnyDesk?'
|
||||
answer: "RustDesk is open-source and self-hosted: the ID/rendezvous server, relay, console, and stored data run on your own infrastructure, and the core client is AGPL so you can audit what it does. It's a genuinely different model than AnyDesk's cloud service, and whether it fits depends on whether your team can run a server."
|
||||
- question: 'Can I self-host an AnyDesk alternative?'
|
||||
answer: 'Yes. RustDesk Server Pro is self-hosted by design, and you can also run the free open-source community server indefinitely at no cost. Someone on your side has to provision the host, open ports, set up TLS, and patch it over time.'
|
||||
- question: 'Is RustDesk cheaper than AnyDesk?'
|
||||
answer: 'RustDesk licensing is per login-user plus per managed-device, with unlimited concurrent connections on standard plans and a defined allowance on Customized V2. Self-hosting is not guaranteed to have the lowest sticker price in every configuration, so model both products against the same user, device, concurrency, feature, and infrastructure requirements; see rustdesk.com/pricing.'
|
||||
- question: 'Does RustDesk support SSO and access control?'
|
||||
answer: 'Yes. RustDesk Pro includes a self-hosted web console, device groups plus a shared address book for per-user access control, and LDAP/SSO (OIDC) available from the Basic plan and up.'
|
||||
- question: 'Can I try RustDesk without a sales call?'
|
||||
answer: 'Yes. You can self-host the free open-source community server today with no cost or expiry, watch a video demo on the RustDesk YouTube channel, or email sales@rustdesk.com to ask about current Pro evaluation terms.'
|
||||
|
||||
metadata:
|
||||
description: "Looking for an AnyDesk alternative? Compare RustDesk's open-source, self-hosted model, licensing, and operational trade-offs."
|
||||
keywords: 'AnyDesk alternative, self-hosted AnyDesk alternative, open source AnyDesk alternative, AnyDesk replacement'
|
||||
@@ -22,9 +34,9 @@ metadata:
|
||||
|
||||
Most people who look for an AnyDesk alternative aren't chasing a shinier feature list. They're reacting to two things: the bill going up, and the feeling that they no longer control their own remote-access setup.
|
||||
|
||||
Buyers typically start this search after reviewing renewal costs, vendor dependence, or security requirements. AnyDesk publicly disclosed a security incident in early 2024; evaluate that event through public reporting rather than private customer correspondence.
|
||||
Buyers typically start this search after reviewing renewal costs, vendor dependence, or security requirements. AnyDesk publicly disclosed a security incident in early 2024; evaluate that event through public reporting and AnyDesk's own disclosure.
|
||||
|
||||
If that's roughly where you are, this page is for you. We'll be direct: RustDesk is a genuinely different model, and it isn't for everyone. Here's the honest version.
|
||||
If that's roughly where you are, this page is for you. RustDesk takes a genuinely different approach from AnyDesk's cloud — you host it, so the data and the access stay yours — and this lays out exactly how, and where it fits best.
|
||||
|
||||
## The core difference: rent access, or own it
|
||||
|
||||
@@ -41,7 +53,7 @@ And **RustDesk's core is [open source (AGPL)](/blog/case-for-open-source-remote-
|
||||
| Hosting | Vendor cloud | Self-hosted (your server) |
|
||||
| Source code | Proprietary | Open source (AGPL) |
|
||||
| Where your data lives | Vendor infrastructure | Infrastructure you control |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Plan-dependent | Unlimited on standard plans; limited on Customized V2 |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Plan-dependent | Unlimited on standard plans; limited on [Customized V2](https://rustdesk.com/pricing#custom2) |
|
||||
| Licensing model | Per-seat cloud subscription | [Per login-user + per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) |
|
||||
| Try without sales call | Varies | Free server today, or Pro trial on request |
|
||||
|
||||
@@ -63,13 +75,9 @@ Self-hosting doesn't mean going without tooling. RustDesk Pro gives you a **[sel
|
||||
|
||||
And it scales: RustDesk publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices) for teams evaluating bigger environments.
|
||||
|
||||
## The honest caveat: someone has to run the server
|
||||
## Your data, on your own server
|
||||
|
||||
Here's the trade-off we won't hide. Self-hosting means **someone on your side runs the server** — you provision a host, open ports, set up TLS, and patch it over time. It's not hard, but it isn't zero.
|
||||
|
||||
If your team wants a fully managed SaaS with no server to maintain, RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-desktop-software) and is not that. Commercial rates can still change at renewal; the structural benefit is control of the server-side services, paired with the responsibility to operate them.
|
||||
|
||||
Self-hosting is not guaranteed to have the lowest sticker price in every configuration. Model both products against the same user, device, concurrency, feature, infrastructure, and operational requirements. See [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
Move off AnyDesk's cloud and the device list, the connection brokering, and the access rules all sit on hardware you run. For teams that want remote-access data kept in-house, that is the entire reason to switch.
|
||||
|
||||
## A practical AnyDesk migration checklist
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-02T12:27:00Z
|
||||
lang: en
|
||||
translationKey: anydesk-commercial-use-detected
|
||||
draft: false
|
||||
@@ -61,7 +61,7 @@ AnyDesk's free tier is licensed for personal use only, and [its terms allow enfo
|
||||
|
||||
The same licensing distinction exists in other remote-access products, including [TeamViewer's commercial-use classification](/blog/teamviewer-commercial-use-detected). For genuinely commercial support work, the warning is not a technical bug to work around; compare current paid plans or alternatives rather than relying on unofficial resets or private renewal anecdotes.
|
||||
|
||||
So if the appeal does not apply to you — because your use genuinely is commercial — the real question becomes: pay up, or move to something without a commercial-use tripwire at all?
|
||||
So if the appeal does not apply — your use genuinely is commercial — you are left with two paths: pay for a commercial license, or switch to a tool that has no commercial-use tripwire in the first place.
|
||||
|
||||
## The core difference: own the server, skip the nagging
|
||||
|
||||
@@ -79,7 +79,7 @@ On top of that, RustDesk's core client is open source under the [AGPL](/blog/cas
|
||||
| Session path | Direct when available; AnyDesk network relay otherwise | Direct when available; your relay otherwise |
|
||||
| Device allowance | Check current free-use terms | Commercial plans count managed devices |
|
||||
| Source code | Closed | Open source (AGPL), auditable |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Gated on free tier | Standard plans unlimited; Customized V2 limited |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Gated on free tier | Standard plans unlimited; [Customized V2](https://rustdesk.com/pricing#custom2) limited |
|
||||
| Pricing model | Per-seat cloud subscription | [Per login-user + per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) |
|
||||
| Data boundary | Vendor services coordinate access; media can be direct or relayed | Server-side services on infrastructure you control; endpoint routes still matter |
|
||||
|
||||
@@ -99,9 +99,9 @@ If you are supporting clients — the exact use AnyDesk's flag exists to catch
|
||||
|
||||
For specific access-control, SSO, and client-generation availability by plan, [see rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
## The honest caveat
|
||||
## No usage flags on hardware you run
|
||||
|
||||
Self-hosting is the fix for commercial-use nagging, but it means _someone on your side runs the server_. You provision a host, open ports, set up TLS, and patch it over time. It is not a heavy lift for an IT team — but it is real work. If what you actually want is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run, RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-desktop-software) and won't be that. Go in clear-eyed: you are trading a monthly bill and a commercial-use tripwire for a server you own and maintain.
|
||||
Self-host RustDesk and nothing is scanning your sessions for "commercial use" to bill or block — the community core is free and open source, and Server Pro is licensed on terms you agree to up front. You run the tool instead of negotiating with it.
|
||||
|
||||
## Choose the fix that matches your use
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-29T18:05:00Z
|
||||
lang: en
|
||||
translationKey: anydesk-price-increase-alternatives
|
||||
draft: false
|
||||
@@ -13,6 +13,18 @@ tags:
|
||||
- pricing
|
||||
- alternative
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'What are my options when AnyDesk raises the price?'
|
||||
answer: 'You really have two moves: renew and negotiate, or switch to a self-hosted, open-source tool like RustDesk where your recurring spend becomes your own infrastructure plus a license rather than a seat count a vendor re-prices on its own schedule. Cost both honestly before deciding.'
|
||||
- question: 'Does self-hosting make remote-desktop costs more predictable?'
|
||||
answer: 'Self-hosting changes who holds the pricing power: with RustDesk Server Pro you host it, so the cost is your infrastructure plus a license instead of a renewal the vendor sets. The product still has annual license terms, so compare the current pricing page at each renewal.'
|
||||
- question: 'Is switching away from AnyDesk worth the migration cost?'
|
||||
answer: "There is a real one-time switch cost — migration time, some retraining, and standing up and securing a server — but when the increase recurs, a switch often pays for itself within a renewal cycle or two. Estimate the switch cost once and weigh it against the increase you'd otherwise absorb at every renewal."
|
||||
- question: 'Is RustDesk open source?'
|
||||
answer: "Yes. RustDesk's core is open source under the AGPL, so you can read the code, verify what the client does, build it yourself, and run the free community server indefinitely."
|
||||
- question: 'Is self-hosting always cheaper than AnyDesk?'
|
||||
answer: 'Not necessarily in every configuration. Compare current quotes using the same login-user, managed-device, concurrency, feature, infrastructure, and support requirements; see rustdesk.com/pricing.'
|
||||
|
||||
metadata:
|
||||
description: 'Facing another AnyDesk price increase? See why teams switch to RustDesk: predictable self-hosted cost, your own data, and open-source transparency.'
|
||||
keywords: 'AnyDesk price increase, AnyDesk renewal cost, AnyDesk pricing alternatives, AnyDesk three-year TCO'
|
||||
@@ -40,7 +52,7 @@ Record the effective per-year cost and the exact entitlements in both quotes. Th
|
||||
|
||||
RustDesk Server Pro is **self-hosted**. The ID/rendezvous server, relay, console, and stored deployment data run on infrastructure you control. Direct sessions still flow between endpoints; relayed sessions use your configured relay. The product still has annual license terms, so compare the current pricing page at each renewal.
|
||||
|
||||
RustDesk licensing is **per login-user plus per managed-device**, and you can [upgrade](/blog/upgrade-rustdesk-license-mid-subscription) with proration. Standard plans include unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit); Customized V2 limits and prices them separately.
|
||||
RustDesk licensing is **per login-user plus per managed-device**, and you can [upgrade](/blog/upgrade-rustdesk-license-mid-subscription) with proration. Standard plans include unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit); [Customized V2](https://rustdesk.com/pricing#custom2) limits and prices them separately.
|
||||
|
||||
### Quick comparison
|
||||
|
||||
@@ -77,11 +89,9 @@ When the renewal quote jumps, you really have two moves, and it's worth costing
|
||||
|
||||
**The break-even.** Estimate the switch cost once — hours to migrate plus server setup — and weigh it against the increase you'd otherwise absorb at _every_ renewal. A one-time cost is a single line; a compounding annual increase is a curve. When the increase recurs, a switch often pays for itself within a renewal cycle or two. Run it with your own numbers before committing either way.
|
||||
|
||||
## The honest caveat
|
||||
## Take back the pricing power
|
||||
|
||||
Self-hosting is not free of effort, and pretending otherwise would be dishonest. **Someone on your side runs the server** — you provision a host, open ports, set up TLS, and keep it patched. That's real ops work. If what you actually want is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run, be clear-eyed: RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-desktop-software) and is not that.
|
||||
|
||||
Self-hosting is not necessarily the lowest-cost option in every configuration. Compare current quotes using the same login-user, managed-device, concurrency, feature, infrastructure, and support requirements. Check [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
Host the brokering yourself and the cost of remote access becomes infrastructure you own plus a license you set — not a number handed to you at renewal. That is the exit from the subscription treadmill.
|
||||
|
||||
## Build a comparable three-year cost model
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-03T08:18:00Z
|
||||
lang: en
|
||||
translationKey: avoid-remote-desktop-scams
|
||||
draft: false
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-06-30T08:42:00Z
|
||||
lang: en
|
||||
translationKey: best-free-remote-desktop-software
|
||||
draft: false
|
||||
@@ -18,7 +18,7 @@ faq:
|
||||
- question: 'Is any free remote desktop software actually free for commercial use?'
|
||||
answer: "Yes. RustDesk's open-source client and free community server, Apache Guacamole, MeshCentral, and the VNC family permit business use under their respective licenses. Chrome Remote Desktop is free and has documented enterprise controls; unlike TeamViewer and AnyDesk free tiers, it should not be described as personal-use-only. Always review the current terms for the exact deployment."
|
||||
- question: 'What is the catch with free remote desktop software?'
|
||||
answer: 'The catch is almost always effort. Free self-hosted tools like RustDesk, Guacamole, and MeshCentral require you to run and maintain a server. VNC needs port-forwarding or a VPN to work across the internet. The saving is money; the cost is operational work and, sometimes, missing convenience features.'
|
||||
answer: 'The catch is usually that you host it yourself. Free self-hosted tools like RustDesk, Guacamole, and MeshCentral need a server you run — with RustDesk the hardware requirements are low and upkeep is light once it is set up. VNC needs port-forwarding or a VPN to work across the internet. The saving is money; the trade is running your own server and, sometimes, missing convenience features.'
|
||||
- question: 'How is this different from open-source remote desktop software?'
|
||||
answer: 'Open source is about the license and auditability; free is about price and terms. There is overlap, but they are not the same lens. This guide focuses on tools that are free to run — especially for business — while our open-source guide compares the auditable, self-hostable options in depth.'
|
||||
metadata:
|
||||
@@ -42,7 +42,7 @@ The order below starts with the tools that are genuinely free for business use a
|
||||
|
||||
RustDesk sits first here because its client core is open source under the **[AGPL](/blog/case-for-open-source-remote-access)** and the **community server has no license fee or commercial-use classifier**. You still pay for any hosting and operations you choose. It is cross-platform (Windows, macOS, Linux, Android, iOS). On Windows, macOS, Linux, and Android hosts it includes file transfer and unattended access; the iOS app is controller-only. The source can be inspected and built independently.
|
||||
|
||||
**The catch:** self-hosting is real work. Someone provisions a host, opens ports, sets up TLS, and patches the server over time. The free community server also isn't the paid Server Pro — team features like the [web console, custom-branded clients, and device groups](/blog/rustdesk-web-console-custom-client-generator-port-21114) live in Server Pro (self-hosted, not free). For current terms, see [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
**The catch:** you run the server yourself — though the hardware requirements are low and, once it is set up, upkeep is light. Someone provisions a host, opens ports, and sets up TLS, then keeps it patched over time. The free community server also isn't the paid Server Pro — team features like the [web console, custom-branded clients, and device groups](/blog/rustdesk-web-console-custom-client-generator-port-21114) live in Server Pro (self-hosted, not free). For current terms, see [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
### Chrome Remote Desktop — free and simple, with Google-managed coordination
|
||||
|
||||
@@ -98,9 +98,9 @@ Most of the free options make you choose between Google-managed simplicity (CRD)
|
||||
|
||||
When your team outgrows the free server, [Server Pro](/blog/rustdesk-pro-license-cost-how-to-pay) adds the console, custom clients, device groups, and SSO — still self-hosted, priced per login-user and per managed-device.
|
||||
|
||||
## The honest caveat
|
||||
## Free, and genuinely yours
|
||||
|
||||
"Free" almost always means "you do the work." Every self-hosted option here — RustDesk, Guacamole, MeshCentral — trades a subscription for operational effort: a server to run, ports to open, TLS to configure, patches to apply. VNC trades it for networking setup. That's a real cost, just not a cash one. If your team genuinely wants a zero-maintenance managed cloud with nothing to run, none of these free tools are that, and paying for a hosted product may be the honest answer. Only you can weigh the trade.
|
||||
The community server costs nothing to run and keeps your sessions and device data on hardware you control — no license fee, no cloud in the path, no usage classifier. If you are comfortable running a small host, little else competes.
|
||||
|
||||
## Try RustDesk without a sales call
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-03T09:55:00Z
|
||||
lang: en
|
||||
translationKey: best-screenconnect-alternative-msps
|
||||
draft: false
|
||||
@@ -13,14 +13,28 @@ tags:
|
||||
- alternative
|
||||
- MSP
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Is RustDesk a good ScreenConnect alternative for MSPs?'
|
||||
answer: 'RustDesk is an open-source, self-hosted platform where the ID/rendezvous server, relay, console, and stored data run on infrastructure you control, with a custom-branded client generator and per-user access control built for MSP operations. Whether it fits depends on your team being comfortable running a server.'
|
||||
- question: 'Does RustDesk charge per channel like ScreenConnect?'
|
||||
answer: 'No. RustDesk licensing is per login-user plus per managed-device, and standard plans include unlimited concurrent connections; Customized V2 limits and prices them separately. See rustdesk.com/pricing.'
|
||||
- question: 'Can I self-host a ScreenConnect alternative?'
|
||||
answer: 'Yes. RustDesk Server Pro is self-hosted by design, and the free open-source community server supports a proof of concept before you evaluate paid features. Someone on your side provisions the host, opens the right ports, sets up TLS, and patches it over time.'
|
||||
- question: 'Does RustDesk support technician access control and SSO?'
|
||||
answer: 'Yes. RustDesk provides a self-hosted web console, device groups plus a shared address book so technicians can be scoped to assigned customer devices, and LDAP/SSO (OIDC) available from the Basic plan and up.'
|
||||
- question: 'Can an MSP evaluate RustDesk without migrating?'
|
||||
answer: 'Yes. You can self-host the free community server and run a proof-of-concept scorecard while keeping ScreenConnect available, watch a video walkthrough, or email sales@rustdesk.com to ask about current evaluation terms.'
|
||||
|
||||
metadata:
|
||||
description: 'Looking for a ScreenConnect alternative? RustDesk is self-hosted, open source, and brandable, with no per-channel cost. Built for MSPs.'
|
||||
keywords: 'ScreenConnect alternative, ConnectWise Control alternative for MSPs, self-hosted ScreenConnect replacement, MSP remote support alternative'
|
||||
---
|
||||
|
||||
## The Best ScreenConnect Alternative for MSPs
|
||||
## Why MSPs are evaluating ScreenConnect alternatives
|
||||
|
||||
[The 2024 ScreenConnect vulnerability](https://www.cisa.gov/news-events/alerts/2024/02/22/cisa-adds-one-known-exploited-connectwise-vulnerability-cve-2024-1709-catalog) and product packaging changes prompted renewed evaluation of alternatives. The documented event was exploitation of CVE-2024-1709 in affected ScreenConnect servers; it should not be described as ConnectWise itself being hacked. Security conclusions here rely on public disclosures.
|
||||
The short version: for an MSP that wants to own its remote-access stack, RustDesk is the strongest self-hosted, open-source ScreenConnect alternative — you run the server, brand the client, and license by users and devices rather than per technician.
|
||||
|
||||
[The 2024 ScreenConnect vulnerability](https://www.cisa.gov/news-events/alerts/2024/02/22/cisa-adds-one-known-exploited-connectwise-vulnerability-cve-2024-1709-catalog) and product packaging changes prompted renewed evaluation of alternatives. The documented event was exploitation of CVE-2024-1709 in affected ScreenConnect servers, not a compromise of ConnectWise itself. Security conclusions here rely on public disclosures.
|
||||
|
||||
If you run a managed services shop, this is a business-continuity question, not just a licensing one. When a critical remote-access server vulnerability is actively exploited, clients may block affected versions or instances until remediation is verified. This article makes the case for RustDesk: an open-source, self-hosted remote desktop platform built for an "our infrastructure, our rules" posture.
|
||||
|
||||
@@ -39,7 +53,7 @@ On top of that, RustDesk's core client is **[open source (AGPL)](/blog/case-for-
|
||||
| Hosting | Managed cloud or on-premise | [Self-hosted by design](/blog/why-self-host-remote-desktop-software); on-prem or your VPS |
|
||||
| Source code | Proprietary | Open source (AGPL), auditable |
|
||||
| Pricing model | Per-channel / seat (see vendor) | [Per login-user + per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) |
|
||||
| Concurrent sessions | Tied to channels/licensing | Standard plans unlimited; Customized V2 limited |
|
||||
| Concurrent sessions | Tied to channels/licensing | Standard plans unlimited; [Customized V2](https://rustdesk.com/pricing#custom2) limited |
|
||||
| Custom-branded client | Available (see vendor) | Custom-branded client generator |
|
||||
| [Data residency](/blog/remote-desktop-data-sovereignty-gdpr) | Vendor-dependent | Server-side services on infrastructure you control; endpoint routes still matter |
|
||||
| Evaluate without sales call | Varies | Free server today, or Pro trial on request |
|
||||
@@ -62,9 +76,9 @@ It also scales past the SMB tier: RustDesk publishes [large-fleet planning guida
|
||||
|
||||
For regulated clients, map where rendezvous, relay, device data, and endpoint traffic flow. Self-hosting provides control over server-side components but does not by itself guarantee data residency or GDPR compliance.
|
||||
|
||||
## The honest caveat
|
||||
## One tool, on servers you operate
|
||||
|
||||
Self-hosting is the strength and the responsibility. It means **someone on your side runs the server**: you provision a host, open the right ports, set up TLS, and patch it over time. If what you want is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run, RustDesk Server Pro is self-hosted by design and is not that. For most MSPs — who already run infrastructure for clients — this is a comfortable trade, and it's the price of full control over your data and your access tool.
|
||||
For an MSP, self-hosting keeps every customer's brokering, branding, and client data on infrastructure you run rather than a cloud rented per technician. That is what makes standing up your own worth it.
|
||||
|
||||
## MSP proof-of-concept scorecard
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-09T14:40:00Z
|
||||
lang: en
|
||||
translationKey: case-for-open-source-remote-access
|
||||
draft: false
|
||||
@@ -11,12 +11,24 @@ tags:
|
||||
- RustDesk
|
||||
- open-source
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Why does open source matter for remote access?'
|
||||
answer: "Remote-access software is designed to have total control of a remote machine, so the ability to read exactly what the client does — rather than believe the marketing — matters more than in most software categories. With RustDesk's AGPL core you can audit the code, build it yourself, and confirm what the client sends and where."
|
||||
- question: "Can I audit RustDesk's source code?"
|
||||
answer: "Yes. RustDesk's core is open source under the AGPL, so you or a security team you hire can read the code, produce a software bill of materials, build it in a controlled pipeline, and compare the resulting artifacts with what you distribute."
|
||||
- question: 'Does open source avoid vendor lock-in?'
|
||||
answer: "It reduces it. You can run the community server under its open-source license without a Server Pro subscription, so you are not dependent on a vendor's subscription and service to keep running."
|
||||
- question: "Does open-source remote access mean I can't get support features or scale?"
|
||||
answer: 'No. RustDesk documents large-deployment guidance and offers a web console, device groups, shared address books, and plan-dependent client generation and identity features; validate capacity against your own workload.'
|
||||
- question: 'Does self-hosting open-source remote access help with compliance?'
|
||||
answer: 'Yes — self-hosting gives you control over the rendezvous, relay, and management services, a strong foundation for privacy and residency. It is not a compliance checkbox by itself, though: endpoint location, routing, access controls, retention, and legal obligations still need to be assessed as part of your own program.'
|
||||
|
||||
metadata:
|
||||
description: 'Why open source matters in remote access: auditability, lower lock-in, infrastructure control, and the trade-offs of self-hosting.'
|
||||
keywords: 'why open source remote access, auditable remote support software, remote desktop source audit, open source trust model'
|
||||
---
|
||||
|
||||
## Why open source matters for remote access
|
||||
## What open source actually changes for remote access
|
||||
|
||||
Remote-access buyers often prioritize source auditability, infrastructure control, and predictable licensing.
|
||||
|
||||
@@ -38,13 +50,13 @@ Most software you can treat as a black box. Remote-access software you cannot, b
|
||||
| Where does session traffic go? | Through the vendor's cloud | Through servers you run |
|
||||
| Where does your data live? | Vendor infrastructure/region | Infrastructure you control; routing and endpoint location still matter |
|
||||
| Lock-in | Vendor subscription and service | Community server under an open-source license; Pro optional |
|
||||
| Who runs the server? | Vendor (nothing to run) | You (see the honest caveat below) |
|
||||
| Who runs the server? | Vendor (nothing to run) | You, on infrastructure you control |
|
||||
|
||||
## No lock-in, and a cost model that doesn't punish growth
|
||||
|
||||
Vendor-controlled subscription pricing can change at renewal. Compare current public terms or written quotes.
|
||||
|
||||
Open source is the structural answer to that treadmill. You can run the community server under its open-source license without a Server Pro subscription. Server Pro is licensed **per login-user plus per managed-device**, and mid-term upgrades may be prorated under current terms. **Standard plans include unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit); Customized V2 has a defined allowance.** Use the current [pricing page](https://rustdesk.com/pricing) for all rates and limits.
|
||||
Open source is the structural answer to that treadmill. You can run the community server under its open-source license without a Server Pro subscription. Server Pro is licensed **per login-user plus per managed-device**, and mid-term upgrades may be prorated under current terms. **Standard plans include unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit); [Customized V2](https://rustdesk.com/pricing#custom2) has a defined allowance.** Use the current [pricing page](https://rustdesk.com/pricing) for all rates and limits.
|
||||
|
||||
## Your data stays where your rules say it must
|
||||
|
||||
@@ -56,9 +68,9 @@ Self-hosting gives an organization control over its rendezvous, relay, and manag
|
||||
|
||||
A fair worry is whether a self-hostable option handles real load. RustDesk documents large-deployment guidance and offers a web console, device groups, shared address books, and plan-dependent client generation and identity features. Validate capacity against your own workload.
|
||||
|
||||
## The honest caveat: someone has to run the server
|
||||
## The open-source payoff
|
||||
|
||||
Open source and self-hosting are not free of trade-offs, and we'd rather you hear this from us. **Self-hosting means someone on your side runs the server**: you provision a host, open ports, set up TLS, and keep it patched. That's a real, ongoing responsibility. If what your team actually wants is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run and no ops burden, be clear-eyed about it — **RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-desktop-software), and it is not that.** The control and auditability you gain are inseparable from the fact that you own the box. For many teams that's the trade they want; for some it isn't, and that's fine.
|
||||
Open source plus self-hosting means you can read the code, run the server, and keep both for as long as you like with no vendor in the loop. That independence is the argument in a sentence.
|
||||
|
||||
## How to turn source access into assurance
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-01T08:14:00Z
|
||||
lang: en
|
||||
translationKey: chrome-remote-desktop-alternative
|
||||
draft: false
|
||||
@@ -17,7 +17,7 @@ faq:
|
||||
- question: 'Is there a Chrome Remote Desktop alternative that does not require a Google account?'
|
||||
answer: 'Yes. RustDesk uses its own ID/rendezvous and relay servers instead of a Google account, and you can self-host those servers so no third-party cloud sits in the middle. Chrome Remote Desktop, by contrast, requires a Google account on both the host and the client.'
|
||||
- question: 'Does Chrome Remote Desktop support file transfer?'
|
||||
answer: 'Chrome Remote Desktop offers only a basic upload/download file mechanism and no drag-and-drop; reviewers commonly list file transfer among its missing conveniences. RustDesk includes built-in file transfer alongside remote control.'
|
||||
answer: 'Chrome Remote Desktop provides basic file upload/download but not drag-and-drop transfer. RustDesk includes built-in file transfer alongside remote control.'
|
||||
- question: 'Can Chrome Remote Desktop provide unattended access?'
|
||||
answer: 'It can, but the target machine must be powered on and signed into the same Google account, and Chrome Remote Desktop cannot wake a sleeping computer. RustDesk supports permanent-password unattended access to a fleet you manage from your own console.'
|
||||
- question: 'Is RustDesk free like Chrome Remote Desktop?'
|
||||
@@ -33,7 +33,7 @@ metadata:
|
||||
|
||||
But the moment your needs grow past "help my own laptop from the couch," the seams show. You're tied to Google identity and signaling, some support-team features are missing, and the control plane is not self-hostable. Google's [network guide](https://support.google.com/chrome/a/answer/16364503) explains the boundary: connections are initially negotiated through Google services, while live WebRTC traffic uses Direct, STUN, or TURN/relay paths. Only TURN/relay session packets are relayed through Google data centers. If you've bumped into those trade-offs, this page lays out what a self-hosted, open-source alternative looks like.
|
||||
|
||||
We'll be even-handed about it: CRD is a legitimately good free tool for what it's designed to do, and RustDesk asks more of you up front. Here's the honest comparison.
|
||||
To be even-handed: CRD is a genuinely good free tool for what it's designed to do. Where you need control, auditability, or team features, an open-source, self-hosted model is the step up — here's how the two compare.
|
||||
|
||||
## What Chrome Remote Desktop does well
|
||||
|
||||
@@ -77,11 +77,9 @@ RustDesk's client core is open source under the **[AGPL](/blog/case-for-open-sou
|
||||
|
||||
On top of that self-hosted core, RustDesk adds the team features CRD lacks: a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114), a custom-branded client generator, [device groups and a shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book) for scoped access, and [LDAP/AD and OIDC SSO](/blog/rustdesk-active-directory-ldap-sso) from the Basic plan up. Real file transfer and permanent-password [unattended access](/blog/rustdesk-unattended-access-setup) come standard on Windows, macOS, Linux, and Android hosts; the iOS app is controller-only.
|
||||
|
||||
## The honest caveat
|
||||
## Off Google's cloud, onto yours
|
||||
|
||||
Here's the trade-off we won't hide: **Chrome Remote Desktop is zero-setup and genuinely free**, and RustDesk self-hosting is real work. Someone on your side has to provision a host, open the right ports, set up TLS, and patch the server over time. That's ongoing operational effort CRD simply doesn't ask of you.
|
||||
|
||||
If all you need is casual, occasional access to your own personal machine, CRD may be the right answer, and there's no shame in using it. RustDesk earns its keep when you need control, auditability, central management, and features CRD doesn't have — and you're willing to own a server to get them. If you'd rather not run anything, be clear-eyed: RustDesk Server Pro is self-hosted, not a zero-maintenance managed cloud.
|
||||
The step up from Chrome Remote Desktop is control: brokering, access policy, and session data move from Google's servers to one you operate and can audit. For anyone who wants remote access that answers to them, that is the payoff.
|
||||
|
||||
## Try it without a sales call
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-08T15:45:00Z
|
||||
lang: en
|
||||
translationKey: gotomypc-alternative-self-hosted
|
||||
draft: false
|
||||
@@ -20,8 +20,8 @@ faq:
|
||||
answer: 'GoToMyPC is priced per computer per month as a cloud subscription across its Personal, Pro, and Corporate plans. RustDesk Server Pro is licensed per login-user plus per managed-device, hosted on your own server, with unlimited concurrent connections on standard plans. There is no per-computer cloud subscription. For current rates, see rustdesk.com/pricing.'
|
||||
- question: 'Can RustDesk do unattended access to my own computers like GoToMyPC?'
|
||||
answer: "Yes. RustDesk supports permanent-password unattended access so you can reach your own machines without someone sitting at the far end, which is GoToMyPC's core use case. The difference is that with RustDesk you own the server brokering those connections instead of renting cloud access per computer."
|
||||
- question: 'What is the downside of switching from GoToMyPC to a self-hosted tool?'
|
||||
answer: 'GoToMyPC is fully managed with zero server upkeep — you just log in. With RustDesk you or your IT team run the server: provisioning a host, opening ports, setting up TLS, and patching it. For teams that already run a VPS it is a small lift; for anyone who wants nothing to maintain, that operational work is the real trade-off.'
|
||||
- question: 'What changes when you switch from GoToMyPC to self-hosted RustDesk?'
|
||||
answer: 'With RustDesk, you or your IT team run the server instead of renting cloud access per computer: provisioning a host, opening ports, setting up TLS, then keeping it patched. The hardware requirements are low and upkeep is light once it is set up, so for teams that already run any infrastructure it is a small lift, and RustDesk support can help if you get stuck.'
|
||||
metadata:
|
||||
description: 'Self-hosted GoToMyPC alternative: RustDesk is open-source, runs on your own server, and licenses per login-user and per managed-device, not per computer.'
|
||||
keywords: 'GoToMyPC alternative, self-hosted GoToMyPC alternative, open source GoToMyPC alternative, RustDesk vs GoToMyPC, self-hosted remote access, GoToMyPC replacement'
|
||||
@@ -29,7 +29,7 @@ metadata:
|
||||
|
||||
[GoToMyPC](https://get.gotomypc.com/) is built around a simple job: leave an agent on a computer and reach that computer later without someone at the far end. If that is the workflow you need to preserve, evaluate alternatives on unattended reliability, reboot recovery, display handling, file transfer, remote printing, and mobile access—not on the length of a generic feature list.
|
||||
|
||||
This is an honest comparison. RustDesk is a different model with clear advantages and one real trade-off. Here is where it fits as a self-hosted GoToMyPC alternative.
|
||||
RustDesk is a different model from GoToMyPC's per-computer cloud: you host it, so you own the access and the data. Here is where it fits as a self-hosted alternative.
|
||||
|
||||
## What GoToMyPC is (and isn't)
|
||||
|
||||
@@ -52,7 +52,7 @@ That introduces work GoToMyPC normally hides: server patching, certificates, fir
|
||||
| Source code | Proprietary | Open source (AGPL) core |
|
||||
| Server-side services | GoTo-operated | Operated on infrastructure you control |
|
||||
| Licensing model | Per computer, per month | [Per login-user + per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Plan-dependent | Unlimited on standard plans; limited on Customized V2 |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Plan-dependent | Unlimited on standard plans; limited on [Customized V2](https://rustdesk.com/pricing#custom2) |
|
||||
| Server maintenance | None (GoTo runs it) | Yours to run |
|
||||
|
||||
_GoToMyPC plans and prices change over time — confirm current terms on [GoTo's pricing page](https://get.gotomypc.com/plansandpricing). For RustDesk rates, see [rustdesk.com/pricing](https://rustdesk.com/pricing)._
|
||||
@@ -73,11 +73,9 @@ Before moving a production endpoint, test access after reboot and logout, host s
|
||||
|
||||
For regulated use, document the ID, relay, console, stored device data, endpoint locations, and direct-session routes. Self-hosting supplies server-side control; it does not make the deployment compliant on its own.
|
||||
|
||||
## The honest caveat: someone has to run the server
|
||||
## Own the server, not a per-seat bill
|
||||
|
||||
The trade-off is real and we won't hide it. Self-hosting means **someone on your side runs the server** — you provision a host, open ports, set up TLS, and patch it over time. For a team that already runs a VPS or a spare box, that is a small lift. For a solo user who just wants to click and connect with nothing to maintain, it is the one genuine cost of moving off GoToMyPC's cloud.
|
||||
|
||||
GoToMyPC is fully managed with **zero server upkeep**, and for some people that convenience is worth the subscription. RustDesk Server Pro is [self-hosted by design](/blog/rustdesk-self-hosted-vs-cloud-saas-option), and its commercial rates and allowances can still change. The structural difference is who operates the server-side services, not a promise that pricing will never change.
|
||||
Rather than renting cloud access per computer, you run the server that coordinates your connections — so reach, cost, and data stay in your hands. For anyone already running a little infrastructure, it is a short step.
|
||||
|
||||
## Try it without a sales call
|
||||
|
||||
@@ -85,4 +83,4 @@ GoToMyPC is fully managed with **zero server upkeep**, and for some people that
|
||||
- **Want the Pro features?** Email [sales@rustdesk.com](mailto:sales@rustdesk.com) about current evaluation terms, or check [rustdesk.com/pricing](https://rustdesk.com/pricing) for standard plan rates.
|
||||
- **Prefer to see it first?** Watch a full [video demo](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk) — no booking required.
|
||||
|
||||
If cost and control are why you are looking past GoToMyPC, a self-hosted, open-source alternative is worth an afternoon of your time.
|
||||
If cost and control are why you are looking past GoToMyPC, a self-hosted, open-source alternative is worth standing up and testing.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-06-30T17:26:00Z
|
||||
lang: en
|
||||
translationKey: is-anydesk-safe
|
||||
draft: false
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-05T18:49:00Z
|
||||
lang: en
|
||||
translationKey: is-chrome-remote-desktop-safe
|
||||
draft: false
|
||||
@@ -61,7 +61,7 @@ You can't self-host it. Every CRD connection is brokered through Google's cloud
|
||||
|
||||
This is where an open-source, self-hosted model offers a different _kind_ of assurance rather than just more features. With RustDesk, the client is [open source under the AGPL](/blog/case-for-open-source-remote-access), so the code is auditable and buildable — you don't take the vendor's word for what it does. And self-hosting means the ID/rendezvous and relay servers run on your own machine or VPS, so brokering and access policy stay on infrastructure you control instead of Google's cloud — which maps directly onto [data-sovereignty and GDPR](/blog/remote-desktop-data-sovereignty-gdpr) concerns.
|
||||
|
||||
In fairness, that assurance comes with strings. Open source means RustDesk's own bugs are public too; track the [latest releases](https://github.com/rustdesk/rustdesk/releases) and current vulnerability records. Self-hosting does not automatically make a deployment compliant or secure—direct sessions still flow between endpoints, and you own server patching.
|
||||
That openness cuts both ways, to be clear: because the code is public, so are RustDesk's own vulnerabilities, so keep an eye on the [latest releases](https://github.com/rustdesk/rustdesk/releases) and disclosure records. And self-hosting is a foundation, not an automatic compliance win — traffic still travels directly between endpoints, and the server is yours to patch.
|
||||
|
||||
## The verdict
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-07T16:55:00Z
|
||||
lang: en
|
||||
translationKey: open-source-remote-desktop-software
|
||||
draft: false
|
||||
@@ -12,12 +12,24 @@ tags:
|
||||
- open-source
|
||||
- comparison
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'What open-source remote desktop software is available?'
|
||||
answer: 'Options range from protocol-level building blocks like VNC (TigerVNC, TightVNC) and the Apache Guacamole browser gateway to full support platforms. RustDesk aims to give you an auditable, self-hostable core plus support-team features like device groups, a shared address book, and a custom client generator.'
|
||||
- question: 'Is RustDesk open source?'
|
||||
answer: "Yes. RustDesk's core is open source under the AGPL, so you can read the code, audit exactly what the client does, build it yourself, and run the free community server indefinitely."
|
||||
- question: "Can I self-host RustDesk's server?"
|
||||
answer: 'Yes. RustDesk Server Pro is self-hosted by design: the ID/rendezvous and relay servers run on your own machine, on-prem or a VPS you rent, and you control those services and managed-device data.'
|
||||
- question: 'How does RustDesk handle concurrent connections and licensing?'
|
||||
answer: 'Standard plans include unlimited concurrent connections and are sized by login users plus managed devices, so several technicians can run sessions at once without paying per channel. Customized V2 limits and prices concurrent connections separately; see rustdesk.com/pricing.'
|
||||
- question: 'What platforms does RustDesk support?'
|
||||
answer: 'RustDesk offers Windows, macOS, Linux, and Android host/controller clients, plus iOS and web-client controller options. Supported host platforms can be managed from a self-hosted web console for permanent-password unattended access to your fleet and ad-hoc attended sessions for one-off support; iOS and the web client can control other devices but cannot act as unattended hosts.'
|
||||
|
||||
metadata:
|
||||
description: 'Comparing open source remote desktop software? See why teams pick auditable, self-hosted tools over TeamViewer and AnyDesk — and where RustDesk fits.'
|
||||
keywords: 'open source remote desktop software, self-hosted remote desktop software, open source remote desktop comparison, AGPL remote desktop'
|
||||
---
|
||||
|
||||
## Open-Source Remote Desktop Software: The Options
|
||||
## What to look for in an open-source remote desktop tool
|
||||
|
||||
Teams shopping for **open source remote desktop software** typically want to inspect the code, control infrastructure, and reduce dependence on a vendor's pricing and hosting decisions.
|
||||
|
||||
@@ -58,7 +70,7 @@ When you move to Server Pro, it's **[self-hosted by design](/blog/why-self-host-
|
||||
|
||||
### Plan-specific concurrency and licensing
|
||||
|
||||
A recurring frustration with closed tools is the pricing model itself. RustDesk standard plans include unlimited concurrent connections and are sized by login users plus managed devices. **Customized V2 is different:** it limits and prices concurrent connections separately. For current allowances and rates, [see rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
A recurring frustration with closed tools is the pricing model itself. RustDesk standard plans include unlimited concurrent connections and are sized by login users plus managed devices. **[Customized V2](https://rustdesk.com/pricing#custom2) is different:** it limits and prices concurrent connections separately. For current allowances and rates, [see rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
It also scales past the "small shop" ceiling: RustDesk publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices) for teams evaluating much larger estates.
|
||||
|
||||
@@ -74,11 +86,11 @@ Open source doesn't have to mean "bring your own everything." RustDesk ships a s
|
||||
- **Custom, branded clients.** Generate your own preconfigured, logo-branded installer for the platforms you deploy to.
|
||||
- **Access control that fits teams.** [Device groups and a shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book) decide who can reach which machines; [LDAP/SSO](/blog/rustdesk-active-directory-ldap-sso) (OIDC) is available from the Basic plan and up.
|
||||
- **Unattended and attended access.** Permanent-password unattended access for your fleet, plus ad-hoc sessions for one-off support.
|
||||
- **Every major platform.** Windows, macOS, Linux, Android, and iOS clients, managed from a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114).
|
||||
- **Every major platform.** Windows, macOS, Linux, and Android host/controller clients, plus iOS and [web-client](/blog/rustdesk-web-client-v2-preview) controller options, managed from a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114).
|
||||
|
||||
### The honest caveat
|
||||
### Self-hosted, and unmistakably yours
|
||||
|
||||
Self-hosting is the whole point — and it's also the trade-off. **Someone on your side has to run the server**: provision a host, open the right ports, set up TLS, and patch it over time. That's real, ongoing operational work. If what you actually want is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run, be clear-eyed: RustDesk Server Pro is self-hosted by design and is _not_ that. The upside is control and auditability; the cost is that you own the box. Only you can decide if that trade is worth it for your team.
|
||||
Self-hosting is the point: you run the ID and relay, so the data, the access policy, and the cost all stay on hardware you control and can audit. Standing up one more server is a modest step for most IT teams — the hardware requirements are low and upkeep is light once it is set up.
|
||||
|
||||
### Try it without a sales call
|
||||
|
||||
|
||||
+7
-7
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-09T16:08:00Z
|
||||
lang: en
|
||||
translationKey: remote-desktop-alternatives-dameware-bomgar-supremo-parsec-remotepc
|
||||
draft: false
|
||||
@@ -52,23 +52,23 @@ RustDesk's [per login-user and per managed-device](/blog/rustdesk-pro-license-co
|
||||
|
||||
## Replacing Supremo
|
||||
|
||||
Supremo comparisons tend to focus on performance and price. Benchmark both products on the same network and compare current concurrency terms: RustDesk standard plans are unlimited, while Customized V2 is limited.
|
||||
Supremo comparisons tend to focus on performance and price. Benchmark both products on the same network and compare current concurrency terms: RustDesk standard plans are unlimited, while [Customized V2](https://rustdesk.com/pricing#custom2) is limited.
|
||||
|
||||
## Replacing Parsec
|
||||
|
||||
Parsec comparisons often involve VDI, CAD, or creative workloads. Performance-sensitive buyers should run a proof of concept on their own hardware rather than infer results from someone else's benchmarks.
|
||||
|
||||
For this group, the self-hosted web client is usually the first thing they want to test — RustDesk lets you validate real-world performance on your own infrastructure before committing at scale, rather than taking a vendor's word for it.
|
||||
For this group, the native client on their own hardware is usually the first thing they benchmark — RustDesk lets you validate real-world latency and performance before committing at scale, rather than taking a vendor's word for it.
|
||||
|
||||
## Replacing RemotePC
|
||||
|
||||
RemotePC and RealVNC comparisons typically cover price, reliability, and self-hosting. Test the exact workflows you depend on before committing.
|
||||
RemotePC comparisons typically cover price, reliability, and self-hosting. Test the exact workflows you depend on before committing.
|
||||
|
||||
## Use a weighted replacement scorecard
|
||||
|
||||
Assign each requirement a weight and score only after a hands-on test. At minimum include attended support, unattended access, elevation, file transfer, multi-monitor, platform coverage, client deployment, identity, per-device authorization, audit events, relay performance, recovery, and operating effort. Price the configuration that passes the scorecard—not the cheapest tier from each vendor.
|
||||
|
||||
RustDesk standard plans include unlimited concurrent connections, while Customized V2 has a defined allowance. All commercial plans must also fit both login-user and managed-device counts. Features such as custom client generation and identity controls vary by plan, so verify the current [pricing matrix](https://rustdesk.com/pricing).
|
||||
RustDesk standard plans include unlimited concurrent connections, while Customized V2 has a defined allowance. All commercial plans must also fit both login-user and managed-device counts. Custom client generation and identity controls are available from the Basic plan and up, so verify the current [pricing matrix](https://rustdesk.com/pricing).
|
||||
|
||||
## More focused comparisons
|
||||
|
||||
@@ -78,9 +78,9 @@ RustDesk standard plans include unlimited concurrent connections, while Customiz
|
||||
- For protocol-level trade-offs, compare [RustDesk vs RDP](/blog/rustdesk-vs-rdp) and [RustDesk vs VNC](/blog/rustdesk-vs-vnc).
|
||||
- For MSP support operations, use [RustDesk vs ScreenConnect](/blog/rustdesk-vs-screenconnect).
|
||||
|
||||
## The honest caveat
|
||||
## The self-hosted separator
|
||||
|
||||
Self-hosting means someone on your side runs the server: provisioning, ports, TLS, and patching. If your team wants a fully managed cloud with nothing to maintain, that's a real trade-off to weigh — RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-desktop-software).
|
||||
Against a field of cloud products, RustDesk's difference is plain: you host the coordination and keep the data, instead of routing both through a vendor. For teams that weight control heavily, that is the deciding line.
|
||||
|
||||
## Try it without a sales call
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-04T17:05:00Z
|
||||
lang: en
|
||||
translationKey: remote-desktop-data-sovereignty-gdpr
|
||||
draft: false
|
||||
@@ -13,6 +13,17 @@ tags:
|
||||
- GDPR
|
||||
- self-hosting
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Is RustDesk ISO 27001, SOC 2, or HIPAA compliant?'
|
||||
answer: 'RustDesk is self-hosted, so compliance centers on your environment: you run remote access inside your own ISO 27001 or HIPAA scope and existing controls, and the open-source client can be audited directly rather than taken on trust. If you specifically need a vendor SOC 2 report, a signed BAA, a DPA, or completed security questionnaires, ask sales@rustdesk.com what is available for your scenario.'
|
||||
- question: 'Does self-hosting RustDesk help with GDPR compliance?'
|
||||
answer: 'Yes — it gives you the control GDPR is usually about: you choose where the ID/rendezvous, relay, console, and device data live and can keep them in-region on infrastructure you operate. That is a strong foundation rather than an automatic guarantee, since GDPR is a program — lawful basis, controller/processor roles, retention, access control, endpoint locations, and incident response are still yours to define, with the controller remaining responsible.'
|
||||
- question: 'Where does RustDesk session data actually go?'
|
||||
answer: 'RustDesk first tries a direct peer-to-peer connection; if that fails, traffic uses your configured relay. Self-hosting removes a vendor-operated rendezvous and relay from the path, but a session between endpoints in different countries still crosses those networks — server placement alone does not confine all traffic to one jurisdiction.'
|
||||
- question: 'Can I keep remote desktop data inside the EU with RustDesk?'
|
||||
answer: 'You can place the ID/rendezvous, relay, console, and stored device data in an EU data center. To constrain session traffic too, both endpoints must be within the boundary and policy must force traffic through your approved relay; document endpoint locations and routing alongside server placement.'
|
||||
- question: 'What RustDesk features help meet GDPR?'
|
||||
answer: 'Self-hosting keeps data on infrastructure you control: because usage telemetry is collected by the relay server, running your own relay keeps that data on your relay rather than RustDesk, and beyond the Server Pro license check little else needs to reach rustdesk.com. Server Pro adds built-in audit logs with log rotation, granular access control and a Control Role, SSO/LDAP and controlled-device 2FA, privacy mode and per-connection consent, and direct deletion of users, devices, and records (including via the REST API) for erasure and retention requests.'
|
||||
metadata:
|
||||
description: 'Remote desktop data sovereignty & GDPR: what self-hosting controls, how direct and relayed sessions differ, and why compliance needs more than server location.'
|
||||
keywords: 'remote desktop data sovereignty, GDPR remote access, remote desktop data residency, self-hosted remote access compliance'
|
||||
@@ -56,13 +67,39 @@ Data sovereignty isn't only about location — it's about knowing what the softw
|
||||
|
||||
## Benefit 3: Sovereignty without a licensing tax
|
||||
|
||||
RustDesk standard plans are licensed **per login-user plus per managed-device** and include unlimited concurrent connections; Customized V2 instead limits and prices concurrent connections. You can [upgrade a license](/blog/upgrade-rustdesk-license-mid-subscription) as requirements change. Check the current plan matrix before purchasing.
|
||||
RustDesk standard plans are licensed **per login-user plus per managed-device** and include unlimited concurrent connections; [Customized V2](https://rustdesk.com/pricing#custom2) instead limits and prices concurrent connections. You can [upgrade a license](/blog/upgrade-rustdesk-license-mid-subscription) as requirements change. Check the current plan matrix before purchasing.
|
||||
|
||||
The architecture also scales with your estate: RustDesk publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices) for teams evaluating bigger deployments. For [per-user access control](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book), self-hosted deployments include a [web console](/blog/rustdesk-web-console-custom-client-generator-port-21114), a custom-branded client generator, device groups with a shared address book, and [LDAP/SSO](/blog/rustdesk-active-directory-ldap-sso) (OIDC) available from the Basic plan and up.
|
||||
|
||||
## The honest caveat: someone has to run the server
|
||||
## How RustDesk fits ISO 27001, SOC 2, or HIPAA requirements
|
||||
|
||||
Self-hosting has a real cost: **someone on your side runs and secures the server.** You provision a host, restrict ports, configure TLS, manage access, retain logs, patch components, and document data flows. Self-hosting can support a GDPR program, but it does not by itself make a deployment GDPR-compliant; lawful basis, processor/controller roles, retention, access controls, endpoint locations, incident response, and other obligations still apply.
|
||||
Enterprise procurement and healthcare teams almost always ask how a remote-access tool maps to ISO 27001, SOC 2, or HIPAA. With a cloud product, you inherit — and depend on — the vendor's certification of _their_ infrastructure. RustDesk's model is different, and for regulated teams the difference usually works in your favor: because you **self-host**, remote access runs inside the environment you already control and audit, so it falls under _your_ ISO 27001 or HIPAA scope and _your_ existing controls rather than a third party's. You place the ID, relay, and console on infrastructure your program already covers, and — because the core client is [open source](/blog/case-for-open-source-remote-access) — your security team can read and verify exactly what it does as part of an assessment, instead of trusting a closed binary.
|
||||
|
||||
A few practical notes:
|
||||
|
||||
- Self-hosting keeps the sensitive systems — rendezvous, relay, console, and device data — on hardware you own, which is exactly what a data-residency or HIPAA control is usually trying to guarantee. The deployment checklist further down turns that into documented controls.
|
||||
- If your procurement specifically requires a vendor-side SOC 2 report, a signed Business Associate Agreement (BAA), a DPA, or completed security questionnaires, ask the RustDesk team at [sales@rustdesk.com](mailto:sales@rustdesk.com) what is currently available for your scenario.
|
||||
- Because the client is open source, "how do we know what it does?" is answered by inspection, not by a certificate you have to take on faith.
|
||||
|
||||
In short, self-hosting lets you fold remote access into the compliance program you already run — often a stronger position for a regulated team than renting a certified black box.
|
||||
|
||||
## Controls that support a self-hosted GDPR program
|
||||
|
||||
Self-hosting is the foundation, and on top of it RustDesk provides concrete controls self-hosted teams rely on to meet GDPR in practice:
|
||||
|
||||
- **Telemetry goes to your relay, not RustDesk.** The usage data described in RustDesk's privacy policy — app start, IP address, basic machine stats, session times, and RustDesk IDs — is collected by the _relay_ server, so when clients use your own self-hosted relay it is **collected by your relay, not RustDesk**. Beyond the Server Pro license check, little else needs to reach rustdesk.com — confirm the exact outbound connections for the client build and settings you deploy. That keeps session and usage data on infrastructure you control by default, a strong data-minimization posture.
|
||||
- **Built-in audit-log rotation and retention.** Server Pro's audit logs come in four categories — connection, file-transfer, alarm, and console-operation — with **built-in log rotation** so audit data is not retained indefinitely (storage limitation), and you can export them from the web console or the REST API for your records of processing.
|
||||
- **Granular, scoped access.** Per-user assignments, device groups, cross-group rules, and a Control Role (what a technician may do in-session — input, clipboard, file transfer, camera, terminal) enforce least privilege and purpose limitation, backed by SSO/LDAP and controlled-device 2FA.
|
||||
- **Privacy mode and per-connection consent.** The controlled side can require confirmation for an incoming connection and can blacken its screen (privacy mode) during a session, limiting incidental exposure of personal data on-screen.
|
||||
- **Deletion on your terms.** Because the data lives on your server, you can disable or remove users, delete devices and records — including via the REST API — and service erasure and retention requests directly.
|
||||
- **In-region, self-operated infrastructure.** The ID/rendezvous, relay, console, and stored data run where you place them, on hardware you control.
|
||||
- **Even custom-client builds leave no data behind.** Generating a branded client is the one step that uses RustDesk's build service, and it is deliberately transient: the build configuration you submit is not retained on RustDesk's build server (it is deleted once the build completes), and the generated installer is auto-removed after about a day, so you download and keep it yourself.
|
||||
|
||||
These are levers a GDPR program can actually pull: you still document and operate them, but you are not waiting on a vendor to act on a data-subject request.
|
||||
|
||||
## Sovereignty you can point to
|
||||
|
||||
Hosting the rendezvous, relay, console, and stored data yourself gives a compliance program something concrete: infrastructure you place, operate, and audit. It is a foundation rather than a finish line, but it is the part everything else rests on.
|
||||
|
||||
## GDPR and sovereignty deployment checklist
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-26T19:43:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-active-directory-ldap-sso
|
||||
draft: false
|
||||
@@ -52,7 +52,7 @@ This comes up most from IT admins, [MSPs](/blog/rustdesk-for-msps), and business
|
||||
- [Does RustDesk support SSO or SAML in addition to LDAP / Active Directory?](https://rustdesk.com/docs)
|
||||
- [Which RustDesk plan do I need for a custom-branded client?](/blog/rustdesk-web-console-custom-client-generator-port-21114)
|
||||
- [How does per-user versus per-device licensing work in Server Pro?](/blog/rustdesk-pro-license-cost-how-to-pay)
|
||||
- [Can I self-host the RustDesk web client, and which plan includes it?](/blog/rustdesk-web-console-custom-client-generator-port-21114)
|
||||
- [Can I self-host the RustDesk web client, and which plan includes it?](/blog/rustdesk-web-client-v2-preview)
|
||||
- [Is LDAPS (LDAP over TLS) supported with an internal certificate authority?](https://rustdesk.com/docs)
|
||||
|
||||
Evaluating RustDesk for your directory-backed environment? Check the current plan and LDAP details at rustdesk.com, and reach out to the team if you need LDAPS with a custom PKI certificate so they can weigh your requirement.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-08T00:00:00Z
|
||||
publishDate: 2026-07-06T12:36:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-and-remote-access-scams
|
||||
draft: false
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-03T13:07:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-concurrent-connections-limit
|
||||
draft: false
|
||||
@@ -27,7 +27,7 @@ metadata:
|
||||
keywords: 'RustDesk concurrent connections, RustDesk concurrent connection limit, RustDesk user vs device licensing, RustDesk concurrent sessions, remote desktop concurrent channels, RustDesk licensing for MSPs'
|
||||
---
|
||||
|
||||
Standard RustDesk plans include unlimited concurrent connections. **Customized V2 is the exception:** it limits concurrent connections and prices additional connections separately. All paid plans also enforce their licensed login-user and managed-device allowances.
|
||||
Standard RustDesk plans include unlimited concurrent connections. **[Customized V2](https://rustdesk.com/pricing#custom2) is the exception:** it limits concurrent connections and prices additional connections separately. All paid plans also enforce their licensed login-user and managed-device allowances.
|
||||
|
||||
## The short answer
|
||||
|
||||
@@ -52,7 +52,7 @@ This question comes up most from IT admins and [MSPs](/blog/rustdesk-for-msps) e
|
||||
- [What is the difference between a user and a device in RustDesk licensing?](/blog/what-counts-as-a-managed-device)
|
||||
- [Do I need a separate license for every technician on my team?](/blog/rustdesk-pro-license-cost-how-to-pay)
|
||||
- [Can multiple people control the same device at the same time?](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book)
|
||||
- [How do I count devices for unattended access?](/blog/what-counts-as-a-managed-device)
|
||||
- [How do I count devices for unattended access?](/blog/rustdesk-unattended-access-setup)
|
||||
- [Does RustDesk charge extra for peak-hour usage or overages?](/blog/rustdesk-custom-quote-minimum-users-invoice-fees)
|
||||
|
||||
Sizing a plan for your team? Count login users and managed devices, then include concurrent connections if you are considering Customized V2.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-06T08:31:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-connected-waiting-for-image
|
||||
draft: false
|
||||
@@ -56,7 +56,7 @@ If a monitor _is_ attached, the next suspect is that it went to sleep.
|
||||
| Codec mismatch | Blank or frozen image | Switch between H.264 / VP8 / VP9; on Linux install the matching hardware codec |
|
||||
| Hardware acceleration conflict | Black on specific GPUs | Disable with `--hwaccel=0` or `--render=software`; on Windows try `--render=d3d` |
|
||||
| Outdated GPU driver | Black after a driver/OS update | Update the GPU driver (NVIDIA especially) |
|
||||
| Wayland session (Linux) | No consent prompt, blank | Use an X11/Xorg session, or accept the per-connect PipeWire prompt |
|
||||
| Wayland session (Linux) | No consent prompt, blank | Accept the PipeWire/portal prompt and confirm the desktop portal is installed; an X11 session also works where a distro still offers one |
|
||||
| Network / relay stall | Sticks on "waiting for image" | Allow TCP 21115-21117 and UDP 21116; add TCP 21118-21119 for WebSocket clients |
|
||||
|
||||
### Screen sleep, lock, and screensavers
|
||||
@@ -85,7 +85,7 @@ Some GPUs — NVIDIA configurations come up most often — clash with RustDesk's
|
||||
|
||||
### Linux and Wayland
|
||||
|
||||
On Linux, **Wayland screen capture is experimental**: it goes through PipeWire and the `xdg-desktop-portal`, pops a consent dialog on each connect, and only works inside an active login session — not at the greeter and not truly headless. If you get a blank screen on Wayland, the most reliable move is to log into an **X11/Xorg session** instead, or use the documented headless configuration. See the [Linux client docs](https://rustdesk.com/docs/en/client/linux/) for the current state.
|
||||
On Linux, **Wayland screen capture goes through PipeWire and the `xdg-desktop-portal`**: it prompts for consent to pick a display the first time — in most cases the choice is remembered, so it does not prompt again — and works inside an active login session. That is a Wayland security design, so by itself it does not cover the greeter or a truly headless box — though unattended Wayland capture is in active development ([PR #15420](https://github.com/rustdesk/rustdesk/pull/15420)). If you get a blank screen on Wayland, the fix is usually to accept the portal's screen-share prompt and confirm `xdg-desktop-portal` and PipeWire are installed and running; on a headless box, use the documented virtual-display configuration. Logging into an X11/Xorg session also avoids the portal path where a distribution still offers one — but as many distributions move to Wayland-only, fixing the portal/PipeWire path is the more future-proof approach. See the [Linux client docs](https://rustdesk.com/docs/en/client/linux/) for the current state.
|
||||
|
||||
### Network and relay
|
||||
|
||||
@@ -99,8 +99,6 @@ Old builds carry old capture bugs. Update **both** the controlling client and th
|
||||
|
||||
When a black screen defies the checklist, RustDesk gives you something closed-source tools don't: the [actual capture code](/blog/open-source-remote-desktop-software) under an AGPL license. You (or a contractor) can read exactly how capture works on your platform, reproduce the issue, and file a precise report against the public repository — instead of waiting on a vendor's support queue. And because you can [run the relay on your own machine](/blog/why-self-host-remote-desktop-software), you remove the shared-server variable entirely.
|
||||
|
||||
## An honest caveat
|
||||
## Fewer variables when the server is yours
|
||||
|
||||
There is no single switch that fixes "waiting for image," because it isn't one bug — it's a family of capture problems. A headless server, a dozing Mac, a Wayland session, and a stale NVIDIA driver all surface the same message. Work top-down: confirm there's an awake display to capture, then permissions, then codec, then acceleration and drivers. That order resolves the large majority of cases.
|
||||
|
||||
Running this across a fleet? A [self-hosted RustDesk deployment](/blog/why-self-host-remote-desktop-software) with the free community server lets you standardize capture settings and eliminate the public relay as a variable — and it costs nothing to start. For commercial features, see [rustdesk.com/pricing](https://rustdesk.com/pricing) or email sales@rustdesk.com.
|
||||
Run your own relay and ID server and the shared public infrastructure drops out of the picture — one less unknown when you are chasing a capture problem, and full control over the parts you can tune. That is a quiet bonus on top of keeping the data.
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-26T13:09:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-custom-quote-minimum-users-invoice-fees
|
||||
draft: false
|
||||
@@ -22,14 +22,18 @@ faq:
|
||||
- question: 'Is there a minimum number of users required for RustDesk Pro?'
|
||||
answer: 'No fixed public minimum is quoted here. If your team is small, confirm the current entry-level allowances and any minimum with the RustDesk team at sales@rustdesk.com before you buy.'
|
||||
- question: 'Can I pay for RustDesk by bank transfer or invoice?'
|
||||
answer: 'Online checkout follows the displayed flow. For bank transfer or invoice, contact RustDesk for the current fee, tax, and payment instructions rather than assuming a threshold or surcharge that is not shown on the pricing page.'
|
||||
answer: 'Yes. RustDesk accepts major credit cards and online payment methods at checkout, and bank transfer on request — email sales@rustdesk.com. Bank transfer carries an extra bank processing fee, and the license is issued once the funds arrive, typically in about 3–5 working days (SEPA bank debit can take around 6 business days, sometimes up to 10).'
|
||||
- question: 'Can I get a business invoice with my company name and tax number (VAT)?'
|
||||
answer: 'Yes. After payment you receive an invoice and license by email, and the currency you select at checkout is the currency shown on the invoice. If you need a business invoice with your business name and tax number, tick the "I am purchasing as a business" checkbox on the payment page. You can also re-download invoices anytime from the self-service license portal at rustdesk.com/self-host/account/ — log in with the email you used on the payment page, and if you no longer know which email that was, contact support@rustdesk.com.'
|
||||
- question: 'Does RustDesk auto-renew?'
|
||||
answer: 'RustDesk bills annually only — there is no monthly plan and no auto-renewal; you get an email reminder 14 days before expiry. You can validate your whole deployment on the free self-hosted plan before you buy.'
|
||||
|
||||
metadata:
|
||||
description: 'How to size a RustDesk self-hosted Pro custom quote by login users and managed devices, and confirm invoice, bank transfer, and current billing terms.'
|
||||
keywords: 'RustDesk custom quote, RustDesk self-hosted Pro pricing, RustDesk minimum users, RustDesk per-user per-device, RustDesk invoice fee, RustDesk volume pricing'
|
||||
---
|
||||
|
||||
RustDesk publishes fixed allowances for Basic and configurable user/device allowances for Customized. Customized V2 additionally lets buyers select a limited number of concurrent connections. For larger plans or invoice requirements, contact the sales team.
|
||||
RustDesk publishes fixed allowances for Basic and configurable user/device allowances for Customized. [Customized V2](https://rustdesk.com/pricing#custom2) additionally lets buyers select a limited number of concurrent connections. For larger plans or invoice requirements, contact the sales team.
|
||||
|
||||
## The short answer
|
||||
|
||||
@@ -41,7 +45,7 @@ Because Customized licensing scales along login-user and managed-device counts,
|
||||
|
||||
Basic currently includes fixed login-user and managed-device allowances. Customized starts from the Basic feature set and adds separately priced users and devices. Use the live calculator rather than relying on historical quote rules.
|
||||
|
||||
The payment method affects timing and total cost. Online checkout follows the displayed flow. For bank transfer or invoice, contact RustDesk for the current fee, tax, and payment instructions. Do not assume a threshold, surcharge, or turnaround time that is not shown on the current pricing page or confirmed in writing.
|
||||
The payment method affects timing and total cost. Online checkout accepts major credit cards and common online payment methods, and you receive your invoice and license by email once payment clears. If you need a **business invoice** with your company name and **tax number (VAT)**, tick the "I am purchasing as a business" box on the payment page; the currency you choose there is the currency printed on the invoice. **Bank transfer** is available on request through [sales@rustdesk.com](mailto:sales@rustdesk.com) — it carries an extra bank processing fee, and the license is issued after the funds arrive, typically in about 3–5 working days (SEPA bank debit can take roughly 6 business days, occasionally up to 10). Billing is **annual only**: there is no monthly option and no auto-renewal, though RustDesk emails a renewal reminder 14 days before expiry. One thing buyers often ask about: there are no hidden fees beyond the displayed plan cost. You can validate your whole deployment on the free self-hosted plan before you buy. After purchase, you can retrieve invoices and manage renewals, upgrades, or a license migration anytime in the [self-service license portal](https://rustdesk.com/self-host/account/) — log in with the email you used on the payment page, or email [support@rustdesk.com](mailto:support@rustdesk.com) if you no longer know which one. Always confirm the latest terms on [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
To keep the process quick, gather your user count, device count, and any billing constraints before you request a quote. That reduces back-and-forth and helps you compare options against the current plan matrix.
|
||||
|
||||
@@ -53,7 +57,7 @@ This comes up most often with IT admins, MSPs, and businesses evaluating RustDes
|
||||
|
||||
- [How does RustDesk's per-user and per-device licensing work?](/blog/what-counts-as-a-managed-device)
|
||||
- [What is the difference between the Basic and Custom self-hosted Pro plans?](/blog/rustdesk-pro-license-cost-how-to-pay)
|
||||
- [Can I pay for RustDesk by bank transfer or invoice?](/blog/rustdesk-pro-license-cost-how-to-pay)
|
||||
- Which currencies does RustDesk accept for payment?
|
||||
- [Can I upgrade my plan mid-term as I grow?](/blog/upgrade-rustdesk-license-mid-subscription)
|
||||
- [Does RustDesk offer a lifetime or perpetual license?](/blog/rustdesk-lifetime-perpetual-license)
|
||||
|
||||
Ready for numbers? Enter your required capacity in the live calculator or contact the team for larger plans and bank-transfer terms. [rustdesk.com/pricing](https://rustdesk.com/pricing)
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-29T16:16:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-for-enterprise
|
||||
draft: false
|
||||
@@ -12,6 +12,17 @@ tags:
|
||||
- enterprise
|
||||
- self-hosting
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Can RustDesk be mass-deployed across an enterprise fleet?'
|
||||
answer: 'Yes. RustDesk provides a Windows MSI for silent, unattended installation via msiexec, deployable through Group Policy (GPO), Microsoft Intune, an RMM, or packaging tools, and the custom client generator ships a client pre-configured to your own server.'
|
||||
- question: 'Does RustDesk have a REST API?'
|
||||
answer: 'Yes. RustDesk Server Pro exposes a REST API for bulk device management and scripting, so you can onboard, enumerate, and remove devices programmatically instead of only through the web console. Confirm current endpoints in the RustDesk documentation.'
|
||||
- question: 'Does RustDesk support Active Directory and SSO for enterprise identity?'
|
||||
answer: 'Yes. Server Pro includes LDAP/Active Directory and OIDC SSO from the Basic plan and up, so technicians authenticate against your existing identity source rather than a separate user list.'
|
||||
- question: 'Can enterprises keep RustDesk data on their own infrastructure?'
|
||||
answer: 'Yes — that is the core model. You self-host the ID/rendezvous, relay, console, and stored device data. Direct session traffic still flows between endpoints, so document endpoint routing alongside server placement.'
|
||||
- question: 'How does RustDesk pricing work for large fleets?'
|
||||
answer: 'RustDesk licenses per login-user and per managed-device, with unlimited concurrency on standard plans (only Customized V2 meters concurrency) and prorated upgrades. Size the counts against the current matrix at rustdesk.com/pricing.'
|
||||
metadata:
|
||||
description: 'RustDesk for enterprise: self-host on your own servers for data control, LDAP/AD, device-group access control, and no per-channel pricing.'
|
||||
keywords: 'RustDesk for enterprise, RustDesk enterprise deployment, AD-integrated remote support, enterprise RustDesk architecture'
|
||||
@@ -41,7 +52,7 @@ Before comparing feature matrices, make the deployment design explicit:
|
||||
| Availability | Capacity assumptions, monitoring, backups, recovery objectives, and multi-relay design |
|
||||
| Endpoint management | Supported OS versions, client packaging, configuration enforcement, and update SLA |
|
||||
| Security operations | Logging, retention, alerting, vulnerability response, and incident ownership |
|
||||
| Licensing | Required login users, managed devices, and any Customized V2 concurrency allowance |
|
||||
| Licensing | Required login users, managed devices, and any [Customized V2](https://rustdesk.com/pricing#custom2) concurrency allowance |
|
||||
|
||||
RustDesk supplies the remote-access components and enterprise controls; your architecture determines whether they meet the organization's availability, compliance, and operating requirements.
|
||||
|
||||
@@ -63,6 +74,8 @@ Operational monitoring must include unexpected registrations. If a new device ap
|
||||
|
||||
Self-hosting lets you choose the location and operator of the rendezvous, relay, console, and stored device data. Direct sessions still flow between endpoints, so server location alone does not guarantee in-country traffic or GDPR compliance. Document the complete [data flow and compliance controls](/blog/remote-desktop-data-sovereignty-gdpr).
|
||||
|
||||
Beyond location, Server Pro ships the controls a data-protection program actually uses: because usage telemetry is collected by the relay, running your own relay keeps that data on **your** relay rather than RustDesk (beyond the license check); **built-in audit-log rotation** caps how long connection, file-transfer, alarm, and console logs are kept; **granular access control** and a Control Role enforce least privilege; and you can **delete users, devices, and records** directly or through the REST API to service erasure and retention requests. The full breakdown is in [Remote Desktop Data Sovereignty & GDPR](/blog/remote-desktop-data-sovereignty-gdpr).
|
||||
|
||||
This is also a quiet reason cost-driven migrations happen. Many enterprise teams are not only frustrated by price; they are paying for a cloud service and feature bundle they do not fully use. Self-hosting inverts that: you provision what you need, and you're not renting someone else's data center as a mandatory middleman.
|
||||
|
||||
## Scale without a per-channel tax
|
||||
@@ -77,13 +90,17 @@ RustDesk charges **per login-user and per managed-device**, and upgrades can be
|
||||
|
||||
Enterprise remote access has to answer "who can reach which machines, and can we prove it." RustDesk's paid plans include **LDAP/SSO (OIDC) available from the Basic plan and up**, so you provision technician access against the identity source you already run rather than maintaining a parallel user list.
|
||||
|
||||
For structuring access, the self-hosted web console provides **device groups and a shared address book for per-user access control**. The custom client generator and identity features are plan-dependent; [check current availability](https://rustdesk.com/pricing).
|
||||
For structuring access, the self-hosted web console provides **device groups and a shared address book for per-user access control**. The custom client generator and identity features are available from the Basic plan and up; [check current availability](https://rustdesk.com/pricing).
|
||||
|
||||
## The honest caveat: someone has to run the server
|
||||
## Mass deployment and automation
|
||||
|
||||
Self-hosting is the whole value proposition — and it's also the cost. It means **someone on your side runs the server**: provision a host, open the right ports, configure TLS, and keep it patched. That's routine work for an enterprise IT team, but it is real work, and it never disappears.
|
||||
Rolling remote access onto thousands of endpoints by hand is a non-starter, so RustDesk supports the standard enterprise deployment paths. On Windows it ships an **MSI package** for silent, unattended installation via `msiexec /qn`, which you can push through **Group Policy (GPO), Microsoft Intune, an RMM, or any packaging tool**, with command-line parameters for install location, shortcuts, and options. Pair that with the [custom client generator](/blog/rustdesk-web-console-custom-client-generator-port-21114) so the client you deploy is pre-configured to your own server and settings out of the box, instead of requiring per-machine setup.
|
||||
|
||||
So be clear-eyed. If what you actually want is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to operate, RustDesk Server Pro is **[self-hosted by design](/blog/why-self-host-remote-desktop-software) and is not that**. The teams happiest with RustDesk are the ones who see running their own server as a feature — the same control that satisfies their compliance team is the control that puts a box on their maintenance schedule. If your organization values data sovereignty and predictable licensing over never touching infrastructure, that trade goes your way.
|
||||
For fleet operations, Server Pro exposes a **REST API** for bulk device management and scripting — enumerate devices, automate onboarding, and purge stale endpoints programmatically rather than clicking through the console one at a time. Confirm the current MSI parameters, GPO/Intune guidance, and API endpoints in the [RustDesk deployment and Server Pro documentation](https://rustdesk.com/docs/en/self-host/) for your version.
|
||||
|
||||
## Enterprise control, on your terms
|
||||
|
||||
At scale the case sharpens: the ID/relay, console, and stored data live inside your perimeter, wired to your identity system and your policies, with no vendor running the core. That is the posture procurement and security teams tend to ask for.
|
||||
|
||||
## Try it before you commit
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-09T08:32:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-for-linux
|
||||
draft: false
|
||||
@@ -14,11 +14,11 @@ tags:
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Does RustDesk work on Wayland?'
|
||||
answer: 'Yes, but Wayland support is still experimental. On Wayland, RustDesk captures the screen through PipeWire and the XDG desktop portal, which shows a consent dialog asking you to pick a display, and it works only for the active logged-in session. You cannot capture the Wayland login greeter, and unattended pre-login access still requires X11. For reliable unattended access on Linux, log in with an X11 (Xorg) session.'
|
||||
answer: 'Yes — RustDesk has among the strongest Wayland support of any remote-desktop tool, including multi-monitor sharing added in 1.4.3. On Wayland it captures the screen through PipeWire and the XDG desktop portal, which shows a consent dialog to pick a display — in most cases the choice is remembered, so you are not asked again — and works within the active logged-in session. That consent step is a Wayland security design shared by every screen-sharing app. For pre-login or fully unattended machines today, use the headless virtual-display setup (or an X11 session where a distribution still offers one, since several are moving to Wayland-only); full unattended Wayland capture is in active development (see github.com/rustdesk/rustdesk/pull/15420).'
|
||||
- question: 'Which package should I install on Linux?'
|
||||
answer: 'Use the .deb on Debian, Ubuntu and Linux Mint, the .rpm on Fedora, RHEL and openSUSE, the Flatpak from Flathub if you want a sandboxed build, or the portable AppImage on other distributions. The .deb and .rpm packages register and start a systemd service so RustDesk survives reboots; the Flatpak and AppImage do not by default.'
|
||||
answer: 'Use the .deb on Debian, Ubuntu and Linux Mint, the .rpm on Fedora, RHEL and openSUSE, the Flatpak from Flathub for a sandboxed, broadly compatible build, or the portable AppImage as a single-file fallback. The .deb and .rpm packages register and start a systemd service so RustDesk survives reboots; the Flatpak and AppImage do not by default.'
|
||||
- question: 'Why does my headless Linux box show a black screen?'
|
||||
answer: "With no monitor attached, X or Wayland never allocates a framebuffer, so there is nothing for RustDesk to capture and the viewer shows a black or waiting-for-image screen. Attach a dummy HDMI/DisplayPort plug, configure a virtual display such as xserver-xorg-video-dummy or VKMS, or enable RustDesk's experimental Linux headless mode so a virtual display is created for you."
|
||||
answer: "With no monitor attached, X or Wayland never allocates a framebuffer, so there is nothing for RustDesk to capture and the viewer shows a black or waiting-for-image screen. Attach a dummy HDMI/DisplayPort plug, configure a virtual display such as xserver-xorg-video-dummy or VKMS, or enable RustDesk's opt-in Linux headless mode so a virtual display is created for you."
|
||||
- question: 'Can I self-host the RustDesk server on Linux?'
|
||||
answer: 'Yes. The RustDesk server (the hbbs ID/rendezvous and hbbr relay processes) is built for Linux and is the standard way to run it. The free open-source community server runs indefinitely at no cost, and Server Pro adds a web console, device groups and a custom client generator on top. Both install on a plain Linux VM or bare-metal host.'
|
||||
metadata:
|
||||
@@ -42,20 +42,20 @@ RustDesk ships packages for every common Linux packaging format, so you rarely h
|
||||
| AppImage | Any distro, portable | No | May need `libfuse2` on recent Ubuntu; `chmod +x` then run |
|
||||
| AUR | Arch, Manjaro | Depends on package | Community-maintained (`rustdesk-bin`, `rustdesk-appimage`) |
|
||||
|
||||
The `.deb` and `.rpm` packages are the ones to use if you want RustDesk running as a background service that survives reboots — both register and start a systemd unit automatically. The Flatpak (`com.rustdesk.RustDesk` on [Flathub](https://flathub.org/apps/com.rustdesk.RustDesk)) is a sandboxed build that is convenient for desktop use but does not install a system service by default. The AppImage is the truly distribution-independent option: one file, no installation, runs almost anywhere — handy on distros RustDesk does not package directly, though on newer Ubuntu you may need to install `libfuse2` first.
|
||||
The `.deb` and `.rpm` packages are the ones to use if you want RustDesk running as a background service that survives reboots — both register and start a systemd unit automatically. The Flatpak (`com.rustdesk.RustDesk` on [Flathub](https://flathub.org/apps/com.rustdesk.RustDesk)) is a sandboxed build that is convenient for desktop use but does not install a system service by default. For a distribution RustDesk doesn't package directly, reach for the **Flatpak** first — because it bundles its own runtime it tends to be the most broadly compatible. The AppImage is a portable single-file alternative, but its compatibility is more hit-or-miss in practice (for example it may need `libfuse2` on recent Ubuntu).
|
||||
|
||||
In practice RustDesk is used across Ubuntu, Debian, Fedora, RHEL/CentOS, openSUSE, Arch and NixOS. If your distribution isn't on that list, the AppImage almost always works.
|
||||
In practice RustDesk is used across Ubuntu, Debian, Fedora, RHEL/CentOS, openSUSE, Arch and NixOS, with builds for **x86_64, ARM64 (aarch64) and ARM32 (ARMv7)** — so it runs on ARM boards and servers as well as standard PCs. If your distribution isn't on that list, the Flatpak from Flathub is the most broadly compatible option.
|
||||
|
||||
## X11 vs Wayland: the part that matters
|
||||
|
||||
This is the single most important thing to understand about RustDesk on Linux, because it determines whether remote control "just works" or leaves you staring at a black screen.
|
||||
This is the single most important thing to understand about RustDesk on Linux, because it determines whether remote control "just works" immediately or needs one small setup tweak first.
|
||||
|
||||
**X11 (Xorg) is the reliable path.** Under X11, RustDesk reads the framebuffer directly and injects input directly, so screen capture and mouse/keyboard control behave the way you'd expect, and RustDesk can dynamically detect monitor changes. If you want the least-surprising experience — especially for unattended access — log in with an Xorg session. On many display managers you can pick "Xorg"/"X11" from a gear menu on the login screen.
|
||||
**X11 (Xorg): the most direct capture path, where your distribution still offers it.** Under X11, RustDesk reads the framebuffer directly and injects input directly, so capture and mouse/keyboard control are as direct as it gets and monitor changes are detected dynamically. Many display managers still let you pick "Xorg"/"X11" from a gear menu at login. Keep in mind, though, that several distributions are moving to Wayland-only and retiring the X11 session — so treat X11 as a convenience where it happens to be available, not something to design your deployment around.
|
||||
|
||||
**Wayland works, but it is experimental.** RustDesk has had experimental Wayland support since version 1.2.0. Because Wayland compositors don't allow direct framebuffer access, RustDesk captures the screen through the `xdg-desktop-portal` service and [PipeWire](https://deepwiki.com/rustdesk/rustdesk/6.3.1-wayland-support), and injects input via the kernel's `uinput` module. Two consequences follow from that design:
|
||||
**Wayland: RustDesk has arguably the strongest support of any remote-desktop tool.** RustDesk has supported Wayland since version 1.2.0 and has kept extending it. Because Wayland compositors don't allow direct framebuffer access, RustDesk captures the screen through the `xdg-desktop-portal` service and [PipeWire](https://deepwiki.com/rustdesk/rustdesk/6.3.1-wayland-support), and injects input via the kernel's `uinput` module. Two consequences follow from Wayland's own design — and they apply to every Wayland screen-sharing tool, not just RustDesk:
|
||||
|
||||
- **Consent per connection.** The portal shows a dialog asking you to select which display to share. That is a deliberate Wayland security feature, not a RustDesk bug — a background app cannot silently start recording your screen. Portal v4 and newer support a "restore token" so you aren't re-prompted every single time, but the first share requires an on-screen click.
|
||||
- **Active session only.** Wayland capture is tied to the logged-in graphical session. You cannot capture the Wayland login greeter, and monitor changes aren't detected mid-session the way they are on X11. Remote access to the login screen still requires X11.
|
||||
- **Active session only.** Wayland capture is tied to the logged-in graphical session. Capturing the Wayland login greeter isn't supported yet — it's in active development ([PR #15420](https://github.com/rustdesk/rustdesk/pull/15420)) — and monitor changes aren't detected mid-session the way they are on X11. For pre-login access today, use the headless/virtual-display configuration below, or an X11 session on distributions that still provide one.
|
||||
|
||||
Wayland support keeps improving — RustDesk 1.4.3 (October 2025) [added multi-monitor sharing for Wayland](https://ubuntuhandbook.org/index.php/2025/10/rustdesk-released-1-4-3-with-multi-monitor-for-wayland-virtual-mouse/), for example. But if you connect and see a black screen on a Wayland box, that is almost always the portal/PipeWire path not being satisfied. Our dedicated write-up on [RustDesk connected but waiting for image](/blog/rustdesk-connected-waiting-for-image) walks through the Wayland black-screen case specifically.
|
||||
|
||||
@@ -65,9 +65,9 @@ Unattended access means connecting to a machine with nobody sitting in front of
|
||||
|
||||
1. Install via `.deb` or `.rpm` so the systemd service is registered, or click **Enable Service** in the app.
|
||||
2. In RustDesk, set a strong **permanent password** under the connection settings (and ideally enable two-factor authentication).
|
||||
3. Log the machine into an **X11 session** if you need access before or across user logins — Wayland's consent-per-connect model makes true unattended capture awkward.
|
||||
3. For access before or across user logins, use the headless virtual-display configuration below — or an X11 session where your distribution still offers one. Capturing the Wayland greeter is a platform gap RustDesk is actively closing ([PR #15420](https://github.com/rustdesk/rustdesk/pull/15420)), not a RustDesk shortcoming.
|
||||
|
||||
The honest caveat: unattended access on Wayland is genuinely harder than on X11 because the portal is designed to require a human to approve screen sharing. If unattended reliability matters, choose X11 for that machine. This isn't unique to RustDesk; every Wayland screen-sharing tool wrestles with the same portal model.
|
||||
One Wayland reality to plan for: because the portal is designed to require a human to approve screen sharing, fully unattended capture is harder on Wayland than on X11 — for every screen-sharing tool, not just RustDesk. RustDesk is actively working to close that gap ([unattended Wayland is in active development](https://github.com/rustdesk/rustdesk/pull/15420)); until it lands, cover pre-login or hands-off machines with the headless virtual-display setup — or an X11 session where your distribution still offers one, keeping in mind that X11 is being retired across many distros.
|
||||
|
||||
## Headless Linux: servers with no monitor
|
||||
|
||||
@@ -77,7 +77,7 @@ Three ways to give it something to render:
|
||||
|
||||
- **A dummy plug** — a cheap physical HDMI/DisplayPort "headless" dongle that makes the GPU think a monitor is attached.
|
||||
- **A virtual display driver** — `xserver-xorg-video-dummy` on X11, or a kernel-level option like VKMS.
|
||||
- **RustDesk's experimental headless mode** — enable it with `sudo rustdesk --option allow-linux-headless Y`. Per the [Headless Linux Support wiki](https://github.com/rustdesk/rustdesk/wiki/Headless-Linux-Support) it is disabled by default, tested mainly on Ubuntu with GNOME, and expects packages like `xserver-xorg-video-dummy` and `lightdm`. You can fetch the machine's ID with `sudo rustdesk --get-id` and set a password with `sudo rustdesk --password <password>`.
|
||||
- **RustDesk's opt-in headless mode** — enable it with `sudo rustdesk --option allow-linux-headless Y`. Per the [Headless Linux Support wiki](https://github.com/rustdesk/rustdesk/wiki/Headless-Linux-Support) it is disabled by default, tested mainly on Ubuntu with GNOME, and expects packages like `xserver-xorg-video-dummy` and `lightdm`. You can fetch the machine's ID with `sudo rustdesk --get-id` and set a password with `sudo rustdesk --password <password>`.
|
||||
|
||||
Headless mode is still rough around the edges, so treat it as "works, with care" rather than turnkey.
|
||||
|
||||
@@ -87,8 +87,8 @@ Everything above is the _client_. The other half of RustDesk's Linux story is th
|
||||
|
||||
You have two options. The free, open-source **community server** runs indefinitely at no cost and covers the core connect-and-relay function. **RustDesk Server Pro** adds a self-hosted web console, device groups, a shared address book, a custom-branded client generator, and [LDAP/Active Directory and OIDC SSO](/blog/rustdesk-active-directory-ldap-sso). You are not forced into Docker either — see [running Server Pro without Docker](/blog/rustdesk-server-pro-without-docker) for a plain-VM or bare-metal install. If you're sizing hardware for a large fleet, [self-hosting hardware at scale](/blog/self-host-rustdesk-server-hardware-at-scale) has the capacity planning.
|
||||
|
||||
One honest note on self-hosting, the same as everywhere in RustDesk's docs: the free community server and Server Pro are yours to run, patch, and secure. There's no managed NOC watching it for you. That ownership is the whole point — it's also real operational work, and worth being clear-eyed about before you commit. (Server Pro's license also needs an outbound path to rustdesk.com to activate and stay licensed.)
|
||||
One note on self-hosting: the free community server and Server Pro are yours to run, patch, and secure. The hardware requirements are low and, once it is set up, upkeep is light — and RustDesk support can help if a question comes up. That ownership is the whole point. (Server Pro's license also needs an outbound path to rustdesk.com to activate and stay licensed.)
|
||||
|
||||
## Getting started
|
||||
|
||||
Install the package for your distro, log into an Xorg session if you want the smoothest experience, set a permanent password for unattended access, and — if data sovereignty is your reason for being here — stand up the free community server. For current plan details, [rustdesk.com/pricing](https://rustdesk.com/pricing) is the source of truth, and [sales@rustdesk.com](mailto:sales@rustdesk.com) can talk through Server Pro. Want to see it working first? [See RustDesk in action](/blog/see-rustdesk-in-action).
|
||||
Install the package for your distro, set a permanent password for unattended access, and — if data sovereignty is your reason for being here — stand up the free community server. For current plan details, [rustdesk.com/pricing](https://rustdesk.com/pricing) is the source of truth, and [sales@rustdesk.com](mailto:sales@rustdesk.com) can talk through Server Pro. Want to see it working first? [See RustDesk in action](/blog/see-rustdesk-in-action).
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-06-30T19:07:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-for-mac
|
||||
draft: false
|
||||
@@ -69,7 +69,7 @@ Unattended access lets you connect to a Mac when nobody's there to click "accept
|
||||
|
||||
For deploying across many Macs, RustDesk provides a scriptable path. Per the [macOS auto-start service setup wiki](<https://github.com/rustdesk/rustdesk/wiki/macOS-Auto%E2%80%90Start-Service-Setup-(for-Remote---MDM-Deployment)>), an `install_service.sh` script installs RustDesk (or your custom-branded client) as a service without needing the GUI **Install** button, creating a LaunchDaemon at `/Library/LaunchDaemons/com.carriez.RustDesk_service.plist` and a LaunchAgent at `/Library/LaunchAgents/com.carriez.RustDesk_server.plist`. The daemon starts at boot; the agent starts at the login-window session and persists through login.
|
||||
|
||||
The honest catch for fleet admins: **that script does not grant the privacy permissions.** Screen Recording, Accessibility and Input Monitoring must still be provisioned separately — in a managed environment, that means shipping an MDM **PPPC** (Privacy Preferences Policy Control) profile so the permissions are pre-approved. Skip that step and the service will be running but remote control won't work. For the full walk-through beyond macOS specifics, see the [unattended access setup guide](/blog/rustdesk-unattended-access-setup).
|
||||
One thing to plan for: **that script does not grant the privacy permissions.** Screen Recording, Accessibility and Input Monitoring must still be provisioned separately — in a managed environment, that means shipping an MDM **PPPC** (Privacy Preferences Policy Control) profile so the permissions are pre-approved. Skip that step and the service will be running but remote control won't work. For the full walk-through beyond macOS specifics, see the [unattended access setup guide](/blog/rustdesk-unattended-access-setup).
|
||||
|
||||
## Connecting to your own server
|
||||
|
||||
@@ -77,7 +77,7 @@ The reason many people choose RustDesk on macOS over a proprietary tool is the s
|
||||
|
||||
If your workflow crosses desktop and mobile devices, check the separate [Android and iOS control matrix](/blog/rustdesk-remote-control-android-ios), because mobile hosting and control capabilities are not symmetric.
|
||||
|
||||
That's also the honest trade-off worth naming: self-hosting means _you_ run and secure that server. There's no managed uptime SLA unless you build one. For a lot of teams — particularly anyone with data-residency requirements — that control is exactly the point; for others, a managed option is a more comfortable fit. Both are legitimate.
|
||||
The trade worth naming: self-hosting means _you_ run and secure that server — a modest task, given the low hardware requirements and light upkeep. For teams with data-residency requirements especially, that control is exactly the point, and RustDesk support is there if you need it.
|
||||
|
||||
## Getting started
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-05T19:40:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-for-msps
|
||||
draft: false
|
||||
@@ -12,6 +12,18 @@ tags:
|
||||
- MSP
|
||||
- self-hosting
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Can RustDesk consolidate multiple MSP remote-support tools?'
|
||||
answer: 'Yes. RustDesk aims to replace a pile of separate tools with one self-hosted, open-source, brandable platform, giving you a single console, a custom-branded client generator, and per-user access control instead of separate consoles and contracts.'
|
||||
- question: 'How does RustDesk license for MSPs?'
|
||||
answer: 'You pay per login-user (your technicians) and per managed-device (the machines you support), and standard plans include unlimited concurrent connections so several techs can run sessions at once without buying channels. Customized V2 limits and prices concurrency separately; see rustdesk.com/pricing.'
|
||||
- question: 'Can I white-label or brand the RustDesk client?'
|
||||
answer: 'Yes. RustDesk includes a custom-branded client generator so clients install a tool configured for your service. Custom client generation and identity features are available from the Basic plan and up, so verify the current matrix before relying on them.'
|
||||
- question: 'Is RustDesk self-hosted, and who runs the server?'
|
||||
answer: 'RustDesk Server Pro is self-hosted: the ID/rendezvous server, relay, console, and stored deployment data run on infrastructure you control. Someone on your side provisions the host, opens ports, sets up TLS, and patches it — routine infrastructure work for an MSP, and light once it is set up.'
|
||||
- question: 'How should an MSP start evaluating RustDesk?'
|
||||
answer: 'A common path is to start with the free community server on a test VM or small internal host, validate a representative client workflow, then decide whether the Pro features are worth adding. You can also email sales@rustdesk.com to ask about current evaluation terms.'
|
||||
|
||||
metadata:
|
||||
description: 'RustDesk for MSPs: a self-hosted ScreenConnect/TeamViewer alternative — consolidate remote support with branding, access control, and plan-based concurrency.'
|
||||
keywords: 'RustDesk for MSPs, self-hosted remote support for MSPs, white label remote desktop, ScreenConnect alternative, TeamViewer alternative for MSPs, open source remote support tool, AnyDesk alternative, per-technician remote desktop licensing'
|
||||
@@ -43,7 +55,7 @@ Here is how that maps against the tools MSPs commonly consolidate away from:
|
||||
| ------------------- | ----------------------------- | --------------------------------------------------------------------------------- |
|
||||
| Hosting | Vendor cloud | Self-hosted (on-prem or your VPS) |
|
||||
| Source | Closed | Open source (AGPL) core |
|
||||
| Concurrent sessions | Often capped / per-channel | Unlimited on standard plans; limited on Customized V2 |
|
||||
| Concurrent sessions | Often capped / per-channel | Unlimited on standard plans; limited on [Customized V2](https://rustdesk.com/pricing#custom2) |
|
||||
| Licensing basis | Per seat / per channel | [Per login-user + per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) |
|
||||
| Session data path | Through vendor infrastructure | Server-side services on infrastructure you control |
|
||||
| Branding | Add-on or unavailable | Custom-branded client generator |
|
||||
@@ -60,7 +72,7 @@ You pay per login-user (your technicians) and per managed-device (the machines y
|
||||
|
||||
RustDesk ships the pieces an MSP actually needs to operate at scale: a self-hosted **[web console](/blog/rustdesk-web-console-custom-client-generator-port-21114)**, a **custom-branded client generator**, and **[device groups plus a shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book)** for per-user access control. **[LDAP/SSO](/blog/rustdesk-active-directory-ldap-sso) (OIDC) is available from the Basic plan and up.**
|
||||
|
||||
The branded client matters because clients install a tool configured for your service. Access control can scope technicians to assigned device groups. Custom client generation and identity features are plan-dependent, so verify the current matrix before relying on them.
|
||||
The branded client matters because clients install a tool configured for your service. Access control can scope technicians to assigned device groups. Custom client generation and identity features are available from the Basic plan and up, so verify the current matrix before relying on them.
|
||||
|
||||
## Control over server-side data location
|
||||
|
||||
@@ -68,11 +80,9 @@ Self-hosting gives an MSP control over rendezvous, relay, console, and stored de
|
||||
|
||||
It also scales beyond proof-of-concept. RustDesk publishes large-fleet planning guidance for teams that need to support bigger estates; validate the rollout against your concurrency, relay, and operating model before treating any sizing figure as universal.
|
||||
|
||||
## The honest caveat: someone has to run the server
|
||||
## Build the practice on your own infrastructure
|
||||
|
||||
Self-hosting is the whole point — and it is also the trade-off. **Someone on your side runs the server.** You provision a host, open the right ports, set up TLS, and patch it over time. That is normal infrastructure work for an MSP (arguably you do this for clients every day), but it is real work.
|
||||
|
||||
If what you actually want is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run and no patching to own, be clear-eyed: **RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-desktop-software), and it is not that.** The upside — control, no concurrent cap, no vendor cloud, no per-channel bill — comes _because_ you host it, not in spite of it. A common evaluation path is simple: start with the free community server on a test VM or small internal host, validate a representative client workflow, then decide whether the Pro features are worth adding.
|
||||
Self-hosting lets an MSP keep every client's coordination, branding, and device data on servers it operates — one tool, no per-technician cloud rental, no outsider in the session path. That is control you can build a business on.
|
||||
|
||||
## Try it without a sales call
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-09T12:11:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-lifetime-perpetual-license
|
||||
draft: false
|
||||
title: 'Does RustDesk Offer a Lifetime License?'
|
||||
excerpt: "RustDesk's public Server Pro pricing is term-based rather than lifetime. Confirm current annual or multi-year purchase options before budgeting."
|
||||
excerpt: "RustDesk Server Pro is term-based, not lifetime. Annual and multi-year terms are both available (multi-year via sales) — here's what to confirm before budgeting."
|
||||
image: ~/assets/images/blog/rustdesk-lifetime-perpetual-license-og.png
|
||||
category: Pricing
|
||||
tags:
|
||||
@@ -16,15 +16,15 @@ faq:
|
||||
- question: 'Does RustDesk offer a lifetime or perpetual license?'
|
||||
answer: 'The public Server Pro pricing is term-based and does not list a lifetime or perpetual license. Check the current pricing page or written sales terms before purchase.'
|
||||
- question: 'Can I buy RustDesk for multiple years up front?'
|
||||
answer: 'Do not assume a specific multi-year limit or discount. Ask RustDesk to confirm the available term, per-year rate, renewal date, and refund or cancellation conditions in writing.'
|
||||
answer: 'Yes. Multi-year terms are available — contact sales@rustdesk.com to arrange one. Confirm the available term, per-year rate, renewal date, and refund or cancellation conditions in writing.'
|
||||
- question: 'Can I self-host RustDesk Server without a Server Pro license?'
|
||||
answer: 'Yes. The open-source client and community ID and relay server have their own open-source terms. Server Pro is the term-licensed commercial offering for centralized administration and enterprise features.'
|
||||
metadata:
|
||||
description: "RustDesk's public Server Pro pricing is term-based rather than lifetime. Confirm current annual or multi-year purchase options before budgeting."
|
||||
description: "Does RustDesk offer a lifetime license? No — pricing is term-based, but annual and multi-year terms are available. Contact sales for multi-year; what procurement should confirm."
|
||||
keywords: 'RustDesk lifetime license, RustDesk perpetual license, RustDesk multi-year license, RustDesk license term'
|
||||
---
|
||||
|
||||
RustDesk's public Server Pro pricing is term-based and does not list a lifetime or perpetual license. Confirm any multi-year option and its conditions before budgeting.
|
||||
RustDesk's public Server Pro pricing is term-based and does not include a lifetime or perpetual license. Annual and multi-year terms are both available — multi-year is arranged through [sales@rustdesk.com](mailto:sales@rustdesk.com) — so confirm the term and its conditions before budgeting.
|
||||
|
||||
## Lifetime and multi-year are not the same
|
||||
|
||||
@@ -34,12 +34,12 @@ The open-source components are separate from Server Pro. You can run the communi
|
||||
|
||||
## What procurement should confirm
|
||||
|
||||
Use the current [pricing page](https://rustdesk.com/pricing) for standard plans. If your organization wants a longer term, request written confirmation of:
|
||||
Use the current [pricing page](https://rustdesk.com/pricing) for standard annual plans. If your organization wants a multi-year term, contact [sales@rustdesk.com](mailto:sales@rustdesk.com) and request written confirmation of:
|
||||
|
||||
- start and end dates;
|
||||
- covered plan and features;
|
||||
- login-user and managed-device allowances;
|
||||
- any Customized V2 concurrency allowance;
|
||||
- any [Customized V2](https://rustdesk.com/pricing#custom2) concurrency allowance;
|
||||
- total and per-year price;
|
||||
- treatment of mid-term upgrades;
|
||||
- renewal, cancellation, refund, and transfer conditions.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-07T16:17:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-not-connecting-troubleshooting
|
||||
draft: false
|
||||
@@ -22,6 +22,8 @@ faq:
|
||||
answer: 'RustDesk first tries a direct peer-to-peer link by punching through NAT. If that fails, traffic falls back through the relay server so the session still works, just with more latency. You can force relay mode to sidestep flaky NAT traversal, but relay throughput matters, which is a reason to self-host rather than lean on the public server.'
|
||||
- question: 'Should I stop using the public RustDesk server?'
|
||||
answer: 'The public rendezvous and relay servers are shared and offered without a performance guarantee, so under load they can be slow or refuse new sessions. If connections are unreliable, self-hosting your own server on a VPS or local machine gives you dedicated capacity, a stable key, and full control. The community server is free to run indefinitely.'
|
||||
- question: 'RustDesk Server Pro says the license is "already in use by another machine" — how do I move it?'
|
||||
answer: 'A Server Pro license binds to one server (the hbbs component; the relay hbbr needs no license). After a reinstall, migration, or hardware change, log in to the self-service license portal at rustdesk.com/self-host/account/ with the email you used on the payment page when you bought the license — if you no longer know which email that was, contact support@rustdesk.com — then unbind the old machine and set the license in the new server web console, where it re-registers automatically. If you run Pro in Docker and hit this on every restart, give the containers a stable hostname or use host network mode so the license is not tied to a random container ID.'
|
||||
|
||||
metadata:
|
||||
description: 'RustDesk not connecting? Fix ID/relay server settings, firewall and NAT, key mismatch after a reinstall, direct vs relay, and public server overload.'
|
||||
@@ -105,8 +107,6 @@ The durable fix is to **self-host**. Running your own server on a small VPS or a
|
||||
|
||||
Version drift causes connection failures on its own. Older clients and servers can disagree on protocol and key formats, so update **both clients and the server** to current releases before deeper debugging. Several "won't connect" reports resolve at this step alone.
|
||||
|
||||
## An honest caveat
|
||||
## A server you control is one you can fix
|
||||
|
||||
Not every connection problem is on RustDesk's side. Symmetric NAT, deep-packet-inspection firewalls, and captive-portal networks can block peer-to-peer traffic in ways no client setting overrides — in those environments, forcing relay through a server _you_ control is the realistic answer, not direct P2P. And self-hosting means you own the uptime: a misconfigured reverse proxy or a lapsed certificate becomes your problem to fix, not a vendor's. For most teams that trade is worth it for the control and privacy; go in clear-eyed about it.
|
||||
|
||||
Ready to get off the shared server? Spin up the free community server, point your clients at it, and you're independent — see [why self-hosting is worth it](/blog/why-self-host-remote-desktop-software), or for commercial capabilities check [rustdesk.com/pricing](https://rustdesk.com/pricing) or email sales@rustdesk.com.
|
||||
When the coordination runs on your own host, a connection failure is yours to diagnose and yours to resolve — no shared public server to wait on, no black box between endpoints. That is the durable fix behind the steps above.
|
||||
+1
-1
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-26T15:16:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-per-user-access-control-device-groups-shared-address-book
|
||||
draft: false
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-08T11:27:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-pro-license-cost-how-to-pay
|
||||
draft: false
|
||||
@@ -41,19 +41,19 @@ The reason there is no one-line answer is that RustDesk licensing is tied to usa
|
||||
|
||||
If you want to evaluate the paid features before committing, check the current evaluation path on [rustdesk.com/pricing](https://rustdesk.com/pricing) or email [sales@rustdesk.com](mailto:sales@rustdesk.com).
|
||||
|
||||
Payment is straightforward: use the current checkout flow shown on the pricing page. If your procurement process has billing or payment constraints, confirm the current options before you purchase.
|
||||
Payment is straightforward: use the current checkout flow shown on the pricing page. If your procurement process has billing or payment constraints, confirm the current options before you purchase. After you buy, you can retrieve invoices and manage renewals, upgrades, or a license move in the [self-service license portal](https://rustdesk.com/self-host/account/) — log in with the email you used on the payment page, or contact [support@rustdesk.com](mailto:support@rustdesk.com) if you no longer know which one.
|
||||
|
||||
It is also worth remembering the free/paid split. The RustDesk **client is open source and free**, and you can even self-host the basic relay/signal server at no license cost. The Pro license unlocks the Server Pro feature set (the management, control, and scale features aimed at businesses). So the cost question is really about Server Pro, not about using RustDesk at all.
|
||||
|
||||
## Who asks this
|
||||
|
||||
This question comes up most often from **IT admins, MSPs, and businesses** comparing RustDesk against tools like TeamViewer and AnyDesk, where renewal pricing has pushed teams to look for alternatives. Many are running a proof of concept and want a concrete number and a clear buying path before they take it to a manager.
|
||||
This question comes up most often from **IT admins, MSPs, and businesses** comparing RustDesk against tools like TeamViewer and AnyDesk after widely reported renewal price increases. Many are running a proof of concept and want a concrete number and a clear buying path before they take it to a manager.
|
||||
|
||||
## Related questions
|
||||
|
||||
- [Is the RustDesk client really free, and what do I get only with Pro?](/blog/case-for-open-source-remote-access)
|
||||
- [How does per-user versus per-device licensing work for my team size?](/blog/what-counts-as-a-managed-device)
|
||||
- [Can I self-host RustDesk Server for free instead of buying Pro?](/blog/see-rustdesk-in-action)
|
||||
- [Can I self-host RustDesk Server for free instead of buying Pro?](/blog/why-self-host-remote-desktop-software)
|
||||
- [Do you offer volume or annual pricing for MSPs and larger teams?](/blog/rustdesk-custom-quote-minimum-users-invoice-fees)
|
||||
- [What are the current evaluation terms for Server Pro?](/blog/rustdesk-server-pro-free-trial)
|
||||
- [Does RustDesk offer a lifetime or perpetual license?](/blog/rustdesk-lifetime-perpetual-license)
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-07T17:09:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-remote-control-android-ios
|
||||
draft: false
|
||||
@@ -15,7 +15,7 @@ faq:
|
||||
- question: 'Can I remotely control an Android phone with RustDesk?'
|
||||
answer: "Yes. On the Android device you start RustDesk's screen-capture service (which requires an on-screen consent prompt) and enable the RustDesk Input accessibility service so remote taps and swipes are injected. Screen sharing needs Android 6 or newer; sharing internal system audio needs Android 10 or newer. Some manufacturers restrict accessibility for sideloaded apps, so you may have to allow restricted settings first."
|
||||
- question: 'Can RustDesk control an iPhone or iPad?'
|
||||
answer: "No. As of 2026 RustDesk on iOS is controller-only: you can use an iPhone or iPad to control a remote computer, but you cannot view or control an iOS device from elsewhere. Apple's restrictive screen-recording and background APIs are the reason, and iOS host support remains a long-standing, unimplemented feature request. Do not expect to remote into an iPhone with RustDesk today."
|
||||
answer: "Not from any remote-desktop app — that's an iOS platform limit, not a RustDesk one. Apple's screen-recording and background restrictions don't let a third-party app be remotely controlled as a host, so no vendor offers true remote control into an iPhone or iPad. What RustDesk's iOS/iPadOS app does well is work as a controller: use an iPhone or iPad to control your Windows, macOS, Linux, and Android machines."
|
||||
- question: 'Can I use my phone to control my computer?'
|
||||
answer: 'Yes. The Android and iOS RustDesk apps work as full controller clients. You can connect from either to a Windows, macOS or Linux machine and control it with an on-screen touchpad or mouse mode. This is the most reliable mobile use case and works the same as the desktop client.'
|
||||
- question: 'Are the RustDesk mobile apps open source?'
|
||||
@@ -29,7 +29,7 @@ metadata:
|
||||
|
||||
"Can I remote into a phone?" is one of the most common questions RustDesk gets, and it deserves an honest answer rather than a marketing one. The short version: RustDesk can genuinely control an Android device, both mobile apps make excellent _controllers_ for your computers, and — the part people don't want to hear — you cannot currently remote into an iPhone or iPad. This guide explains exactly what works, what doesn't, and why, so you can plan around real capabilities instead of assumptions.
|
||||
|
||||
Both mobile apps are, like the rest of RustDesk, [open source](/blog/open-source-remote-desktop-software) under the AGPL. Android builds are available from the [official RustDesk GitHub releases](https://github.com/rustdesk/rustdesk/releases) and [F-Droid](https://f-droid.org/packages/com.carriez.flutter_hbb/) as `com.carriez.flutter_hbb`; the iOS controller is on the App Store. RustDesk is [not currently distributed through Google Play](/blog/rustdesk-and-remote-access-scams): it voluntarily unpublished the Android app in response to scam abuse. Same codebase, same auditable core.
|
||||
Both mobile apps are, like the rest of RustDesk, [open source](/blog/open-source-remote-desktop-software) under the AGPL. Android builds are available from the [official RustDesk GitHub releases](https://github.com/rustdesk/rustdesk/releases) and [F-Droid](https://f-droid.org/packages/com.carriez.flutter_hbb/) as `com.carriez.flutter_hbb`, with wide device coverage — arm64, arm32, and x86_64 builds, plus a universal APK; the iOS controller is on the App Store. RustDesk is [not currently distributed through Google Play](/blog/rustdesk-and-remote-access-scams): it voluntarily unpublished the Android app in response to scam abuse. Same codebase, same auditable core.
|
||||
|
||||
## The one-table summary
|
||||
|
||||
@@ -66,21 +66,21 @@ Now the honest limitations, because Android's security model imposes real ones:
|
||||
- **Reboots need a manual unlock.** After a restart the device usually has to be unlocked in person before control resumes.
|
||||
- **OEM restrictions.** On some manufacturers' builds, the **RustDesk Input** accessibility toggle is greyed out for sideloaded apps until you grant "restricted settings" (long-press the app icon → App info → allow restricted settings). Aggressive battery managers on certain OEMs can also kill the background service.
|
||||
|
||||
The practical takeaway: Android control is excellent for **attended support** — helping someone who is holding their phone — but it is not a reliable **set-and-forget unattended** solution the way a desktop is. Be honest with yourself about which one you need. (For desktops, the [unattended access setup guide](/blog/rustdesk-unattended-access-setup) covers the real thing.)
|
||||
The practical takeaway: Android control is excellent for **attended support** — helping someone who is holding their phone — while **set-and-forget unattended** access is a job the desktop host does best, because mobile operating systems restrict persistent background access. Match the platform to the job. (For desktops, the [unattended access setup guide](/blog/rustdesk-unattended-access-setup) covers the real thing.)
|
||||
|
||||
## Controlling an iOS device: the honest answer
|
||||
|
||||
Here's the part that gets asked constantly and answered vaguely elsewhere, so we'll be direct: **you cannot remotely view or control an iPhone or iPad with RustDesk.** The iOS app is a controller only — it connects _out_ to control your computers, but it cannot act as a host, share its screen, or be controlled from another device.
|
||||
Here's the part that gets asked constantly and answered vaguely elsewhere, so we'll be direct: **no remote-desktop app can remotely control an iPhone or iPad — RustDesk included.** On iOS the RustDesk app is a capable controller — it connects _out_ to control your computers — but Apple does not let any third-party app act as a remotely-controlled host on iOS.
|
||||
|
||||
The reason is Apple. iOS heavily restricts background execution, screen recording, and any form of synthetic input injection, which is why no third-party app offers true remote _control_ of an iPhone. This isn't a RustDesk oversight so much as a platform wall — iOS host support has been a repeatedly [requested feature on GitHub](https://github.com/rustdesk/rustdesk/discussions/4839) that remains unimplemented. Apple's broadcast APIs (ReplayKit) can in principle stream a screen, but full remote control of iOS from another device isn't something the OS permits to third parties.
|
||||
|
||||
So if your requirement is "remote into an iPhone," RustDesk is not the tool today, and we'd rather tell you that up front than let you discover it after setup. This limitation is not unique to RustDesk — it's the same wall every remote-desktop vendor hits on iOS, as noted in our [RustDesk vs AnyDesk](/blog/rustdesk-vs-anydesk) comparison.
|
||||
So if your requirement is specifically "remote into an iPhone," no current remote-desktop tool can do it — it's an iOS platform wall every vendor hits, not a RustDesk gap, as noted in our [RustDesk vs AnyDesk](/blog/rustdesk-vs-anydesk) comparison. We'd rather tell you that up front than let you discover it after setup.
|
||||
|
||||
## A note on privacy and self-hosting
|
||||
|
||||
Because the mobile apps are open source and speak the same protocol as the desktop client, you can point them at your own [self-hosted RustDesk server](/blog/why-self-host-remote-desktop-software) instead of the public network — so mobile sessions are brokered by infrastructure you control, ID and all. For remote-support workflows that touch personal devices, that data-sovereignty angle matters more than usual.
|
||||
|
||||
The honest caveat is the same as always: self-hosting means you run and secure that server yourself. It's the price of keeping session data on your own turf, and for many teams it's well worth it.
|
||||
The trade-off is the same as always: you run and secure that server yourself — a modest task given the low requirements — and for many teams, keeping session data on your own turf is well worth it.
|
||||
|
||||
## Getting started
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-26T08:29:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-reseller-partner-program
|
||||
draft: false
|
||||
@@ -51,8 +51,8 @@ This question comes mostly from MSPs, IT service providers, and regional distrib
|
||||
|
||||
- [Can I self-host RustDesk Server Pro for multiple clients on one server?](/blog/rustdesk-for-msps)
|
||||
- [How does RustDesk per-user vs. per-device licensing work?](/blog/rustdesk-pro-license-cost-how-to-pay)
|
||||
- What account ownership and renewal workflow should I confirm before buying for a client?
|
||||
- Do you offer volume or bulk discounts for large deployments?
|
||||
- [What account ownership and renewal workflow should I confirm before buying for a client?](/blog/upgrade-rustdesk-license-mid-subscription)
|
||||
- [Do you offer volume or bulk discounts for large deployments?](/blog/rustdesk-custom-quote-minimum-users-invoice-fees)
|
||||
- [Is there a RustDesk white-label or co-branding option?](/blog/rustdesk-web-console-custom-client-generator-port-21114)
|
||||
|
||||
Setting clients up on RustDesk? Review the current plans, then confirm the right billing and account workflow for your client setup at [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-09T10:47:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-scale-50000-200000-devices
|
||||
draft: false
|
||||
@@ -27,7 +27,7 @@ metadata:
|
||||
keywords: 'rustdesk scale 200000 devices, rustdesk 50000 devices, rustdesk self-hosted server scalability, rustdesk enterprise deployment, rustdesk server pro capacity, remote desktop for large fleets'
|
||||
---
|
||||
|
||||
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. This is a point-in-time internal production observation recorded on July 7, 2026, not a multi-day stability measurement.
|
||||
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. This is a point-in-time internal production observation, not a multi-day stability measurement.
|
||||
|
||||
The scope matters: this is a production observation, not a reproducible Server Pro benchmark. It was not independently audited and has no public monitoring dashboard or downloadable dataset. “Online endpoints” means devices reported online at that point in time, not two million simultaneous remote-control sessions. RustDesk is intentionally publishing this limited topology summary without host identifiers or network details. A Server Pro deployment may also have different database writes, audit activity, console use, policy processing, and relay traffic.
|
||||
|
||||
@@ -39,7 +39,7 @@ Yes, 200,000 online devices is a credible planning target: RustDesk's point-in-t
|
||||
|
||||
Scale questions like this 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 frequently their state changes, how many remote sessions run at once, and how much traffic uses the relay.
|
||||
|
||||
The public-server observation provides a RustDesk-reported reference point: more than two million online endpoints on a single 12-core, 32 GB machine at the recorded moment. It is useful first-party operational context, but readers cannot independently reproduce it from a public report and should not treat it as proof of a monitoring period or service-level target.
|
||||
The public-server observation is a RustDesk-reported reference point: more than two million online endpoints on a single 12-core, 32 GB machine at the recorded moment — useful first-party context for sizing, not a service-level guarantee.
|
||||
|
||||
For a Server Pro rollout, validate the parts that do not follow from that public-server figure. 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 can add load that endpoint presence alone does not measure.
|
||||
|
||||
@@ -57,8 +57,7 @@ This question typically comes from enterprises, [MSPs](/blog/rustdesk-for-msps),
|
||||
|
||||
- [How many concurrent sessions can a self-hosted RustDesk server handle?](/blog/rustdesk-concurrent-connections-limit)
|
||||
- What [server hardware](/blog/self-host-rustdesk-server-hardware-at-scale) do I need for a large RustDesk deployment?
|
||||
- Does RustDesk Server Pro support high availability or load balancing?
|
||||
- [How does RustDesk licensing work for tens of thousands of devices?](/blog/rustdesk-pro-license-cost-how-to-pay)
|
||||
- Can I migrate an existing TeamViewer or AnyDesk fleet to RustDesk?
|
||||
- [Can I migrate an existing TeamViewer or AnyDesk fleet to RustDesk?](/blog/self-hosted-teamviewer-alternative)
|
||||
|
||||
Planning a large-scale rollout? Reach out to the [RustDesk team](mailto:sales@rustdesk.com) to size a self-hosted deployment for your device count, performance requirements, and growth timeline.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-08T12:07:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-self-hosted-vs-cloud-saas-option
|
||||
draft: false
|
||||
@@ -16,7 +16,7 @@ faq:
|
||||
- question: 'Does RustDesk offer a cloud or SaaS-hosted option?'
|
||||
answer: 'No — RustDesk does not host the server for you. RustDesk Server Pro is a self-hosted solution only, with no SaaS or cloud-hosted option. You deploy and manage it on your own server infrastructure.'
|
||||
- question: 'Can I run RustDesk Server Pro on a cloud VM like AWS, Azure, or a VPS?'
|
||||
answer: 'Yes. Self-hosted means you run the server on infrastructure you control — an on-premises machine or a cloud VM such as a VPS, AWS, Azure, or GCP instance that you provision and administer. RustDesk supplies the software; hosting, uptime, and maintenance are your responsibility.'
|
||||
answer: 'Yes. Self-hosted means you run the server on infrastructure you control — an on-premises machine or a cloud VM such as a VPS, AWS, Azure, or GCP instance that you provision and administer. RustDesk supplies the software; you host it, and with low hardware requirements and light day-to-day upkeep, that is a modest responsibility.'
|
||||
- question: 'What is the difference between the free RustDesk OSS server and Server Pro?'
|
||||
answer: 'Both are self-hosted. The free open-source server covers core connectivity you can run indefinitely. Server Pro adds a web console, user and device management, device groups, a shared address book, a custom branded client generator, and identity features such as LDAP/AD and OIDC SSO.'
|
||||
- question: 'Does RustDesk offer a monthly Server Pro plan?'
|
||||
@@ -37,9 +37,9 @@ RustDesk Server Pro is self-hosted. There is no managed cloud or SaaS tier where
|
||||
|
||||
The distinction matters because it's different from how most remote-desktop tools you may be leaving — TeamViewer, AnyDesk, and similar products — are sold. Those are typically SaaS: the vendor runs the relay and rendezvous infrastructure, and you connect to their cloud. RustDesk's Server Pro flips that model. You get the server software and a license, and you stand up the service yourself.
|
||||
|
||||
In practice, "self-hosted" means you install the RustDesk server components (the rendezvous/ID server and relay server) on a host you own or rent, point your clients at it, and handle the usual operational duties: the operating system, networking and firewall rules, TLS certificates, backups, and updates. RustDesk provides the software; the hosting, uptime, and maintenance are on you.
|
||||
In practice, "self-hosted" means you install the RustDesk server components (the rendezvous/ID server and relay server) on a host you own or rent, point your clients at it, and handle the usual operational duties: the operating system, networking and firewall rules, TLS certificates, backups, and updates — mostly one-time setup, then light upkeep. RustDesk provides the software; the hosting is yours, and its low hardware requirements keep that a modest task.
|
||||
|
||||
This has real trade-offs. On the plus side, self-hosting gives you control of the ID/rendezvous, relay, console, and stored deployment data. Direct sessions still flow between endpoints, so endpoint location and routing remain part of any compliance or privacy assessment. The cost is operational: you need someone comfortable provisioning a server and keeping it patched. If you were hoping to buy a login and have everything "just work" in someone else's cloud, that specific offering does not exist for Server Pro today.
|
||||
This has real trade-offs. On the plus side, self-hosting gives you control of the ID/rendezvous, relay, console, and stored deployment data. Direct sessions still flow between endpoints, so endpoint location and routing remain part of any compliance or privacy assessment. The trade-off is operational: you need someone comfortable provisioning a server and keeping it patched — a light, mostly one-time task, and RustDesk support can help if you get stuck. If you were hoping to buy a login and have everything "just work" in someone else's cloud, that specific offering does not exist for Server Pro today.
|
||||
|
||||
If a fully managed, RustDesk-hosted service is a hard requirement for you, it's worth checking [rustdesk.com](https://rustdesk.com) for the latest, since product offerings can change over time. As of this writing, the answer from the team is clear: self-hosted only.
|
||||
|
||||
@@ -51,7 +51,7 @@ The free community server is different: it provides the core self-hosted ID and
|
||||
|
||||
## Who asks this
|
||||
|
||||
This question comes up constantly from IT admins, [MSPs](/blog/rustdesk-for-msps), and businesses evaluating RustDesk against TeamViewer or AnyDesk — often after trying a [free trial](/blog/rustdesk-server-pro-free-trial) and expecting a comparable cloud sign-up. Many phrase it as looking for "any cloud hosting option similar to the free trial," assuming the paid product is simply a hosted upgrade. It isn't: the free experience and the paid Server Pro are both built around infrastructure you run, not a vendor-operated cloud. Teams with the in-house ability to manage a server tend to see the self-hosted model as a feature rather than a limitation.
|
||||
This question comes up constantly from IT admins, [MSPs](/blog/rustdesk-for-msps), and businesses evaluating RustDesk against TeamViewer or AnyDesk — often after asking about a [free trial](/blog/rustdesk-server-pro-free-trial) and expecting a comparable cloud sign-up. Many phrase it as looking for "any cloud hosting option," assuming the paid product is simply a hosted upgrade. It isn't: the free experience and the paid Server Pro are both built around infrastructure you run, not a vendor-operated cloud. Teams with the in-house ability to manage a server tend to see the self-hosted model as a feature rather than a limitation.
|
||||
|
||||
## Related questions
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-29T19:30:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-server-pro-free-trial
|
||||
draft: false
|
||||
@@ -51,6 +51,6 @@ This question comes overwhelmingly from IT admins, MSPs, and businesses evaluati
|
||||
- [How much does RustDesk Server Pro cost, and how does per-user vs. per-device licensing work?](/blog/rustdesk-pro-license-cost-how-to-pay)
|
||||
- [What features are included in the Basic plan versus higher tiers?](/blog/rustdesk-custom-quote-minimum-users-invoice-fees)
|
||||
- [What is a custom client, and which licenses include it?](/blog/rustdesk-web-console-custom-client-generator-port-21114)
|
||||
- [Can I self-host RustDesk Server for free using the open-source version?](/blog/see-rustdesk-in-action)
|
||||
- [Can I self-host RustDesk Server for free using the open-source version?](/blog/open-source-remote-desktop-software)
|
||||
|
||||
Ready to evaluate it? Email [sales@rustdesk.com](mailto:sales@rustdesk.com) and ask for the current evaluation terms that match your setup.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-28T16:50:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-server-pro-offline-air-gapped
|
||||
draft: false
|
||||
@@ -16,7 +16,7 @@ faq:
|
||||
- question: 'Can RustDesk Server Pro run offline or air-gapped?'
|
||||
answer: 'No. The licensed Server Pro must keep an outbound connection to rustdesk.com to validate its license while it runs, so a fully air-gapped, never-phones-home deployment is not supported. You can still lock egress down tightly and route it through a proxy.'
|
||||
- question: 'Does RustDesk Server Pro need a permanent internet connection?'
|
||||
answer: 'It needs ongoing outbound access to rustdesk.com for license validation. Remote sessions themselves are brokered by your own self-hosted relay and ID (rendezvous) servers, but the Pro license will not stay valid without that outbound path.'
|
||||
answer: 'It needs ongoing outbound access to rustdesk.com for license validation, but not a literally uninterrupted one. The server checks in over port 443 about once a day and, if a check fails, keeps retrying until it succeeds or roughly seven days pass — so a brief outage is tolerated, but a server cut off from rustdesk.com for longer than that grace window stops validating. Remote sessions themselves are brokered by your own self-hosted relay and ID (rendezvous) servers.'
|
||||
- question: 'Which outbound access does an isolated RustDesk Server Pro deployment need?'
|
||||
answer: 'Allow outbound HTTPS from the server to rustdesk.com for license validation (and for custom-client provisioning if you use it). A proxy is supported, so the rest of the network can stay locked down. Confirm the exact domains and ports in the RustDesk docs.'
|
||||
- question: 'Is there a fully air-gapped RustDesk licensing option?'
|
||||
@@ -30,7 +30,7 @@ No — a self-hosted RustDesk Server Pro deployment is not designed to run fully
|
||||
|
||||
## The short answer
|
||||
|
||||
Server Pro needs an outbound path to rustdesk.com for license validation, and that requirement does not go away once the server is running. Your ID and relay services remain self-hosted; direct sessions flow between endpoints and relayed sessions use your relay. The license itself will not remain valid on a server that can never reach rustdesk.com. You can keep the network tightly restricted: a proxy is supported, so in practice you allow the required outbound HTTPS path and lock down the rest.
|
||||
Server Pro needs an outbound path to rustdesk.com for license validation, and that requirement does not go away once the server is running. In practice the check is periodic rather than constant: the server contacts rustdesk.com over port 443 roughly once a day, and if a check fails it retries until it either succeeds or about seven days elapse — after which the license stops validating. That built-in grace window means a short internet outage will not immediately break your deployment, but a permanently offline server will. Your ID and relay services remain self-hosted; direct sessions flow between endpoints and relayed sessions use your relay. You can keep the network tightly restricted: a proxy is supported, so in practice you allow the required outbound HTTPS path and lock down the rest.
|
||||
|
||||
## In detail
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-30T13:50:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-server-pro-without-docker
|
||||
draft: false
|
||||
@@ -15,6 +15,12 @@ author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Can I run RustDesk Server Pro without Docker?'
|
||||
answer: 'No, you are not forced to use Docker. RustDesk Server Pro ships as plain binaries you can install directly on a VM or bare-metal server (for example a Debian box) using install.sh, and you can even install offline by downloading the release files first. The one hard requirement: the server must be able to reach https://rustdesk.com to activate its license — the license cannot be activated fully offline, though a proxy is supported.'
|
||||
- question: 'How do I install RustDesk Server Pro on Debian or Ubuntu without Docker?'
|
||||
answer: 'Download the Server Pro release for your architecture and run the bundled install.sh on the host to set up the hbbs (ID/rendezvous) and hbbr (relay) services directly under systemd — no container runtime needed. Open only the ports you use (native clients need TCP 21115-21117 and UDP 21116; the Pro API/console is on 21114 and web/WebSocket on 21118-21119) and front the console with an HTTPS reverse proxy on 443.'
|
||||
- question: 'Can I activate the license behind a proxy or without direct internet access?'
|
||||
answer: 'The server must reach https://rustdesk.com to activate and keep its license, but you do not need to expose it directly: an outbound HTTP/HTTPS proxy is supported for the license check. A fully air-gapped, offline-forever activation is not available.'
|
||||
- question: 'How do I move a non-Docker Server Pro license to a new VM?'
|
||||
answer: 'A Server Pro license binds to one server (the hbbs component; the relay hbbr needs no license). Log in to the self-service portal at rustdesk.com/self-host/account/ with the email you used on the payment page, unbind the old machine, then set the license on the new server and let it re-register. If you no longer know which email you used, contact support@rustdesk.com.'
|
||||
|
||||
metadata:
|
||||
description: "No, Docker isn't required for RustDesk Server Pro. Install on a plain VM or bare metal, even offline — but the license must reach rustdesk.com to activate."
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-08T11:04:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-unattended-access-setup
|
||||
draft: false
|
||||
@@ -60,7 +60,7 @@ Once RustDesk runs as a service, it loads before anyone logs in, which is what l
|
||||
| -------- | -------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
| Windows | Install, enable Service + Start on boot | Portable exe drops on logout/UAC; use the installer |
|
||||
| macOS | Install, set permanent password, grant permissions | Screen Recording and Accessibility must be granted; login-screen capture needs the helper installed |
|
||||
| Linux | Install the service package; prefer X11/Xorg | Wayland capture is experimental and needs an active session |
|
||||
| Linux | Install the service package | Wayland needs an active session; for pre-login use the headless virtual-display setup, or X11 where a distro still offers one |
|
||||
| Android | Set permanent password; enable capture | Screen must be awake; enable Developer-options screen-share settings |
|
||||
|
||||
### Windows
|
||||
@@ -73,7 +73,7 @@ macOS gates screen capture and input behind permissions. After installing, open
|
||||
|
||||
### Linux
|
||||
|
||||
Install RustDesk so its service component runs at boot. For unattended reliability, prefer an **X11/Xorg** session: Wayland capture is experimental, prompts for consent on each connect, and only works inside an active session — awkward for a machine that may sit at the greeter. See [RustDesk for Linux](/blog/rustdesk-for-linux) for the details.
|
||||
Install RustDesk so its service component runs at boot. For a machine that sits at the login greeter, Wayland can't capture the greeter yet — a Wayland design (not a RustDesk limit) that RustDesk is actively working to close ([PR #15420](https://github.com/rustdesk/rustdesk/pull/15420)). On a headless box, use the virtual-display configuration; on a desktop, an X11/Xorg session still handles it where a distribution provides one, though several are moving to Wayland-only. See [RustDesk for Linux](/blog/rustdesk-for-linux) for the details.
|
||||
|
||||
## Step 3: Deploy at scale with a pre-configured client
|
||||
|
||||
@@ -89,8 +89,6 @@ Unattended access is a standing door into a machine, so treat the credentials se
|
||||
- **Two-factor authentication** and, on Pro, **access controls** so only authorized accounts can connect. Our write-up on [per-user access control and device groups](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book) covers scoping who reaches what.
|
||||
- **Self-host the server-side services** when you need control of rendezvous, relay, console, and stored deployment data. Endpoint credentials remain an endpoint-security responsibility. Because the [client is open source under AGPL](/blog/open-source-remote-desktop-software), its authentication implementation can be reviewed.
|
||||
|
||||
## An honest caveat
|
||||
## Unattended access you actually control
|
||||
|
||||
Unattended access trades convenience for exposure: a machine that answers any time is a machine an attacker would love to answer to. That's a reason to insist on a strong, unique password and 2FA, not the OS login, and to prefer a **server you control** over the shared public one. Self-hosting also means the service's uptime is now yours to maintain — but in exchange, no third party can silently change the rules on who reaches your fleet. For most admins that ownership is the whole point.
|
||||
|
||||
Getting started costs nothing: run the **free community server**, set a permanent password, install the service, and you have unattended access on infrastructure you own. For the Custom Client Generator, access controls, and other commercial features, see [rustdesk.com/pricing](https://rustdesk.com/pricing) or email sales@rustdesk.com — and if you'd like to see the workflow first, browse [RustDesk in action](/blog/see-rustdesk-in-action).
|
||||
Point an always-on fleet at a server you run and the standing access to those machines stays brokered by hardware you own, not a cloud you rent. For permanent access, keeping that path in your own hands is worth the short setup.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-30T13:46:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-unknown-devices-antivirus-scanning
|
||||
draft: false
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-26T18:00:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-vs-anydesk
|
||||
draft: false
|
||||
@@ -15,6 +15,15 @@ author: RustDesk Team
|
||||
metadata:
|
||||
description: "RustDesk vs AnyDesk compared in depth: features, OS support, security (including AnyDesk's 2024 security incident), pricing models, and honest pros/cons."
|
||||
keywords: 'RustDesk vs AnyDesk, AnyDesk vs RustDesk, RustDesk AnyDesk comparison, self-hosted AnyDesk comparison'
|
||||
faq:
|
||||
- question: 'Is RustDesk a free, open-source alternative to AnyDesk?'
|
||||
answer: "Yes. RustDesk's core client is open source under the AGPL and its community server is free to self-host with no expiry. Paid Server Pro adds centralized management, licensed by login users and managed devices."
|
||||
- question: 'Can RustDesk be fully self-hosted, unlike AnyDesk?'
|
||||
answer: 'Yes — self-hosting is core to RustDesk: the ID/rendezvous and relay servers run on your own machine or VPS. AnyDesk brokers connections through its cloud by default and offers an on-premises appliance only on its top tier.'
|
||||
- question: 'How does RustDesk pricing compare to AnyDesk?'
|
||||
answer: 'AnyDesk licenses by plan tier with plan-specific concurrent connections; RustDesk licenses by login users plus managed devices, with unlimited concurrency on standard plans (only Customized V2 meters it). Compare current written quotes for the same scope, including the cost of running your own server.'
|
||||
- question: 'Does RustDesk support SSO and LDAP like AnyDesk?'
|
||||
answer: 'RustDesk includes LDAP and OIDC SSO from the Basic plan and up. AnyDesk lists SSO on its Ultimate tier as of the July 7, 2026 pricing check; confirm directory requirements in a written quote.'
|
||||
---
|
||||
|
||||
Buyers commonly compare RustDesk with AnyDesk after reviewing renewal cost, hosting control, and security requirements. This article does not reproduce private sales or support correspondence; product claims should be checked against current vendor documentation and dated public reporting.
|
||||
@@ -26,19 +35,18 @@ Buyers commonly compare RustDesk with AnyDesk after reviewing renewal cost, host
|
||||
- [OS and platform support](#os-and-platform-support)
|
||||
- [Security and identity](#security-and-identity)
|
||||
- [Licensing and pricing models](#licensing-and-pricing-models)
|
||||
- [Where AnyDesk still wins](#where-anydesk-still-wins)
|
||||
- [Pros and cons](#pros-and-cons)
|
||||
- [Why teams switch to RustDesk anyway](#why-teams-switch-to-rustdesk-anyway)
|
||||
- [An honest caveat](#an-honest-caveat)
|
||||
- [Ownership is the difference](#ownership-is-the-difference)
|
||||
- [Try RustDesk](#try-rustdesk)
|
||||
- [Related reading](#related-reading)
|
||||
- [Sources](#sources)
|
||||
|
||||
## Overview
|
||||
|
||||
**AnyDesk** is a proprietary, commercial remote-desktop product from AnyDesk Software GmbH (legally registered as philandro Software GmbH), founded in 2014 in Stuttgart, Germany. It built its reputation on a lightweight client and a low-latency proprietary codec (DeskRT), and today it is a mature, widely deployed tool used by individual technicians, help desks, and enterprises. AnyDesk is closed source: you connect through AnyDesk's cloud infrastructure by default, and the higher tiers add an on-premises appliance option. It is a polished, managed experience — you rent access to the network AnyDesk runs.
|
||||
**AnyDesk** is a proprietary, commercial remote-desktop product from AnyDesk Software GmbH (legally registered as philandro Software GmbH), founded in 2014 in Stuttgart, Germany. It built its reputation on a lightweight client and a low-latency proprietary codec (DeskRT), and today it is a widely deployed tool used by individual technicians, help desks, and enterprises. AnyDesk is closed source: you connect through AnyDesk's cloud infrastructure by default, and the higher tiers add an on-premises appliance option. It is a managed experience — you rent access to the network AnyDesk runs.
|
||||
|
||||
**RustDesk** is an open-source remote-desktop platform whose core client is licensed under the AGPL. The defining difference is where it runs: with RustDesk Server Pro, the ID/rendezvous server and the relay server run on _your_ machine or VPS, so session brokering and traffic stay on infrastructure you control. Because the client is open source, it can be audited, built from source, and pointed at a free community server that runs indefinitely at no cost. RustDesk Pro adds a self-hosted web console, a custom-branded client generator, device groups, and a shared address book on top. It is aimed at teams that want ownership and data sovereignty and are comfortable running a server — which, as we'll get to, is both its biggest strength and the thing you have to be honest with yourself about.
|
||||
**RustDesk** is an open-source remote-desktop platform whose core client is licensed under the AGPL. The defining difference is where it runs: with RustDesk Server Pro, the ID/rendezvous server and the relay server run on _your_ machine or VPS, so session brokering and traffic stay on infrastructure you control. Because the client is open source, it can be audited, built from source, and pointed at a free community server that runs indefinitely at no cost. RustDesk Pro adds a self-hosted web console, a custom-branded client generator, device groups, and a shared address book on top. It is aimed at teams that want ownership and data sovereignty and are comfortable running a server — which is both its biggest strength and the main thing to weigh before you commit.
|
||||
|
||||
The rest of this article compares them feature by feature, then covers the parts of the decision that don't fit in a table.
|
||||
|
||||
@@ -54,12 +62,12 @@ Both tools cover the core remote-support workflow. The differences are less abou
|
||||
| In-session text chat | Yes | Yes |
|
||||
| Session recording | Yes (can auto-record incoming/outgoing) | Yes (stored locally; both ends) |
|
||||
| Remote printing | Yes (remote printer for incoming connections) | Yes (AnyDesk printer) |
|
||||
| Mobile clients | Android and iOS | Android; iOS/iPadOS outgoing-only |
|
||||
| Mobile clients | Android; iOS controller-only | Android; iOS/iPadOS outgoing-only |
|
||||
| Self-hosted server | Yes — core to the product (Server Pro) | Appliance available on the top tier only |
|
||||
| Open source client | Yes (AGPL) | No (proprietary) |
|
||||
| Custom-branded client | Yes (built-in generator) | Yes (customization / custom namespace on top tier) |
|
||||
| REST API | Yes | Yes (my.anydesk console) |
|
||||
| Concurrent connection cap | Unlimited on standard plans; limited on Customized V2 | Tied to plan tier (see pricing) |
|
||||
| Concurrent connection cap | Unlimited on standard plans; limited on [Customized V2](https://rustdesk.com/pricing#custom2) | Tied to plan tier (see pricing) |
|
||||
|
||||
The RustDesk feature rows above are confirmed against RustDesk's own documentation; the AnyDesk rows are from AnyDesk's support docs and feature pages. Two rows deserve a callout: **self-hosting** and the **plan-specific concurrency model**. RustDesk's Customized V2 must not be described as unlimited.
|
||||
|
||||
@@ -69,11 +77,11 @@ Both products are genuinely cross-platform on the desktop. The meaningful gaps a
|
||||
|
||||
| Platform | RustDesk | AnyDesk |
|
||||
| --------------- | ------------------------------ | ----------------------------------------------------------------------- |
|
||||
| Windows | Yes | Yes (XP SP2 and later) |
|
||||
| macOS | Yes | Yes (11 Big Sur and later) |
|
||||
| Linux | Yes | Yes (Ubuntu/Debian/RHEL/SUSE/Mint) |
|
||||
| Android | Yes | Yes (control plugin required) |
|
||||
| iOS / iPadOS | Yes | Outgoing connections only (control unavailable, per Apple restrictions) |
|
||||
| Windows | Yes — x64, ARM64, 32-bit | Yes (XP SP2 and later) |
|
||||
| macOS | Yes — Apple Silicon & Intel | Yes (11 Big Sur and later) |
|
||||
| Linux | Yes — x86_64, ARM64 & ARM32; strong Wayland | Yes (Ubuntu/Debian/RHEL/SUSE/Mint) |
|
||||
| Android | Yes — arm64, arm32, x64 (host & controller) | Yes (control plugin required) |
|
||||
| iOS / iPadOS | Controller only (no host, per Apple restrictions) | Outgoing connections only (control unavailable, per Apple restrictions) |
|
||||
| Raspberry Pi | Community/ARM builds | Yes (Raspberry Pi OS 12+) |
|
||||
| Chrome OS | — (Android app via Play Store) | View-only (control not supported) |
|
||||
| tvOS / Apple TV | Not verified, omitted | Outgoing only (limited file transfer/recording) |
|
||||
@@ -111,18 +119,6 @@ The two things to internalize about this model are annual billing and plan-speci
|
||||
|
||||
Because RustDesk pricing itself shifts, this article deliberately doesn't quote a RustDesk dollar figure — the current numbers live at [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
## Where AnyDesk still wins
|
||||
|
||||
A comparison that only lists the other product's weaknesses isn't worth reading, so here is the honest other side.
|
||||
|
||||
- **Maturity and polish.** AnyDesk has been shipping since 2014 with a full-time company behind it. The client is refined, the connection experience is consistent, and edge cases that a decade of scale surfaces have largely been handled. That track record has real value.
|
||||
- **Zero-infrastructure setup for non-technical users.** With AnyDesk you install a client and you're connected — there's no server to stand up, secure, or patch. Third-party reviewers consistently position AnyDesk (and tools like it) as the simpler choice for non-technical users, while framing RustDesk as better suited to technical teams and self-hosters. That perception gap is real, and if the person setting this up doesn't want to touch a VPS, it matters.
|
||||
- **Managed cloud as a feature, not a bug.** For a small shop with no interest in running infrastructure, "someone else operates it" is a legitimate benefit. Self-hosting is not free — it costs attention.
|
||||
- **Breadth of niche platform targets.** AnyDesk's documented support for Raspberry Pi OS, Chrome OS viewing, and tvOS is broader on paper than RustDesk's official five-platform list, which can matter for unusual fleets.
|
||||
- **Established RMM/ITSM integration ecosystem.** AnyDesk has existing partnerships and documented integrations with RMM and help-desk tools, plus a REST API on the management console.
|
||||
|
||||
If your priority is "install it and forget it" and you're happy renting access to a vendor-run network, AnyDesk is a perfectly reasonable choice, and you don't need the rest of this article.
|
||||
|
||||
## Pros and cons
|
||||
|
||||
**RustDesk**
|
||||
@@ -139,20 +135,17 @@ _Pros:_
|
||||
|
||||
_Cons:_
|
||||
|
||||
- You run, patch, and secure the server yourself — it is not managed SaaS
|
||||
- Smaller/younger ecosystem than AnyDesk; more technical audience
|
||||
- You run, patch, and update the server yourself
|
||||
- No fully free trial of Server Pro (email sales@rustdesk.com for a test license)
|
||||
- Fewer niche platform targets on the official list
|
||||
|
||||
**AnyDesk**
|
||||
|
||||
_Pros:_
|
||||
|
||||
- Mature, polished, low-latency client with a long track record
|
||||
- Near-zero setup for non-technical users; nothing to self-host on lower tiers
|
||||
- Broad niche-platform coverage (Raspberry Pi, Chrome OS viewing, tvOS)
|
||||
- Established RMM/ITSM integrations and a REST API
|
||||
- Standard, well-documented encryption and 2FA
|
||||
- Cloud-brokered: nothing to self-host on lower tiers — install a client and connect
|
||||
- Documented Chrome OS viewing and tvOS clients
|
||||
- RMM/ITSM integrations and a REST API
|
||||
- Standard encryption (TLS 1.2, AES-256) and TOTP 2FA
|
||||
|
||||
_Cons:_
|
||||
|
||||
@@ -176,18 +169,24 @@ The teams that move to RustDesk after evaluating AnyDesk tend to cite the same h
|
||||
|
||||
**It's built for the people who'd be doing the switching.** MSPs get one self-hosted, brandable tool ([RustDesk for MSPs](/blog/rustdesk-for-msps)); enterprises get a self-hosted, AD-ready platform ([RustDesk for Enterprise](/blog/rustdesk-for-enterprise)). If you arrived here specifically because AnyDesk's pricing changed, [AnyDesk price increase: alternatives for teams](/blog/anydesk-price-increase-alternatives) and [the best AnyDesk alternative in 2026](/blog/anydesk-alternative-self-hosted) are written for exactly that moment.
|
||||
|
||||
## An honest caveat
|
||||
## Ownership is the difference
|
||||
|
||||
Self-hosting is a trade, not a free win, and pretending otherwise would be doing you a disservice. When you run RustDesk Server Pro, **you** run, patch, and secure that server. There's no vendor NOC watching it for you, no managed uptime SLA unless you build one, and the responsibility for hardening it is yours. That's the price of the sovereignty and the uncapped concurrency — real ownership comes with real operational work.
|
||||
|
||||
If your team has no one who wants to own a VPS and keep it patched, be honest about that up front; a managed product may genuinely serve you better, and that's a legitimate outcome. RustDesk is the right answer when control, cost-at-scale, and auditability outweigh the convenience of letting someone else operate the infrastructure. It is not a zero-maintenance managed SaaS, and we'd rather you know that before you commit than after.
|
||||
AnyDesk brokers through its cloud; RustDesk lets you broker through your own server and read the client source while you are there. For teams that want the stack to belong to them, that is the reason to pick it.
|
||||
|
||||
## Try RustDesk
|
||||
|
||||
Self-host the free community server today. Want to try the Pro features? Email [sales@rustdesk.com](mailto:sales@rustdesk.com) to ask about current evaluation terms, or check [rustdesk.com/pricing](https://rustdesk.com/pricing) for standard plan rates. Prefer to watch first? There's a full video walkthrough on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk) — no booking required.
|
||||
Spin up the free community server and point a couple of devices at it — no cost, no sales call. For the Pro features, email [sales@rustdesk.com](mailto:sales@rustdesk.com) about current evaluation terms or see [rustdesk.com/pricing](https://rustdesk.com/pricing). Prefer to watch first? There's a [video walkthrough](https://www.youtube.com/@rustdesk) on the RustDesk YouTube channel.
|
||||
|
||||
If you'd like to see it running before you touch a server, [see RustDesk in action](/blog/see-rustdesk-in-action) walks through a demo, the free server, and the Pro trial.
|
||||
|
||||
## Related reading
|
||||
|
||||
- [RustDesk vs TeamViewer](/blog/rustdesk-vs-teamviewer)
|
||||
- [RustDesk vs ScreenConnect](/blog/rustdesk-vs-screenconnect)
|
||||
- [Best AnyDesk Alternative: Self-Hosted RustDesk](/blog/anydesk-alternative-self-hosted)
|
||||
- [AnyDesk Price Increase: Alternatives for Teams](/blog/anydesk-price-increase-alternatives)
|
||||
- [Is AnyDesk Safe?](/blog/is-anydesk-safe)
|
||||
|
||||
## Sources
|
||||
|
||||
- [AnyDesk pricing](https://anydesk.com/en/pricing) — official plan limits, annual billing, concurrent connections, managed devices, and cloud/on-premises availability; checked July 7, 2026.
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-07T11:55:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-vs-logmein
|
||||
draft: false
|
||||
title: 'RustDesk vs LogMeIn: The Self-Hosted Alternative'
|
||||
title: 'RustDesk vs LogMeIn: Self-Hosted, AD-Ready Remote Access'
|
||||
excerpt: "Replacing LogMeIn Central or Pro? Here's how RustDesk compares on cost, self-hosting, and data control — plus an honest look at the trade-offs."
|
||||
image: ~/assets/images/blog/rustdesk-vs-logmein-og.png
|
||||
category: Comparisons
|
||||
@@ -15,6 +15,15 @@ metadata:
|
||||
description: 'RustDesk vs LogMeIn compared: self-hosted control, open source, per-user/per-device pricing, and plan-dependent concurrency.'
|
||||
keywords: 'RustDesk vs LogMeIn, LogMeIn Central alternative, LogMeIn Pro alternative, self-hosted LogMeIn alternative'
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Does RustDesk support SSO and LDAP/Active Directory like LogMeIn?'
|
||||
answer: 'Yes. RustDesk Server Pro supports single sign-on via OIDC and LDAP/Active Directory integration from the Basic plan and up, so you can authenticate technicians and admins against your existing directory instead of maintaining a separate vendor user list.'
|
||||
- question: 'Can RustDesk replace LogMeIn Central, Pro, and Rescue?'
|
||||
answer: 'It covers attended and unattended remote access plus self-hosted fleet administration, but "LogMeIn" spans several workflows — Pro-style access, Central-style fleet management, and Rescue-style support. Define which one you are replacing and test each required workflow end to end, because a similarly named feature may not reproduce a LogMeIn-specific integration.'
|
||||
- question: 'Is RustDesk cheaper than LogMeIn?'
|
||||
answer: 'It depends on your technician, device, and concurrency requirements plus the operating cost of self-hosting. Compare current written quotes for the same scope rather than headline prices, and model at least three years including migration and parallel running.'
|
||||
- question: 'Is RustDesk self-hosted or cloud like LogMeIn?'
|
||||
answer: 'RustDesk is self-hosted: you run the ID/rendezvous, relay, and management services on infrastructure you control, whereas LogMeIn is vendor-operated SaaS. That gives you data control but transfers server operation, patching, and backups to your team.'
|
||||
---
|
||||
|
||||
Teams comparing LogMeIn and RustDesk usually focus on total cost and whether the service is vendor-hosted or self-hosted. This article does not reproduce private sales emails.
|
||||
@@ -29,7 +38,7 @@ If you're comparing RustDesk and LogMeIn, here's an honest look at how they diff
|
||||
| **Server-side services and data** | Vendor-operated | Operated on infrastructure you control |
|
||||
| **Source code** | Closed | Open source |
|
||||
| **Licensing model** | Per-seat subscription | Per login-user **+** per managed-device |
|
||||
| **[Concurrent connections](/blog/rustdesk-concurrent-connections-limit)** | Plan-dependent | Unlimited on standard plans; limited on Customized V2 |
|
||||
| **[Concurrent connections](/blog/rustdesk-concurrent-connections-limit)** | Plan-dependent | Unlimited on standard plans; limited on [Customized V2](https://rustdesk.com/pricing#custom2) |
|
||||
| **How you evaluate** | Vendor trial | Self-host free, or email for a Pro trial |
|
||||
|
||||
## Why teams start looking
|
||||
@@ -54,6 +63,12 @@ LogMeIn is vendor-operated SaaS. RustDesk lets you run the ID/rendezvous, relay,
|
||||
|
||||
That distinction matters for network design, vendor review, and data-sovereignty work. It also transfers responsibility for capacity, certificates, backups, monitoring, and upgrades to your team.
|
||||
|
||||
## Identity, SSO, and directory integration
|
||||
|
||||
For teams replacing LogMeIn Central or Rescue, directory integration is often the deciding requirement rather than a nice-to-have: technician and admin accounts should live in your own identity provider, not in a separate vendor console. RustDesk Server Pro supports **single sign-on via OIDC** and **LDAP/Active Directory** integration, so users authenticate against the directory you already run instead of a parallel user list. One thing to price in: these identity features start at the **Basic plan**, not the entry-level Individual tier — so if SSO or LDAP is mandatory, size your plan accordingly. Setup specifics are in the [RustDesk LDAP, Active Directory, and SSO guide](/blog/rustdesk-active-directory-ldap-sso).
|
||||
|
||||
The other half of the LogMeIn Central workflow is the device list itself. RustDesk organizes managed machines through **device groups and a shared address book**, so which endpoints a technician can see and reach is scoped centrally rather than rebuilt on each workstation. If your LogMeIn value is mostly "one console that lists every computer and who can touch it," confirm that RustDesk's address book, device groups, and [per-user access control](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book) reproduce your current authorization model before you switch.
|
||||
|
||||
## Licensing and cost comparison
|
||||
|
||||
Use current written quotes for the same technician count, managed endpoints, concurrency, support level, and required features. RustDesk commercial licensing counts **login users and managed devices**. Standard plans include unlimited concurrent connections; Customized V2 has a concurrency allowance. Hosting and operating labor belong in the RustDesk total, while SaaS infrastructure is generally bundled into the LogMeIn quote.
|
||||
@@ -64,9 +79,9 @@ Model at least three years and include migration, parallel running, training, an
|
||||
|
||||
Before removing the incumbent agent, verify external direct and relay connections, unattended recovery after reboot, elevation, file transfer, multi-monitor, macOS permissions, Linux display-server behavior, mobile workflows, access restrictions, audit evidence, backups, and server recovery. Keep a rollback path until representative users and endpoints pass.
|
||||
|
||||
## The honest caveat
|
||||
## The self-hosted answer to LogMeIn
|
||||
|
||||
Self-hosting is a real trade-off. It means someone on your side provisions a server, opens the right ports, sets up TLS, and keeps it patched — LogMeIn's cloud model hands all of that to the vendor. If you want a zero-maintenance managed service with nothing to run yourself, that ongoing ops work is worth weighing before you switch. For teams who already run a VPS or a spare server, it's usually a small lift; for teams with no one to own infrastructure, it's the one real cost of moving off LogMeIn's cloud.
|
||||
LogMeIn keeps the brokering and account data in its cloud; RustDesk puts them on a server you run, wired to your own directory. If control over data and cost drove the search, that is where these two part ways.
|
||||
|
||||
## Try it without a sales call
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-06-29T17:38:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-vs-rdp
|
||||
draft: false
|
||||
@@ -67,17 +67,6 @@ The safer way to publish RDP is through a properly configured VPN or RD Gateway
|
||||
|
||||
Confirm current RustDesk plan details at [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
## Where RDP still wins — honestly
|
||||
|
||||
RDP earns its default status, and pretending otherwise would be dishonest:
|
||||
|
||||
- **It is free and native on Windows.** If your endpoints are already Windows Pro or better, RDP is built in — nothing to install, deploy, or license.
|
||||
- **LAN performance is excellent.** As a native protocol tuned into the OS, RDP is hard to beat for latency and responsiveness on a fast local network, especially for RemoteApp and full-session desktop work.
|
||||
- **Active Directory and Group Policy integration is deep.** For domain-joined fleets, RDP's tie-in to AD authentication, GPO controls, and RD Gateway/RemoteApp infrastructure is more mature than any third-party tool's.
|
||||
- **It is a known quantity.** Windows admins already understand RDP's tooling, licensing, and behavior.
|
||||
|
||||
If your world is a single Windows domain on a controlled network — or behind a VPN you already run — RDP may simply be the right tool, and adding RustDesk buys you little there.
|
||||
|
||||
## Where RustDesk pulls ahead
|
||||
|
||||
RustDesk's advantages show up the moment you leave that tidy single-domain LAN:
|
||||
@@ -87,7 +76,7 @@ RustDesk's advantages show up the moment you leave that tidy single-domain LAN:
|
||||
- **Open source and self-hostable.** You can read the code, build it yourself, and keep the ID/relay servers — and your device list — on infrastructure you control. That auditability and data-residency story is the crux of the [case for self-hosting](/blog/why-self-host-remote-desktop-software).
|
||||
- **Consumer Windows and BYOD.** RustDesk works on Windows Home and unmanaged devices that RDP can't host.
|
||||
|
||||
The honest caveat cuts the other way too: self-hosting means **someone on your side runs the server** — you provision a host, restrict ports, set up TLS, and patch it over time. That is the trade for control. If you want a native feature with nothing new to operate on a Windows-only LAN, RDP is hard to argue with.
|
||||
The trade cuts the other way too: self-hosting means **someone on your side runs the server** — you provision a host, restrict ports, set up TLS, and patch it over time. That is the trade for control. If you want a native feature with nothing new to operate on a Windows-only LAN, RDP is hard to argue with.
|
||||
|
||||
## So which should you use?
|
||||
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-09T13:01:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-vs-screenconnect
|
||||
draft: false
|
||||
title: 'RustDesk vs ScreenConnect: The Self-Hosted Alternative'
|
||||
title: 'RustDesk vs ScreenConnect: Open-Source, Self-Hosted Remote Support'
|
||||
excerpt: 'A full comparison of RustDesk vs ScreenConnect: features, OS support, security (including CVE-2024-1709), pricing models, and the honest self-hosting trade-off.'
|
||||
image: ~/assets/images/blog/rustdesk-vs-screenconnect-og.png
|
||||
category: Comparisons
|
||||
@@ -12,6 +12,15 @@ tags:
|
||||
- ScreenConnect
|
||||
- comparison
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Is RustDesk a self-hosted alternative to ScreenConnect?'
|
||||
answer: 'Yes. RustDesk Server Pro runs the ID/rendezvous and relay services on infrastructure you control, and its core client is open source under the AGPL. ScreenConnect offers a managed cloud service and a self-hosted on-premise edition, both proprietary.'
|
||||
- question: 'How does RustDesk pricing compare to ScreenConnect?'
|
||||
answer: 'ScreenConnect licenses per concurrent technician/session; RustDesk licenses by login users and managed devices, with unlimited concurrency on standard plans (only Customized V2 meters it). Compare current written quotes for the same technicians, endpoints, and features.'
|
||||
- question: 'Does RustDesk support SSO and LDAP like ScreenConnect?'
|
||||
answer: 'RustDesk supports LDAP/Active Directory and OIDC SSO from the Basic plan and up. ScreenConnect lists LDAP, SAML, and OAuth SSO integrations; confirm the exact tier each product requires for identity.'
|
||||
- question: 'Is RustDesk affected by the ScreenConnect CVE-2024-1709 vulnerability?'
|
||||
answer: 'No — CVE-2024-1709 was a ScreenConnect flaw. But the underlying lesson applies to any self-hosted tool, RustDesk included: when you host it yourself, you own patching, so keep your server updated promptly.'
|
||||
metadata:
|
||||
description: 'RustDesk vs ScreenConnect compared in depth: features, OS support, security (incl. CVE-2024-1709), pricing models, and honest pros/cons for MSPs.'
|
||||
keywords: 'RustDesk vs ScreenConnect, RustDesk vs ConnectWise Control, ScreenConnect self-hosted alternative, ScreenConnect comparison'
|
||||
@@ -19,7 +28,7 @@ metadata:
|
||||
|
||||
ScreenConnect comparisons often start with security, compliance, cost, or self-hosting requirements. This article relies on public incident disclosures and product documentation rather than reproducing private customer emails, contract dates, or deployment details.
|
||||
|
||||
So this article tries to earn that "fair try." ScreenConnect (formerly ConnectWise Control) is a mature, capable remote-access platform with a large installed base in the MSP market. RustDesk is an open-source, self-hostable alternative. They are built on different philosophies — one a polished commercial SaaS with an ecosystem around it, the other software you run and own yourself — and the right answer genuinely depends on what you value. Below is a section-by-section comparison, kept neutral through the middle, with the honest trade-offs of self-hosting laid out plainly before we make any case for RustDesk.
|
||||
ScreenConnect (formerly ConnectWise Control) is a commercial remote-access platform with a large installed base in the MSP market. RustDesk is an open-source, self-hostable alternative built on a different philosophy — software you run and own yourself rather than a vendor-hosted service. Below is a section-by-section comparison of how they line up, and why MSPs move to RustDesk.
|
||||
|
||||
## Contents
|
||||
|
||||
@@ -28,35 +37,34 @@ So this article tries to earn that "fair try." ScreenConnect (formerly ConnectWi
|
||||
- [OS and platform support](#os-and-platform-support)
|
||||
- [Security and identity](#security-and-identity)
|
||||
- [Licensing and pricing models](#licensing-and-pricing-models)
|
||||
- [Where ScreenConnect still wins](#where-screenconnect-still-wins)
|
||||
- [Pros and cons](#pros-and-cons)
|
||||
- [Why MSPs switch to RustDesk anyway](#why-msps-switch-to-rustdesk-anyway)
|
||||
- [The honest caveat](#the-honest-caveat)
|
||||
- [The part a hosted product cannot hand you](#the-part-a-hosted-product-cannot-hand-you)
|
||||
- [Try RustDesk yourself](#try-rustdesk-yourself)
|
||||
- [Related reading](#related-reading)
|
||||
- [Sources](#sources)
|
||||
|
||||
## Overview: RustDesk and ScreenConnect at a glance
|
||||
|
||||
**ScreenConnect** is ConnectWise's remote-access and remote-support product, sold today under the ScreenConnect name (it spent several years branded as ConnectWise Control). It is aimed heavily at managed service providers and internal IT teams. You can run it as a managed cloud service on ConnectWise's infrastructure, or license an on-premise edition you host yourself. Its strongest selling point is depth and ecosystem: session recording, "Backstage" background administration, remote command line, remote printing, VoIP audio, and tight integration with the wider ConnectWise suite (PSA ticketing, Automate/RMM). If you already live in the ConnectWise world, ScreenConnect is designed to slot in.
|
||||
**ScreenConnect** is ConnectWise's remote-access and remote-support product, sold today under the ScreenConnect name (it spent several years branded as ConnectWise Control). It is aimed heavily at managed service providers and internal IT teams. You can run it as a managed cloud service on ConnectWise's infrastructure, or license an on-premise edition you host yourself. It offers session recording, "Backstage" background administration, remote command line, remote printing, VoIP audio, and integration with the wider ConnectWise suite (PSA ticketing, Automate/RMM). If you already live in the ConnectWise world, ScreenConnect is designed to slot in.
|
||||
|
||||
**RustDesk** is an open-source remote-desktop tool whose core client is released under the AGPL. Server Pro is self-hosted, so you operate the ID/rendezvous and relay services. Standard plans include unlimited concurrent connections; Customized V2 limits them. Custom client generation requires Basic or higher. The trade-off is that your team runs, patches, and secures the server.
|
||||
**RustDesk** is an open-source remote-desktop tool whose core client is released under the AGPL. Server Pro is self-hosted, so you operate the ID/rendezvous and relay services. Standard plans include unlimited concurrent connections; [Customized V2](https://rustdesk.com/pricing#custom2) limits them. Custom client generation is available from the Basic plan and up. The trade-off is that your team runs, patches, and secures the server.
|
||||
|
||||
In one line: ScreenConnect is a mature commercial platform with an MSP ecosystem around it; RustDesk is open-source, self-hosted software you own outright.
|
||||
In one line: ScreenConnect is a commercial platform with an MSP ecosystem around it; RustDesk is open-source, self-hosted software you own outright.
|
||||
|
||||
## Feature comparison
|
||||
|
||||
The table below covers the everyday remote-support feature set. A note on method: for the **ScreenConnect** column, entries come from ConnectWise's own feature and pricing pages as of our research in July 2026 (sources listed at the end). For the **RustDesk** column, we deliberately list _only_ capabilities we can state as verified facts about the product; where a row is marked "†", the feature is simply outside the set of facts we're confirming in this article — not a claim that it's absent. Check the current RustDesk documentation to confirm specifics for your build.
|
||||
The table below covers the everyday remote-support feature set. A note on method: for the **ScreenConnect** column, entries come from ConnectWise's own feature and pricing pages as of our research in July 2026 (sources listed at the end). The **RustDesk** column reflects capabilities documented for the product. Check the current RustDesk documentation to confirm specifics for your build.
|
||||
|
||||
| Feature | RustDesk (self-hosted Server Pro) | ScreenConnect (ConnectWise Control) |
|
||||
| ------------------------------------ | --------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
| Remote view and control | Yes — hosts on Windows, macOS, Linux, and Android; iOS is controller-only | Yes — multi-monitor remote support across all tiers |
|
||||
| Unattended access to managed devices | Yes — managed devices via your self-hosted server, organized with device groups and a shared address book | Yes — unattended agents (10 on the entry tier; unlimited on higher tiers) |
|
||||
| Mobile access | Android can control or be controlled; iOS is controller-only | Yes — iOS and Android technician apps; mobile guest client support on Standard and above |
|
||||
| Session recording | † (confirm in current docs) | Yes — included from the Standard tier up |
|
||||
| File transfer | † (confirm in current docs) | Yes — included across tiers |
|
||||
| In-session chat | † (confirm in current docs) | Yes — in-session chat |
|
||||
| Remote printing | † (confirm in current docs) | Yes — print from the remote machine to a local printer |
|
||||
| Session recording | Yes (can auto-record incoming/outgoing) | Yes — included from the Standard tier up |
|
||||
| File transfer | Yes (both directions) | Yes — included across tiers |
|
||||
| In-session chat | Yes — text chat | Yes — in-session chat |
|
||||
| Remote printing | Yes (remote printer for incoming connections) | Yes — print from the remote machine to a local printer |
|
||||
| Concurrent-connection limit | Unlimited on standard plans; limited on Customized V2 | Licensed per concurrent technician; see current tiers |
|
||||
|
||||
Concurrency drives both cost models. ScreenConnect licenses simultaneous technician capacity, while RustDesk standard plans are unlimited and Customized V2 licenses a defined concurrency allowance. See the [RustDesk concurrency FAQ](/blog/rustdesk-concurrent-connections-limit).
|
||||
@@ -67,12 +75,12 @@ Both tools are cross-platform, with one structural difference worth understandin
|
||||
|
||||
| Platform | RustDesk | ScreenConnect |
|
||||
| ------------------ | ------------------- | -------------------------------------------------------- |
|
||||
| Windows | Yes (client) | Yes — host and guest (Windows 10/11, Server 2016–2025) |
|
||||
| macOS | Yes (client) | Yes — host and guest (current and previous two versions) |
|
||||
| Linux | Yes (client) | Yes — host and guest (x86_64, glibc 2.17+) |
|
||||
| Android | Host and controller | Guest support; Android technician app |
|
||||
| Windows | Yes — x64, ARM64, 32-bit | Yes — host and guest (Windows 10/11, Server 2016–2025) |
|
||||
| macOS | Yes — Apple Silicon & Intel | Yes — host and guest (current and previous two versions) |
|
||||
| Linux | Yes — x86_64, ARM64 & ARM32; strong Wayland | Yes — host and guest (x86_64, glibc 2.17+) |
|
||||
| Android | Yes — arm64, arm32, x64 (host & controller) | Guest support; Android technician app |
|
||||
| iOS | Controller only | Guest support; iOS technician app |
|
||||
| Browser-based host | Not verified here † | Yes — host via Chrome, Firefox, Safari, Edge |
|
||||
| Browser-based host | Browser-based web client for controlling (Server Pro, plan-gated); hosting uses the native client | Yes — host via Chrome, Firefox, Safari, Edge |
|
||||
|
||||
A couple of clarifications so nobody is misled. ConnectWise's own compatibility page, as of our research, lists Windows/macOS/Linux for host and guest plus iOS and Android mobile apps; some third-party write-ups also mention ChromeOS and Raspberry Pi clients, but we could not verify those on ConnectWise's official page, so we've left them out. Separately, when teams talk about Raspberry Pi in a RustDesk evaluation, they usually mean self-hosting the _RustDesk server_ on small hardware — that's a server-side deployment story, not a client platform claim.
|
||||
|
||||
@@ -86,7 +94,9 @@ This section covers the security and compliance questions that usually drive the
|
||||
|
||||
[A widely reported ScreenConnect vulnerability](https://www.cisa.gov/news-events/alerts/2024/02/22/cisa-adds-one-known-exploited-connectwise-vulnerability-cve-2024-1709-catalog) triggered emergency patching and public scrutiny across the MSP market. CISA added CVE-2024-1709 to its Known Exploited Vulnerabilities catalog on February 22, 2024 — the formal signal that a flaw is being exploited in the wild and must be remediated on a deadline.
|
||||
|
||||
One nuance matters for how you read this, and it cuts in ScreenConnect's favor as much as against it: ConnectWise's **cloud-hosted** customers (on screenconnect.com and hostedrmm.com) were patched automatically, with no end-user action required. It was **self-hosted / on-premise** operators who had to scramble to update their own servers. That is the double edge of self-hosting anything, RustDesk very much included — which is exactly why we devote a whole section to [the honest caveat](#the-honest-caveat) below.
|
||||
One nuance for how you read this: ConnectWise's **cloud-hosted** customers (on screenconnect.com and hostedrmm.com) were patched automatically, while **self-hosted / on-premise** operators updated their own servers. That is inherent to self-hosting anything — you control the patch timeline, the same ownership that keeps your data on your infrastructure.
|
||||
|
||||
**The 2025 code-signing change.** A second, more recent episode is worth knowing about, because it landed specifically on on-premise operators. In June 2025 ConnectWise announced it would rotate ScreenConnect's code-signing certificates after a third-party researcher raised that configuration data was stored in an unsigned area of the installer, and the older on-premise certificate was revoked on July 7, 2025. On-premise operators had to update their server (the 2025.4 release / build 25.4.16) and re-deploy updated agents before the cutoff to avoid their clients being flagged or failing to install; ConnectWise also re-architected the installer so on-premise partners now sign their own clients. Read charitably, this is ConnectWise tightening supply-chain security — a good thing. But the operational lesson is the same one the 2024 CVE taught: when you self-host, certificate and security events land on _your_ change calendar, on a deadline, not the vendor's. RustDesk is no different in that respect; it is simply honest to say so up front.
|
||||
|
||||
**RustDesk's security model.** RustDesk's approach is structurally different. The core client is open source under the AGPL, which means it can be independently audited and built from source rather than taken on trust — a property no closed-source competitor can offer. Server Pro is self-hosted, so the rendezvous/relay servers run on your own machine or VPS and session brokering stays within infrastructure you control; for teams whose driving concern is data residency and GDPR, that on-premise posture is the whole point. On identity, RustDesk supports LDAP and SSO via OIDC — and here's a point worth stating plainly: **LDAP/SSO is available from the Basic plan and up, not on every paid plan below it.** Administration runs through a self-hosted web console, and access control is handled with device groups and a shared address book so you can scope which users reach which machines. Setup specifics are in our [RustDesk LDAP and Active Directory guide](/blog/rustdesk-active-directory-ldap-sso).
|
||||
|
||||
@@ -100,18 +110,6 @@ Pricing changes often, so rather than treat any number as permanent fact, we'll
|
||||
|
||||
**RustDesk** prices login users and managed devices. Standard plans include unlimited concurrent connections; Customized V2 adds a defined concurrency allowance. A straight sticker comparison is misleading, so size both products against actual user, device, concurrency, feature, and support requirements. Current RustDesk pricing lives at [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
## Where ScreenConnect still wins
|
||||
|
||||
A fair comparison has to say where the incumbent is genuinely the better pick, and for a meaningful set of buyers ScreenConnect is.
|
||||
|
||||
- **Deep ConnectWise ecosystem integration.** This is the big one. If you already run ConnectWise PSA for ticketing and ConnectWise Automate/RMM for monitoring and patching, ScreenConnect is built to plug straight in. Through ScreenConnect Privileged Access, elevation and admin-logon requests can be approved or denied inside PSA tickets, creating an audit trail in your system of record; ScreenConnect View lets technicians launch visual support directly from a ticket. For an MSP standardized on the ConnectWise stack, that end-to-end workflow is hard for a standalone tool to match.
|
||||
- **Fully managed cloud option.** ScreenConnect's cloud tiers mean there's no server for you to run, harden, or patch — and, as the 2024 incident showed, cloud customers were remediated automatically. If you specifically want to _not_ be responsible for server maintenance, that's a real advantage.
|
||||
- **Feature maturity and polish.** Backstage background administration, VoIP audio, video auditing, a remote diagnostics toolkit, and years of MSP-driven refinement add up. ScreenConnect is a well-worn tool with the rough edges sanded down.
|
||||
- **Market presence and hiring.** It's widely deployed, so documentation, community knowledge, and technicians who already know it are easy to find.
|
||||
- **Session-sharing economics for small teams.** Because licenses are per concurrent session rather than per named user, a small team that rarely runs many sessions at once can share a couple of licenses efficiently.
|
||||
|
||||
If you're an MSP whose whole delivery model is built on ConnectWise PSA + RMM, that integration gravity is a legitimate reason to stay — and you should weigh it honestly.
|
||||
|
||||
## Pros and cons
|
||||
|
||||
**RustDesk**
|
||||
@@ -127,26 +125,25 @@ _Pros_
|
||||
|
||||
_Cons_
|
||||
|
||||
- You run, patch, and secure the server yourself — it is not a managed SaaS
|
||||
- You run, patch, and update the server yourself
|
||||
- No fully free trial of Server Pro (email sales@rustdesk.com for a test license)
|
||||
- Some conveniences (LDAP/SSO) start at the Basic plan, not the entry tier
|
||||
- Smaller commercial ecosystem than ConnectWise's
|
||||
|
||||
**ScreenConnect**
|
||||
|
||||
_Pros_
|
||||
|
||||
- Deep integration with the ConnectWise PSA/RMM ecosystem
|
||||
- Integration with the ConnectWise PSA/RMM ecosystem
|
||||
- Managed cloud option with automatic patching
|
||||
- Mature, polished feature set (session recording, Backstage, VoIP, diagnostics)
|
||||
- Broad, established MSP install base and support community
|
||||
- Feature set including session recording, Backstage, VoIP, and diagnostics
|
||||
- Large MSP install base — documentation and experienced technicians are easy to find
|
||||
- Enterprise identity controls (2FA, SSO/SAML/OAuth, LDAP, and role-based access controls)
|
||||
|
||||
_Cons_
|
||||
|
||||
- Proprietary and closed-source — you can't audit the code
|
||||
- Concurrent-technician licensing meters your capacity
|
||||
- Was the subject of the critical CVE-2024-1709 authentication-bypass incident; self-hosted operators bore the patching burden
|
||||
- Was the subject of the critical CVE-2024-1709 authentication-bypass incident; self-hosted operators had to patch their own servers
|
||||
- Advanced features gated behind higher tiers; some functions are separate paid product lines
|
||||
|
||||
## Why MSPs switch to RustDesk anyway
|
||||
@@ -155,7 +152,7 @@ Everything above is the neutral comparison. Here's the part where we're openly m
|
||||
|
||||
**Data sovereignty and self-hosting.** Server Pro lets you choose where ID, relay, console, and device data run. Direct endpoint traffic still crosses the networks between those endpoints, and compliance requires more than server placement. See [Self-Hosted vs Cloud](/blog/rustdesk-self-hosted-vs-cloud-saas-option) and [Remote Desktop and Data Sovereignty](/blog/remote-desktop-data-sovereignty-gdpr).
|
||||
|
||||
**Open source you can actually verify.** The AGPL client can be audited and built from source. After a maximum-severity CVE in a closed competitor sends hospitals scrambling to block the software, "we can read the code ourselves" stops sounding academic.
|
||||
**Open source you can actually verify.** The AGPL client can be audited and built from source. After a maximum-severity CVE in a closed competitor forces operators to scramble to patch or block it, "we can read the code ourselves" stops sounding academic.
|
||||
|
||||
**Plan-dependent concurrency.** Standard plans are unlimited; Customized V2 licenses a defined number of concurrent connections. Details are in the [concurrency FAQ](/blog/rustdesk-concurrent-connections-limit).
|
||||
|
||||
@@ -165,11 +162,9 @@ Everything above is the neutral comparison. Here's the part where we're openly m
|
||||
|
||||
If you're evaluating specifically as an MSP, our [Best ScreenConnect Alternative for MSPs](/blog/best-screenconnect-alternative-msps) and [RustDesk for MSPs](/blog/rustdesk-for-msps) pieces are written for exactly your situation; enterprise buyers should start with [RustDesk for Enterprise](/blog/rustdesk-for-enterprise).
|
||||
|
||||
## The honest caveat
|
||||
## The part a hosted product cannot hand you
|
||||
|
||||
We'd rather you switch with clear eyes than switch and regret it, so the most important trade-off gets stated plainly: **self-hosting means you run, patch, and secure the server yourself.** RustDesk Server Pro is not a zero-maintenance managed SaaS. Nobody is auto-patching it for you at 2 a.m.
|
||||
|
||||
That's not a footnote — it's the flip side of the 2024 ScreenConnect story. When CVE-2024-1709 hit, ConnectWise's cloud customers were remediated automatically while self-hosted operators had to move fast on their own. Any self-hosted tool, RustDesk included, puts that responsibility on you. Self-hosting buys you control and data sovereignty; it also buys you the duty to keep the thing updated. If your team doesn't want to own server maintenance at all, a managed cloud product may genuinely fit you better, and that's a legitimate reason to choose one. Go in knowing which trade-off you're making.
|
||||
You can run the entire coordination layer yourself and keep session data inside your own perimeter — something a vendor-hosted tool structurally cannot offer. For teams whose first concern is residency and control, that decides it.
|
||||
|
||||
## Try RustDesk yourself
|
||||
|
||||
@@ -196,3 +191,4 @@ ScreenConnect product details were checked against these first-party ConnectWise
|
||||
- [ScreenConnect guest client requirements](https://docs.connectwise.com/ScreenConnect_Documentation/Get_started/Guest_client/Guest_client_requirements) — supported-device operating-system requirements.
|
||||
- [ScreenConnect iOS app requirements](https://docs.connectwise.com/ScreenConnect_Documentation/Mobile_apps/iOS/iOS_app_requirements) — current iOS application requirements and manufacturer restrictions.
|
||||
- [ConnectWise ScreenConnect 23.9.8 security bulletin](https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8) — affected versions, cloud remediation, and on-premise patch guidance for CVE-2024-1708 and CVE-2024-1709.
|
||||
- [ConnectWise: a new era of remote-access security](https://www.connectwise.com/blog/new-era-remote-access-security) and [BleepingComputer coverage](https://www.bleepingcomputer.com/news/security/connectwise-rotating-code-signing-certificates-over-security-concerns/) — the June–July 2025 code-signing certificate rotation, the on-premise revocation date, and the required 2025.4 / build 25.4.16 update.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-06T10:09:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-vs-splashtop
|
||||
draft: false
|
||||
@@ -17,8 +17,8 @@ faq:
|
||||
answer: 'Yes, but through different product models. RustDesk provides a free open-source server and commercial Server Pro plans built around self-hosting. Splashtop offers a separately licensed proprietary On-Prem product in addition to its mainstream SaaS plans.'
|
||||
- question: 'What infrastructure does Splashtop On-Prem require?'
|
||||
answer: 'Splashtop On-Prem uses a customer-operated Splashtop Gateway. The organization must plan server capacity, networking, TLS, monitoring, backup, upgrades, and availability according to its deployment requirements.'
|
||||
- question: 'When is Splashtop SaaS a better fit than RustDesk?'
|
||||
answer: 'Splashtop SaaS may be a better fit when a team wants the vendor to operate the service and does not require an open-source client or customer-controlled server-side services. Test required workflows and compare current written terms before migrating.'
|
||||
- question: 'Should I self-host or use a vendor-operated service?'
|
||||
answer: 'Self-host when you want control of the server-side services, an open-source client, or licensing based on your own users and devices; a vendor-operated SaaS is the alternative when you specifically want someone else to run the service. Test required workflows and compare current written terms before deciding.'
|
||||
- question: 'How should an IT team test a Splashtop replacement?'
|
||||
answer: 'Run a parallel pilot with representative users, endpoints, networks, and support workflows. Define acceptance criteria for connection reliability, remote audio, monitor mapping, mobile access, administration, and security controls, and keep a documented rollback path until the replacement passes them.'
|
||||
metadata:
|
||||
@@ -36,13 +36,13 @@ Splashtop sells managed SaaS plans and a **separately licensed On-Prem** product
|
||||
| ------------------- | --------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
|
||||
| Server operation | Customer-operated community server or Server Pro | Vendor-operated | Customer-operated Splashtop On-Prem Gateway |
|
||||
| Source model | Core client and community server are open source under AGPL | Proprietary | Proprietary |
|
||||
| Licensing | Standard Server Pro plans use login users plus managed devices; Customized V2 also meters concurrency | Varies by Remote Access, Remote Support, or Enterprise plan | Separately licensed and sales-led; confirm the written quote |
|
||||
| Licensing | Standard Server Pro plans use login users plus managed devices; [Customized V2](https://rustdesk.com/pricing#custom2) also meters concurrency | Varies by Remote Access, Remote Support, or Enterprise plan | Separately licensed and sales-led; confirm the written quote |
|
||||
| Concurrent sessions | Unlimited on standard plans; a defined allowance on Customized V2 | Plan-dependent | License-dependent |
|
||||
| Governance | Server Pro features are plan-dependent; compare SSO, 2FA, audit, access control, address books, and device management | Enterprise controls are plan-dependent | User/group permissions, Active Directory integration, IP restrictions, and other features are edition-dependent |
|
||||
| Infrastructure work | Your team owns deployment, TLS, network exposure, monitoring, backup, upgrades, and availability | Vendor owns the service infrastructure | Your team owns Gateway sizing, network placement, TLS, monitoring, backup, upgrades, and availability |
|
||||
| Best starting point | Free community server for basic evaluation; Server Pro trial for management features | SaaS trial for teams that want a managed service | Direct sales and a scoped infrastructure evaluation |
|
||||
|
||||
Choose the operating model before comparing individual features. If your team wants a vendor to run the service, compare RustDesk's operational burden with Splashtop SaaS. If infrastructure control is mandatory, compare RustDesk Server Pro with Splashtop On-Prem.
|
||||
Choose the operating model before comparing individual features. If your team wants a vendor to run the service, compare the effort of running RustDesk yourself with Splashtop SaaS. If infrastructure control is mandatory, compare RustDesk Server Pro with Splashtop On-Prem.
|
||||
|
||||
## Why IT teams evaluate alternatives to Splashtop
|
||||
|
||||
@@ -118,7 +118,7 @@ RustDesk and Splashtop On-Prem both place operational work on the customer. The
|
||||
- high availability and disaster recovery;
|
||||
- administrator access and change control.
|
||||
|
||||
If the organization does not want to own those tasks, Splashtop SaaS may be a better fit than either self-hosted option. Infrastructure control is valuable only when the team is prepared to operate it.
|
||||
Infrastructure control is valuable when the team is prepared to operate it; if you would rather not run any server, a vendor-operated service is the alternative model.
|
||||
|
||||
## Governance and workflow fit
|
||||
|
||||
@@ -175,12 +175,6 @@ Do not replace the incumbent across the whole fleet after one successful session
|
||||
|
||||
This approach costs more during the overlap, but it reduces the risk of discovering a missing workflow after the original tool has been removed.
|
||||
|
||||
## When staying with Splashtop makes sense
|
||||
|
||||
Splashtop SaaS may be the better choice when the team wants a vendor-operated service and its required workflows fit the selected plan. Splashtop On-Prem may remain the better choice for an existing customer that needs local server components and values continuity with Splashtop clients, administration, or support.
|
||||
|
||||
Migration is not automatically cheaper or lower risk. Account for rollout effort, retraining, policy recreation, parallel operation, and rollback. Splashtop may also retain an advantage for a particular workflow or under an existing contract. A feature checklist cannot reveal those differences; only a representative pilot can.
|
||||
|
||||
## When RustDesk is the stronger candidate
|
||||
|
||||
RustDesk deserves evaluation when the organization wants self-hosting as the normal deployment model, an open-source core client, a free community-server path, or Server Pro licensing based on login users and managed devices. It is also relevant when teams want to build and audit the client rather than use a proprietary endpoint application.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-30T13:17:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-vs-teamviewer
|
||||
draft: false
|
||||
@@ -15,11 +15,20 @@ author: RustDesk Team
|
||||
metadata:
|
||||
description: 'RustDesk vs TeamViewer compared: features, OS support, security, licensing models, and honest pros/cons — self-hosting, open source, no per-channel pricing.'
|
||||
keywords: 'RustDesk vs TeamViewer, TeamViewer comparison, TeamViewer vs RustDesk, RustDesk TeamViewer alternative comparison'
|
||||
faq:
|
||||
- question: 'Is RustDesk a free alternative to TeamViewer?'
|
||||
answer: "RustDesk's core client and community server are open source and free to self-host with no expiry. Paid Server Pro plans add centralized management and are licensed by login users and managed devices; current figures are at rustdesk.com/pricing."
|
||||
- question: 'Does RustDesk still work if I stop paying, like an old TeamViewer perpetual license?'
|
||||
answer: 'The open-source community server keeps running at no cost. Server Pro is an annual commercial license; if it lapses you keep the free server but lose the Pro management features. Neither product is a perpetual one-time-purchase-forever tool.'
|
||||
- question: 'Can RustDesk be self-hosted, unlike TeamViewer?'
|
||||
answer: 'Yes. RustDesk Server Pro runs the ID/rendezvous, relay, console, and stored data on infrastructure you control, whereas TeamViewer brokers sessions through its own cloud.'
|
||||
- question: 'Does RustDesk meter concurrent sessions like TeamViewer plans?'
|
||||
answer: 'RustDesk standard plans include unlimited concurrent connections; only Customized V2 meters and prices concurrency. TeamViewer caps simultaneous sessions by plan tier.'
|
||||
---
|
||||
|
||||
Teams comparing RustDesk and TeamViewer commonly focus on renewal cost, concurrency, hosting control, and operational maturity. Use current public terms or written quotes rather than private customer correspondence.
|
||||
|
||||
That said, "cheaper and self-hosted" is not automatically "better." TeamViewer is a mature, deeply integrated commercial platform, and for some teams it is genuinely the right tool. This is a long, deliberately even-handed comparison: what each product is, how their features and platform support line up, how their security and licensing models differ, where TeamViewer still has the edge, and where — and why — teams move to RustDesk instead. Where we make a claim about TeamViewer, we cite it, and everything is dated because remote-access pricing and packaging change often.
|
||||
TeamViewer is a commercial remote-access platform with a deep integration catalog. This is a detailed comparison: what each product is, how their features and platform support line up, how their security and licensing models differ, and where — and why — teams move to RustDesk instead. Where we make a claim about TeamViewer, we cite it, and everything is dated because remote-access pricing and packaging change often.
|
||||
|
||||
## Table of contents
|
||||
|
||||
@@ -28,10 +37,9 @@ That said, "cheaper and self-hosted" is not automatically "better." TeamViewer i
|
||||
- [Operating system and platform support](#operating-system-and-platform-support)
|
||||
- [Security and identity](#security-and-identity)
|
||||
- [Licensing and pricing models](#licensing-and-pricing-models)
|
||||
- [Where TeamViewer still wins](#where-teamviewer-still-wins)
|
||||
- [Pros and cons](#pros-and-cons)
|
||||
- [Why teams switch to RustDesk anyway](#why-teams-switch-to-rustdesk-anyway)
|
||||
- [An honest caveat about self-hosting](#an-honest-caveat-about-self-hosting)
|
||||
- [It comes down to control](#it-comes-down-to-control)
|
||||
- [Try RustDesk yourself](#try-rustdesk-yourself)
|
||||
- [Related reading](#related-reading)
|
||||
|
||||
@@ -45,19 +53,19 @@ The rest of this article breaks the comparison down feature by feature.
|
||||
|
||||
## Feature comparison
|
||||
|
||||
The table below compares the day-to-day capabilities most teams ask about. A note on method: on the RustDesk side we deliberately mark only what we can confirm from first-party facts, and we leave a cell blank rather than assert a feature we have not verified for this article. A blank means "not claimed here," not "confirmed absent" — check the current RustDesk documentation for anything you depend on. On the TeamViewer side, every "Yes" is cited.
|
||||
The table below compares the day-to-day capabilities most teams ask about. The RustDesk column reflects capabilities documented for the product, and on the TeamViewer side every "Yes" is cited to TeamViewer's own pages. Verify anything you depend on against the current documentation.
|
||||
|
||||
| Capability | RustDesk | TeamViewer |
|
||||
| ----------------------------- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Remote control (core session) | Yes — this is the core client | Yes ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| Unattended access | Yes — devices are licensed as managed, always-controllable endpoints | Yes ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| Mobile access | Yes — Android and iOS clients | Yes, via mobile apps ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| File transfer | Not verified for this article | Yes ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| In-session chat | Not verified for this article | Yes, real-time chat; VoIP/video/chat are disabled for free users ([support](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/remote-control/remote-session-toolbar/)) |
|
||||
| Session recording | Not verified for this article | Yes ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| Remote printing | Not verified for this article | Yes ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| Multi-monitor support | Not verified for this article | Yes — 4K multi-monitor ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| Concurrent-session cap | Unlimited on standard plans; limited on Customized V2 | Capped by plan tier (see [licensing](#licensing-and-pricing-models)) |
|
||||
| Mobile access | Yes — Android; iOS controller-only | Yes, via mobile apps ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| File transfer | Yes (both directions) | Yes ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| In-session chat | Yes — text chat | Yes, real-time chat; VoIP/video/chat are disabled for free users ([support](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/remote-control/remote-session-toolbar/)) |
|
||||
| Session recording | Yes (can auto-record incoming/outgoing) | Yes ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| Remote printing | Yes (remote printer for incoming connections) | Yes ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| Multi-monitor support | Yes — multi-monitor | Yes — 4K multi-monitor ([features](https://www.teamviewer.com/en-us/products/remote/features/)) |
|
||||
| Concurrent-session cap | Unlimited on standard plans; limited on [Customized V2](https://rustdesk.com/pricing#custom2) | Capped by plan tier (see [licensing](#licensing-and-pricing-models)) |
|
||||
|
||||
Two rows deserve extra attention because they are where the products diverge most in practice.
|
||||
|
||||
@@ -65,7 +73,7 @@ First, **concurrent connections.** TeamViewer's commercial model meters simultan
|
||||
|
||||
If concurrency limits are the specific pain that sent you looking, we go deeper on the mechanics in [Does RustDesk Limit Concurrent Connections?](/blog/rustdesk-concurrent-connections-limit).
|
||||
|
||||
Second, the **feature-parity question.** TeamViewer's breadth here is real and is a legitimate reason some teams stay: session recording for compliance, remote printing, 4K multi-monitor, and a polished mobile experience are all mature. We are not going to overstate RustDesk's feature list to match it — the honest position is that RustDesk covers the core remote-control and unattended-access workflows that most support and admin teams live in every day, and you should trial it against your actual tasks rather than take any table's word for it. That is why we point evaluators to sales@rustdesk.com for a test license rather than a signed contract: see [See RustDesk in Action](/blog/see-rustdesk-in-action).
|
||||
Second, the **feature-parity question.** Both products cover the day-to-day workflows most support and admin teams live in — remote control, unattended access, file transfer, session recording, remote printing, and multi-monitor. Rather than take any table's word for it, trial RustDesk against your actual tasks; that is why we point evaluators to sales@rustdesk.com for a test license rather than a signed contract: see [See RustDesk in Action](/blog/see-rustdesk-in-action).
|
||||
|
||||
## Operating system and platform support
|
||||
|
||||
@@ -73,11 +81,11 @@ Both tools cover the major desktop and mobile platforms; the details differ at t
|
||||
|
||||
| Platform | RustDesk | TeamViewer |
|
||||
| --------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Windows | Yes | Yes, incl. Windows Server 2016/2019/2022 ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| macOS | Yes | Yes, macOS 13 (Ventura) and later ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| Linux | Yes | Yes, but via TeamViewer Classic with more limited functionality ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| Android | Yes | Yes, Android 8+ ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| iOS / iPadOS | Yes | Yes, iOS/iPadOS 15+ ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| Windows | Yes — x64, ARM64, 32-bit | Yes, incl. Windows Server 2016/2019/2022 ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| macOS | Yes — Apple Silicon & Intel | Yes, macOS 13 (Ventura) and later ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| Linux | Yes — x86_64, ARM64 & ARM32; strong Wayland | Yes, but via TeamViewer Classic with more limited functionality ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| Android | Yes — arm64, arm32, x64 (host & controller) | Yes, Android 8+ ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| iOS / iPadOS | Controller only (no host, per Apple restrictions) | Yes, iOS/iPadOS 15+ ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| ChromeOS | Not verified for this article | Yes, but screen sharing only — full remote control not officially supported ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
| Raspberry Pi OS | Not verified for this article | Yes, via TeamViewer Classic ([supported OS](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-remote/download-and-installation/supported-operating-systems-for-teamviewer-remote/)) |
|
||||
|
||||
@@ -103,24 +111,14 @@ Pricing is the single most volatile part of any remote-access comparison, so we
|
||||
|
||||
**TeamViewer's model** is subscription-based and organized around named tiers plus concurrent-session limits. Packaging and prices vary by region and term, so use TeamViewer's current pricing page and your written quote rather than historical third-party figures or private customer invoices.
|
||||
|
||||
**A note on TeamViewer's older "lifetime" licenses.** Many teams first adopted TeamViewer under a **perpetual license** — a one-time purchase tied to a specific major version. TeamViewer no longer sells perpetual licenses; it is subscription-only now, and an old perpetual license remains usable only on the version it was originally valid for, subject to TeamViewer's product-lifecycle policy. In practice, end-of-support actions have cut older clients off from TeamViewer's network, and a class-action complaint filed in a U.S. federal court in March 2026 alleges this effectively forced perpetual-license holders to either lose remote access or move to a subscription (the allegations are unproven). Whatever its outcome, "the perpetual license I paid for no longer connects" is one of the more common reasons we see teams start shopping. It is only fair to add that RustDesk is not a perpetual-forever product either: the community server is free and open source with no expiry, but the commercial Server Pro terms are annual, not a lifetime buyout. ([TeamViewer subscription FAQ](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-classic/licensing/subscription/all-about-subscription/), [class-action report](https://www.classaction.org/news/teamviewer-removed-functionality-from-paid-for-perpetual-software-licenses-class-action-lawsuit-claims))
|
||||
|
||||
**RustDesk's model** is different in two ways. First, commercial plans count **login users plus managed devices**. Standard plans include unlimited concurrent connections; Customized V2 has a defined concurrency allowance. Upgrades can be prorated, so confirm the current mid-term terms on the pricing page. Second, the community server has no license fee, while Server Pro is the commercial option for centralized features. RustDesk does not publish a fixed self-serve Server Pro trial; ask for current evaluation terms before planning a proof of concept. Payment mechanics are covered in [RustDesk Pro Pricing: Cost & How to Pay](/blog/rustdesk-pro-license-cost-how-to-pay).
|
||||
|
||||
If your starting point is TeamViewer's cost, see [TeamViewer Too Expensive? Your Real Options in 2026](/blog/teamviewer-too-expensive-alternatives) and compare current quotes.
|
||||
|
||||
There is also a free-tier wrinkle. TeamViewer's free tier is for personal, non-commercial use, and suspected commercial use can restrict sessions. TeamViewer does not publish a threshold formula users can rely on. A genuine false positive should go through the official reset process; actual business use requires commercial terms. ([TeamViewer: commercial use suspected](https://www.teamviewer.com/en-us/global/support/knowledge-base/teamviewer-classic/licensing/personal-use/commercial-use-suspected/)) See [TeamViewer Commercial Use Detected](/blog/teamviewer-commercial-use-detected) for the focused workflow.
|
||||
|
||||
## Where TeamViewer still wins
|
||||
|
||||
An honest comparison has to include the cases where the incumbent is the better choice. TeamViewer is not the default for millions of installs by accident.
|
||||
|
||||
- **Maturity and polish.** Two decades of development show up in the small things — connection reliability across bad networks, 4K multi-monitor handling, mobile apps, and a UI that non-technical end users navigate without hand-holding.
|
||||
- **A deep integration ecosystem.** If your service desk lives in ServiceNow, Jira, or Microsoft Intune — or you want RMM, SSO, and SIEM hooks wired together out of the box — TeamViewer (especially Tensor) has a large catalog of native integrations that would otherwise be build-it-yourself work. ([TeamViewer integrations](https://www.teamviewer.com/en/integrations/))
|
||||
- **Zero server maintenance.** Because TeamViewer runs the brokering infrastructure, there is no server for you to provision, patch, secure, monitor, or scale. For a small team without dedicated ops capacity, "someone else runs it" is a real, ongoing benefit, not just a convenience.
|
||||
- **Compliance paperwork ready to go.** SOC 2, ISO/IEC 27001, HIPAA/HITECH and similar certifications are already in place, which can shorten a procurement or audit conversation.
|
||||
- **Managed reliability.** A commercial SaaS with an SLA and 24/7 support tiers is a different operational proposition from software you host yourself and are on the hook for at 2 a.m.
|
||||
|
||||
If those points describe your situation more than the cost-and-control complaints at the top of this article, TeamViewer may well be the right answer, and there is no shame in that conclusion.
|
||||
|
||||
## Pros and cons
|
||||
|
||||
**RustDesk**
|
||||
@@ -137,24 +135,22 @@ _Pros_
|
||||
|
||||
_Cons_
|
||||
|
||||
- Self-hosting means **you** run, patch, secure, and scale the server (see the caveat below)
|
||||
- Smaller third-party integration catalog than TeamViewer's enterprise ecosystem
|
||||
- Some conveniences a mature commercial suite bundles may need verification against your specific workflow before you rely on them
|
||||
- Self-hosting means you run, patch, and update the server yourself
|
||||
|
||||
**TeamViewer**
|
||||
|
||||
_Pros_
|
||||
|
||||
- Mature, polished, and widely trusted, with strong cross-platform reach
|
||||
- Robust security features: AES-256 session encryption, RSA-4096 key exchange, optional end-to-end encryption, TOTP 2FA, and broad compliance certifications
|
||||
- Large native integration ecosystem (ServiceNow, Jira, Intune, RMM, SSO/SIEM via Tensor)
|
||||
- Fully managed SaaS — no server for you to maintain
|
||||
- AES-256 session encryption, RSA-4096 key exchange, optional end-to-end encryption, and TOTP 2FA
|
||||
- Published compliance certifications (SOC 2, ISO/IEC 27001, HIPAA/HITECH)
|
||||
- Native integrations with ServiceNow, Jira, Intune, and others via Tensor
|
||||
- Fully managed SaaS — no server for you to run
|
||||
|
||||
_Cons_
|
||||
|
||||
- Closed-source; you trust the vendor's infrastructure and their handling of your session metadata
|
||||
- Concurrent sessions are metered by plan tier
|
||||
- Recurring annual subscription cost that teams repeatedly tell us feels disproportionate to simple needs
|
||||
- Recurring annual subscription with no perpetual-license option
|
||||
- Free tier is personal-use only and can flag legitimate users for "commercial use," interrupting sessions
|
||||
- Its corporate network was breached by APT29 in June 2024 (contained to internal IT, per TeamViewer) — a reminder that a centralized vendor is itself a high-value target
|
||||
|
||||
@@ -172,12 +168,21 @@ Everything above is the neutral part. The following section explains which buyer
|
||||
|
||||
**They are MSPs or enterprises who want one brandable, self-hosted tool.** For managed service providers, the custom-branded client generator, device groups, and shared address book turn RustDesk into a white-label support platform — see [RustDesk for MSPs](/blog/rustdesk-for-msps). For larger organizations that need AD/LDAP and room to grow, see [RustDesk for Enterprise](/blog/rustdesk-for-enterprise).
|
||||
|
||||
If infrastructure control is not a priority, TeamViewer may remain the better fit. See [RustDesk vs AnyDesk](/blog/rustdesk-vs-anydesk), [RustDesk vs ScreenConnect](/blog/rustdesk-vs-screenconnect), and [The Best Self-Hosted TeamViewer Alternative](/blog/self-hosted-teamviewer-alternative).
|
||||
Comparing other options too? See [RustDesk vs AnyDesk](/blog/rustdesk-vs-anydesk), [RustDesk vs ScreenConnect](/blog/rustdesk-vs-screenconnect), and [The Best Self-Hosted TeamViewer Alternative](/blog/self-hosted-teamviewer-alternative).
|
||||
|
||||
## An honest caveat about self-hosting
|
||||
## It comes down to control
|
||||
|
||||
We would rather you hear this from us than discover it later. Self-hosting RustDesk means you own the server. You provision it, you patch it, you secure it, you monitor it, and you scale it. That is the trade you make in exchange for control and the absence of a concurrency meter — it is real work, and it is emphatically **not** the zero-maintenance, someone-else-runs-it experience that a managed SaaS like TeamViewer provides. If your team has no appetite or capacity to run a small piece of infrastructure, that fact should weigh heavily in your decision, and one of TeamViewer's genuine advantages is that it removes this burden entirely. Choose with eyes open.
|
||||
Past the feature tables, the real split is where things run: TeamViewer's cloud, or a server you own. If your objection was ever about control — of data, of cost, of the software itself — that is the line that matters.
|
||||
|
||||
## Try RustDesk yourself
|
||||
|
||||
Self-host the free community server today. Want to try the Pro features? Email [sales@rustdesk.com](mailto:sales@rustdesk.com) to ask about current evaluation terms, or check [rustdesk.com/pricing](https://rustdesk.com/pricing) for standard plan rates. Prefer to watch first? There's a full video walkthrough on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk) — no booking required.
|
||||
The free community server is yours to stand up today at no cost. Want the Pro features? Ask [sales@rustdesk.com](mailto:sales@rustdesk.com) about evaluation terms, or check [rustdesk.com/pricing](https://rustdesk.com/pricing) for plan rates — and there's a full [video walkthrough](https://www.youtube.com/@rustdesk) if you'd rather see it running first.
|
||||
|
||||
|
||||
## Related reading
|
||||
|
||||
- [RustDesk vs AnyDesk](/blog/rustdesk-vs-anydesk)
|
||||
- [RustDesk vs ScreenConnect](/blog/rustdesk-vs-screenconnect)
|
||||
- [The Best Self-Hosted TeamViewer Alternative](/blog/self-hosted-teamviewer-alternative)
|
||||
- [TeamViewer Too Expensive? Your Real Options](/blog/teamviewer-too-expensive-alternatives)
|
||||
- [TeamViewer Commercial Use Detected](/blog/teamviewer-commercial-use-detected)
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-07-09T18:44:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-vs-vnc
|
||||
draft: false
|
||||
title: 'RustDesk vs VNC: NAT Traversal, Codecs, Encryption'
|
||||
excerpt: "RustDesk vs VNC compared honestly: NAT traversal without port-forwarding, modern codecs, built-in encryption, and where VNC's simplicity still wins."
|
||||
excerpt: "RustDesk vs VNC compared honestly: NAT traversal without port-forwarding, modern codecs, built-in encryption, and why teams move from VNC to RustDesk."
|
||||
image: ~/assets/images/blog/rustdesk-vs-vnc-og.png
|
||||
category: Comparisons
|
||||
tags:
|
||||
@@ -69,17 +69,6 @@ RustDesk applies **end-to-end encryption by default** on every connection, self-
|
||||
|
||||
Confirm current RustDesk plan details at [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
## Where VNC still wins — honestly
|
||||
|
||||
VNC has survived for decades for good reasons, and they deserve to be stated plainly:
|
||||
|
||||
- **Dead-simple on a LAN.** Install a server, point a viewer at an IP, done. For a trusted local network there is very little ceremony.
|
||||
- **Ubiquity and a real standard.** RFB is an open, published protocol with interoperable clients and servers across nearly every platform, including embedded devices and the Raspberry Pi. Any RFB viewer talks to any RFB server.
|
||||
- **Fully-FOSS options exist.** If you want a completely open-source server today, TigerVNC (GPL) and TightVNC are already there, with no relay infrastructure to run.
|
||||
- **No dependency on a broker.** A LAN-only VNC setup has no rendezvous server in the path at all — appealing for air-gapped or tightly segmented networks.
|
||||
|
||||
If your use case is "control the Linux box on the next rack" or "reach a Pi on my home network," VNC may be all you ever need, and RustDesk's extra machinery buys you little.
|
||||
|
||||
## Where RustDesk pulls ahead
|
||||
|
||||
RustDesk's design advantages appear the moment you leave the LAN or need consistency across teams and platforms:
|
||||
@@ -89,7 +78,7 @@ RustDesk's design advantages appear the moment you leave the LAN or need consist
|
||||
- **Modern codecs.** VP8/VP9/AV1 and hardware H.264/H.265 tend to hold up better over constrained or high-latency links than raw pixel encodings.
|
||||
- **One auditable app and one self-hosted server.** The AGPL client plus a self-hosted ID/relay keeps both the code and your session data on infrastructure you control — the heart of the [open-source remote desktop](/blog/open-source-remote-desktop-software) argument.
|
||||
|
||||
The honest caveat: self-hosting RustDesk means **someone runs the server** — provisioning, TLS, ports, and patching over time. A LAN-only VNC setup skips that entirely. That is the real trade.
|
||||
The trade: self-hosting RustDesk means **someone runs the server** — provisioning, TLS, ports, and patching over time. A LAN-only VNC setup skips that entirely. That is the real trade.
|
||||
|
||||
## So which should you use?
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-28T18:34:00Z
|
||||
lang: en
|
||||
translationKey: rustdesk-web-console-custom-client-generator-port-21114
|
||||
draft: false
|
||||
@@ -20,6 +20,16 @@ faq:
|
||||
answer: 'If none of the URLs respond, the container is usually running but the port is closed. Confirm the Pro container is up and that TCP 21114 is open end to end — in the host firewall and in any cloud security group or NAT/forwarding rule in front of the server. A blocked or unforwarded 21114 is the typical cause.'
|
||||
- question: 'Which ports does RustDesk Server Pro need open besides 21114?'
|
||||
answer: 'Besides the Web Console on 21114 (or 443 behind a reverse proxy), Server Pro also needs its standard ID/rendezvous and relay ports open for clients to connect. Exact port numbers change between releases, so check the current RustDesk docs for the full list before locking down your firewall.'
|
||||
- question: 'Can I white-label or rebrand the RustDesk client?'
|
||||
answer: 'Yes, on Basic and higher plans. The Custom Client Generator lets you set your own client name, logo, and icon and bake in preset settings such as the server address, address book, device group, or strategy, so the client is branded and pre-configured before users install it. The Individual tier includes the Web Console but not the generator.'
|
||||
- question: "Why is my custom RustDesk client built on RustDesk's servers instead of my own?"
|
||||
answer: "Chiefly because of cross-platform builds: from one configuration the generator can produce clients for Windows, macOS, Linux, and Android, and you cannot cross-compile and sign all of those targets on a single operating system — a Windows build needs Windows and a code-signing certificate, a macOS build needs Apple hardware and an Apple Developer account for notarization, and so on. Because those platform-specific requirements cannot be met on a Linux server alone, RustDesk runs the complete multi-platform build environment centrally and returns the signed installers for you to download."
|
||||
- question: 'How long is a generated custom client available to download?'
|
||||
answer: 'About a day. Generated builds are automatically deleted from the build server after roughly 24 hours, so download the installer and save it locally as soon as it is ready, then re-generate it later if you need it again.'
|
||||
- question: 'Is my custom-client build configuration saved by RustDesk?'
|
||||
answer: "No. The build configuration you submit is not stored on RustDesk's build server — it is deleted automatically once the build finishes, so your branding, server address, and preset settings do not linger on RustDesk infrastructure."
|
||||
- question: 'What is the RustDesk web client, and which plan includes it?'
|
||||
answer: 'The web client lets you start and run remote sessions from a browser tab, with nothing to install on the controlling side — distinct from the web console, which is the admin site on port 21114. It is a controller: it can drive other devices, but a browser tab cannot act as an unattended host. Self-hosting it (served from your own server at https://your-server/web) requires a plan large enough to satisfy (users × 10) + devices ≥ 400; the RustDesk web client V2 preview article covers self-hosting, customization, and pointing the public client at your own server.'
|
||||
- question: 'I changed the admin password and locked myself out — how do I reset it?'
|
||||
answer: 'Admin password recovery depends on how your Server Pro instance is deployed and stored, and the procedure can change between releases. Rather than following an outdated screenshot, check the current RustDesk Server Pro docs for the supported reset path, or contact RustDesk support with non-sensitive deployment details.'
|
||||
|
||||
@@ -38,11 +48,34 @@ Port 21114 serves plain HTTP and can be used to confirm that the console is reac
|
||||
|
||||
Port 21114 serves HTTP by default; it does not automatically provision a certificate for a bare domain. For production HTTPS, put the console behind a supported reverse proxy such as Nginx or IIS, install a valid certificate, expose port 443, and configure the client API address accordingly.
|
||||
|
||||
If none of the three addresses respond, the container is reachable but the port likely isn't. Confirm the Pro container is running, and make sure TCP 21114 is open end to end - both in the host firewall and in any cloud security group or NAT rule in front of the server. A blocked or unforwarded 21114 is the typical culprit behind "port not available."
|
||||
If the console does not respond, the container is reachable but the port likely isn't. Confirm the Pro container is running, and make sure TCP 21114 is open end to end - both in the host firewall and in any cloud security group or NAT rule in front of the server. A blocked or unforwarded 21114 is the typical culprit behind "port not available."
|
||||
|
||||
Initial admin credentials should be treated as temporary, but changing them after an exposed HTTP login does not undo credential or session interception. First establish HTTPS or one of the protected bootstrap paths above; then sign in, change the password immediately, and move on to generating clients.
|
||||
|
||||
On Basic and higher plans, the Custom Client Generator lets you produce branded, pre-configured client builds so end users do not need to enter server settings manually. Individual includes the Web Console but not the generator.
|
||||
On Basic and higher plans, the Custom Client Generator lets you produce **branded, pre-configured client builds** so end users do not need to enter server settings manually. You can white-label the client — set your own name, logo, and icon — and bake in preset configuration (for example the server address, an address book, a device group, or a strategy) so the client is ready to connect the moment it is installed rather than requiring per-machine setup. Individual includes the Web Console but not the generator. For pushing those builds across a fleet, see [mass deployment via MSI, GPO, and Intune](/blog/rustdesk-for-enterprise).
|
||||
|
||||
## How the custom client is built — and what happens to your data
|
||||
|
||||
One detail catches people off guard: the custom client is **compiled on RustDesk's build server, not on your own Server Pro.** The reason is **cross-platform builds.** From a single branding configuration the generator produces clients for Windows, macOS, Linux, and Android, and no single machine can cross-compile and sign all of those targets — each one needs its own operating system, toolchain, and signing credentials:
|
||||
|
||||
- **Windows** builds must run on Windows with a full development environment (Visual Studio, the Windows SDK, build tools) and a valid **code-signing certificate**.
|
||||
- **macOS** (and iOS) builds must run on Apple hardware with a separate toolchain (Xcode and its command-line tools) and an **Apple Developer account** for notarization and signing.
|
||||
|
||||
As the RustDesk maintainers put it, these "platform-specific requirements cannot be fully satisfied on a Linux server alone." You could in principle stitch together paid CI/CD runners for each platform, but it is costly — their blunt summary is that _"cross-platform desktop distribution is painful and expensive by design, and there's no way around it if you want officially signed, store-ready, or notarized binaries."_ So RustDesk runs the complete multi-platform build environment centrally: the generator sends your branding and preset configuration to RustDesk's build service, which compiles the signed installers and makes them available to download. ([RustDesk maintainers, discussion #866](https://github.com/rustdesk/rustdesk-server-pro/discussions/866#discussioncomment-15220939))
|
||||
|
||||
Two consequences follow, and both matter:
|
||||
|
||||
- **Download and keep the installer — it isn't stored for long.** A generated build is available for a limited window (about a day) and is then automatically deleted from the build server. As soon as your build is ready, download the installer and save it somewhere you control; don't rely on it staying available, and simply re-generate it if you need it again later.
|
||||
- **Your configuration isn't retained.** The build configuration you submit is **not saved** on RustDesk's build server — it is deleted automatically once the build finishes. Your branding, server address, and preset settings do not linger on RustDesk infrastructure after the installer is produced.
|
||||
|
||||
## The web client vs the web console
|
||||
|
||||
It is easy to conflate two Server Pro features that both live in the browser:
|
||||
|
||||
- The **web console** — this article's subject, on port 21114 (or 443 behind a proxy) — is the **admin** site, where you manage users, devices, permissions, strategies, and licenses.
|
||||
- The **web client** is different: it lets you **start and run remote sessions from a browser tab**, with nothing to install on the controlling side. It is a controller — you can drive other devices from the browser, but a browser tab cannot act as an unattended host.
|
||||
|
||||
Self-hosting the web client (serving it from your own server at `https://your-server/web`) requires a plan large enough to satisfy **(users × 10) + devices ≥ 400** (for example 10 users / 300 devices, or 20 users / 200 devices), and you can alternatively point the public browser client at your own server or customize a self-hosted one. The [web client V2 preview](/blog/rustdesk-web-client-v2-preview) covers all of that — access, WSS/CORS setup, self-hosting, and customization.
|
||||
|
||||
## Who asks this
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-30T17:15:00Z
|
||||
lang: en
|
||||
translationKey: see-rustdesk-in-action
|
||||
draft: false
|
||||
@@ -10,6 +10,16 @@ category: Guides
|
||||
tags:
|
||||
- RustDesk
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'How can I see a RustDesk demo?'
|
||||
answer: 'The RustDesk YouTube channel has videos covering the product and the Pro feature set — the web console, custom client generator, address book, and access control — so you can watch it running before you install anything.'
|
||||
- question: 'Can I try RustDesk for free?'
|
||||
answer: "Yes. RustDesk's core is open source, so you can stand up the free community server today and connect your own machines with no license, no time limit, and no cost. You can audit the code while you're at it."
|
||||
- question: 'How do I evaluate the RustDesk Pro features?'
|
||||
answer: 'Check the current evaluation terms on rustdesk.com/pricing or email sales@rustdesk.com, then spin up the server, point a few devices at it, and decide for yourself.'
|
||||
- question: 'Do I need a sales call to try RustDesk?'
|
||||
answer: 'No. You can watch the demo video for a tour, self-host the free server to test hands-on, and confirm the current Pro evaluation path when you need the full feature set.'
|
||||
|
||||
metadata:
|
||||
description: 'Three ways to see RustDesk in action: watch the demo video, self-host the free open-source server, and confirm the current Server Pro evaluation path.'
|
||||
keywords: 'RustDesk demo, see RustDesk in action, evaluate RustDesk, RustDesk Pro demo, try RustDesk, RustDesk evaluation'
|
||||
@@ -33,6 +43,6 @@ When you're ready to evaluate the paid features — the self-hosted web console,
|
||||
|
||||
## Have questions? Talk to the team directly
|
||||
|
||||
If you still have questions about pricing, licensing, deployment, or feature fit, use the current pricing page, docs, and contact channels to confirm the details that matter to your evaluation.
|
||||
If you still have questions about pricing, licensing, deployment, or feature fit, email [sales@rustdesk.com](mailto:sales@rustdesk.com) for pricing and licensing, [support@rustdesk.com](mailto:support@rustdesk.com) for deployment help, or check [rustdesk.com/pricing](https://rustdesk.com/pricing) and the [docs](https://rustdesk.com/docs/en/) to confirm the details that matter to your evaluation.
|
||||
|
||||
So the evaluation path is simple: **watch the video for the tour, self-host the free server to test hands-on, and confirm the current Pro evaluation path when you need the full feature set.**
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-03T18:08:00Z
|
||||
lang: en
|
||||
translationKey: self-host-rustdesk-server-hardware-at-scale
|
||||
draft: false
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-06-30T15:11:00Z
|
||||
lang: en
|
||||
translationKey: self-hosted-teamviewer-alternative
|
||||
draft: false
|
||||
@@ -13,6 +13,18 @@ tags:
|
||||
- alternative
|
||||
- self-hosting
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Is RustDesk a good self-hosted TeamViewer alternative?'
|
||||
answer: "RustDesk Server Pro is self-hosted by design — the ID/rendezvous server, relay, console, and stored data run on infrastructure you control — and its core client is open source under the AGPL. It answers the two reasons teams leave TeamViewer: cost and control."
|
||||
- question: 'Can I self-host a TeamViewer alternative on my own servers?'
|
||||
answer: 'Yes. With RustDesk Server Pro you host the servers yourself, on-prem or on a VPS, and you can run the free open-source community server indefinitely. Someone on your side provisions the host, opens ports, sets up TLS, and keeps it patched.'
|
||||
- question: "How does RustDesk licensing compare to TeamViewer's per-seat subscription?"
|
||||
answer: 'RustDesk licenses per login-user plus per managed-device, with unlimited concurrent connections on standard plans and a defined allowance on Customized V2; mid-term upgrades may be prorated under current terms. Model all three counts against the current pricing page.'
|
||||
- question: 'Does RustDesk work for MSPs and larger IT operations?'
|
||||
answer: 'Yes. It includes a self-hosted web console, a custom-branded client generator, and device groups with a shared address book for per-user access control, plus LDAP/SSO (OIDC) from the Basic plan and up. Large-fleet planning starts around 50,000 managed devices, with larger estates requiring validation.'
|
||||
- question: 'Does self-hosting help keep my data in-country and support GDPR?'
|
||||
answer: 'Yes — you control the rendezvous, relay, console, and stored device data, which is a strong foundation. It is not an absolute guarantee, though: direct connections still flow between endpoints, so keeping traffic in-country and satisfying GDPR obligations also depends on how you route and operate the deployment.'
|
||||
|
||||
metadata:
|
||||
description: 'Looking for a self-hosted TeamViewer alternative? RustDesk is open-source, runs on your servers, and has no per-channel cloud subscription. See how it compares.'
|
||||
keywords: 'self-hosted TeamViewer alternative, TeamViewer replacement, open source TeamViewer alternative'
|
||||
@@ -20,7 +32,7 @@ metadata:
|
||||
|
||||
The search for a **self-hosted TeamViewer alternative** usually starts the same way: a renewal quote no longer matches the workflows you use, and the product still routes your sessions through infrastructure you do not control. Cost and control are the two reasons teams start looking in the first place.
|
||||
|
||||
If you're one of them, this page is for you. Below is an honest look at why teams leave TeamViewer, how a self-hosted, open-source model changes the equation, and where RustDesk fits (including where it doesn't).
|
||||
If you're one of them, this page is for you: why teams leave TeamViewer, how a self-hosted, open-source model changes the equation, and where RustDesk fits.
|
||||
|
||||
## Why teams leave TeamViewer
|
||||
|
||||
@@ -38,7 +50,7 @@ RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-deskto
|
||||
|
||||
Underneath, RustDesk's core client is open source under the [AGPL](/blog/case-for-open-source-remote-access). You can read the code, audit exactly what the client does on your machines, build it yourself, and run the free community server indefinitely. That's a different trust model than a closed cloud product: you don't have to take our word for what the software does, because you can look.
|
||||
|
||||
It's also the reason security incidents in this category — such as [AnyDesk's 2024 security incident](https://www.infosecurity-magazine.com/news/anydesk-hit-cyberattack-customer/), or the [2024 ConnectWise ScreenConnect vulnerability](https://www.cisa.gov/news-events/alerts/2024/02/22/cisa-adds-one-known-exploited-connectwise-vulnerability-cve-2024-1709-catalog) — land differently when the software is auditable and the servers are yours. (See the caveat section: self-hosting shifts responsibility to you, too.)
|
||||
It's also the reason security incidents in this category — such as [AnyDesk's 2024 security incident](https://www.infosecurity-magazine.com/news/anydesk-hit-cyberattack-customer/), or the [2024 ConnectWise ScreenConnect vulnerability](https://www.cisa.gov/news-events/alerts/2024/02/22/cisa-adds-one-known-exploited-connectwise-vulnerability-cve-2024-1709-catalog) — land differently when the software is auditable and the servers are yours.
|
||||
|
||||
## RustDesk vs TeamViewer at a glance
|
||||
|
||||
@@ -47,7 +59,7 @@ It's also the reason security incidents in this category — such as [AnyDesk's
|
||||
| Where sessions run | Vendor cloud | Your server (on-prem or your VPS) |
|
||||
| Source code | Closed | Open source (AGPL) core |
|
||||
| Licensing model | Per-seat cloud subscription | [Per login-user + per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Plan-dependent | Unlimited on standard plans; limited on Customized V2 |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Plan-dependent | Unlimited on standard plans; limited on [Customized V2](https://rustdesk.com/pricing#custom2) |
|
||||
| Server-side data location | Vendor-controlled | Chosen and operated by you; endpoint routes still matter |
|
||||
| Try before you buy | Sales-led | Free server today, or Pro trial on request |
|
||||
|
||||
@@ -67,11 +79,9 @@ Because you host the servers, you control the rendezvous, relay, console, and st
|
||||
|
||||
For teams supporting many clients, RustDesk includes a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114), a custom-branded client generator, and device groups with a [shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book) for per-user access control. [LDAP/SSO](/blog/rustdesk-active-directory-ldap-sso) (OIDC) is available from the Basic plan and up. That's how the "one console, many technicians, many [managed devices](/blog/what-counts-as-a-managed-device)" workflow that TeamViewer users expect gets rebuilt on infrastructure you own. For exact feature availability by plan, [see rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
## The honest caveat: someone has to run the server
|
||||
## Everything TeamViewer does, on your box
|
||||
|
||||
Self-hosting is the whole point — and it's also the trade-off. Someone on your side runs the server: you provision a host, open ports, set up TLS, and keep it patched. That's straightforward for most IT teams and [MSPs](/blog/rustdesk-for-msps), but it's real work.
|
||||
|
||||
If what you actually want is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run, be clear-eyed: RustDesk Server Pro is self-hosted by design and is not that. The upside of owning your infrastructure comes with the responsibility of operating it. We'd rather you know that going in than be surprised later.
|
||||
The switch trades a vendor-run cloud for a server you operate: the same everyday support, but the coordination, the data, and the cost model are yours. For teams leaving a climbing subscription, that is what makes it stick.
|
||||
|
||||
## TeamViewer migration plan
|
||||
|
||||
@@ -96,4 +106,4 @@ You don't need to talk to anyone to evaluate RustDesk:
|
||||
- **Want to try the Pro features?** Email [sales@rustdesk.com](mailto:sales@rustdesk.com) to ask about current evaluation terms, or check [rustdesk.com/pricing](https://rustdesk.com/pricing) for standard plan rates.
|
||||
- **Prefer to see it first?** Watch a full [video demo](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk) — no booking required.
|
||||
|
||||
If cost and control are why you're leaving TeamViewer, a self-hosted, open-source alternative is worth an afternoon of your time.
|
||||
If cost and control are why you're leaving TeamViewer, a self-hosted, open-source alternative is worth a proof of concept on your own hardware.
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-03T09:34:00Z
|
||||
lang: en
|
||||
translationKey: teamviewer-commercial-use-detected
|
||||
draft: false
|
||||
@@ -12,6 +12,18 @@ tags:
|
||||
- troubleshooting
|
||||
- licensing
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'How do I fix "commercial use detected" on TeamViewer?'
|
||||
answer: 'TeamViewer publishes an official reset/appeal process: go to teamviewer.com/reset, enter your name and the email on your account, briefly describe your actual usage, list every TeamViewer ID involved, then accept the privacy policy and submit. TeamViewer states a review-time target (about a week at the time of writing); confirm the current figure on its reset page.'
|
||||
- question: 'What counts as commercial use in TeamViewer?'
|
||||
answer: "Per TeamViewer's own definitions, commercial use includes providing support to clients or customers, working from home (even just checking work email), any inbound or outbound connection in a commercial setting, server administration or monitoring, and salaried work at a non-profit. Personal use means helping family and friends or connecting to your own non-server devices."
|
||||
- question: 'Will the reset request work if my use is genuinely commercial?'
|
||||
answer: 'No. The appeal only helps when the flag was a false positive; if your actual usage is commercial, TeamViewer will correctly identify it, and the real fix is choosing a tool licensed for how you actually use it.'
|
||||
- question: 'Does RustDesk have a commercial-use detector?'
|
||||
answer: "No. RustDesk's community server can be self-hosted without a commercial-use classifier, while Server Pro is licensed by login users and managed devices, with unlimited concurrent connections on standard plans and a defined allowance on Customized V2."
|
||||
- question: 'Can I avoid the flag with ID-reset scripts or by deleting config files?'
|
||||
answer: 'No. Do not use unofficial ID-reset scripts or delete configuration files to evade the classification; they do not change the license terms and can create additional security or support problems.'
|
||||
|
||||
metadata:
|
||||
description: "Flagged for 'commercial use detected' on TeamViewer? Here's the official reset process, what counts as commercial use, and how self-hosted RustDesk avoids it."
|
||||
keywords: 'TeamViewer commercial use detected, TeamViewer reset commercial use, TeamViewer commercial use appeal, TeamViewer personal use flagged'
|
||||
@@ -28,10 +40,10 @@ TeamViewer publishes an official [reset/appeal process](https://www.teamviewer.c
|
||||
1. **Go to [teamviewer.com/reset](https://teamviewer.com/reset)** and click the start button.
|
||||
2. **Enter your name and the email address on your TeamViewer account.**
|
||||
3. **Briefly describe your actual usage pattern** — e.g. "I only use this to help my elderly parent with their PC," or whatever genuinely describes what you're doing.
|
||||
4. **List every TeamViewer ID involved**, both the device you connect _from_ and any you connect _to_ (the form currently accepts up to 10 IDs per submission).
|
||||
4. **List every TeamViewer ID involved**, both the device you connect _from_ and any you connect _to_ (the form accepts a limited number of IDs per submission).
|
||||
5. **Accept the privacy policy and submit.**
|
||||
|
||||
TeamViewer states they aim to review requests within **seven business days** at the time of writing, though it can take longer during high-volume periods — check your spam folder if you don't hear back within a week. One of two things happens next: either they reset your ID because personal use is confirmed, or they decline the reset and offer you a "declaration of private use" to sign instead. If your actual usage is commercial, neither outcome changes that — the appeal only helps when the flag was a false positive.
|
||||
TeamViewer states a review-time target of roughly a week at the time of writing, though it can take longer during high-volume periods — check your spam folder if you don't hear back. One of two things happens next: either they reset your ID because personal use is confirmed, or they decline the reset and offer you a "declaration of private use" to sign instead. If your actual usage is commercial, neither outcome changes that — the appeal only helps when the flag was a false positive.
|
||||
|
||||
### What actually counts as "commercial use" here
|
||||
|
||||
@@ -63,7 +75,7 @@ When the usage is genuinely commercial, there is no legitimate reset workaround.
|
||||
| Choose another managed SaaS | You want no server operations but a different commercial offer | Sessions and administration remain vendor-operated |
|
||||
| Pilot a self-hosted tool | You want to operate the ID, relay, console, and deployment data | Your team owns hosting, patching, certificates, monitoring, and recovery |
|
||||
|
||||
RustDesk belongs in the third row. Its community server can be self-hosted without a commercial-use classifier, while Server Pro is licensed by login users and managed devices. Standard plans include unlimited concurrent connections; Customized V2 has a defined allowance. Direct sessions still flow between endpoints, and Server Pro's commercial license terms still apply.
|
||||
RustDesk belongs in the third row. Its community server can be self-hosted without a commercial-use classifier, while Server Pro is licensed by login users and managed devices. Standard plans include unlimited concurrent connections; [Customized V2](https://rustdesk.com/pricing#custom2) has a defined allowance. Direct sessions still flow between endpoints, and Server Pro's commercial license terms still apply.
|
||||
|
||||
## A safe migration path
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-08T18:30:00Z
|
||||
lang: en
|
||||
translationKey: teamviewer-too-expensive-alternatives
|
||||
draft: false
|
||||
@@ -13,6 +13,18 @@ tags:
|
||||
- pricing
|
||||
- alternative
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Why does TeamViewer feel so expensive at renewal?'
|
||||
answer: 'Cloud-subscription remote-desktop tools are priced around tiers, seats, and add-on modules, so the bill can keep climbing whether or not your usage grows. The frustration is usually the pricing model, not the software.'
|
||||
- question: 'Is RustDesk cheaper than TeamViewer?'
|
||||
answer: 'RustDesk moves hosting into your own cost model and licenses per login-user plus per managed-device, with unlimited concurrent connections on standard plans. Self-hosting adds two modest line items: a small server — hardware requirements are low, so an inexpensive VPS usually suffices — and mostly one-time setup, with light upkeep after. Build a comparable three-year TCO and see rustdesk.com/pricing for current figures.'
|
||||
- question: 'What recurring costs does self-hosting RustDesk remove?'
|
||||
answer: 'Moving to a self-hosted model can remove per-channel or per-concurrent-session fees, the vendor-cloud premium, and feature-tier tolls, since capabilities like device groups, a shared address book, and LDAP/SSO come from the Basic plan and up. RustDesk licenses still renew annually and current rates can change.'
|
||||
- question: 'Can I prove the cost model before paying?'
|
||||
answer: 'Yes. You can self-host the free open-source community server today, or email sales@rustdesk.com for current Pro evaluation terms, and validate the cost model and operational fit on your own hardware before purchasing an annual license.'
|
||||
- question: 'What is the trade-off of self-hosting to save money?'
|
||||
answer: 'Someone on your side runs the server, but the effort is modest: mostly one-time setup (provision a small host, open ports, set up TLS), then light monitoring and patching. The upside is control of server-side services and unlimited concurrency on standard plans; size the user, device, and Customized V2 allowances from current terms.'
|
||||
|
||||
metadata:
|
||||
description: 'TeamViewer too expensive at renewal? Build a comparable three-year TCO across licensing, migration, hosting, operations, users, devices, and concurrency.'
|
||||
keywords: 'TeamViewer too expensive, TeamViewer renewal cost, TeamViewer three-year TCO, TeamViewer cost alternatives'
|
||||
@@ -20,9 +32,11 @@ metadata:
|
||||
|
||||
## "TeamViewer Too Expensive?" You're Not Alone
|
||||
|
||||
The short answer: your real options are to renew, negotiate, or move to a model you control — and if predictable cost is the goal, self-hosting RustDesk (licensed by users and devices, not seats) is the structural fix.
|
||||
|
||||
If the renewal invoice triggered your search, compare current written quotes using the same users, devices, concurrency, features, and support requirements.
|
||||
|
||||
The real problem is paying for functions you do not use. If **TeamViewer feels too expensive**, it usually isn't because you're using more. It's because the pricing model keeps climbing whether you grow or not. This guide explains _why_ that happens, and lays out the real options for teams shopping to leave, including where RustDesk fits and where it honestly doesn't.
|
||||
The real problem is paying for functions you do not use. If **TeamViewer feels too expensive**, it usually isn't because you're using more. It's because the pricing model keeps climbing whether you grow or not. This guide explains _why_ that happens, and lays out the real options for teams shopping to leave, including where RustDesk fits and what running it involves.
|
||||
|
||||
## Why the bill keeps going up
|
||||
|
||||
@@ -38,7 +52,7 @@ RustDesk changes the cost equation in two structural ways.
|
||||
|
||||
First, **it's self-hosted.** RustDesk Server Pro runs the ID/rendezvous server, relay, console, and stored deployment data on infrastructure you operate. Direct sessions still flow between endpoints; relayed sessions use your configured relay. Hosting moves into your cost model rather than being bundled into SaaS pricing.
|
||||
|
||||
Second, licensing is [per login-user plus per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay). Standard plans include unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit); Customized V2 limits and prices them separately.
|
||||
Second, licensing is [per login-user plus per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay). Standard plans include unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit); [Customized V2](https://rustdesk.com/pricing#custom2) limits and prices them separately.
|
||||
|
||||
You can also [upgrade any time](/blog/upgrade-rustdesk-license-mid-subscription), prorated — for exact numbers, [see rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
@@ -78,11 +92,11 @@ Sticker price is a poor way to compare these two models, because they put the mo
|
||||
**Self-hosted RustDesk (mixed):**
|
||||
|
||||
- A [RustDesk Server Pro license](/blog/rustdesk-pro-license-cost-how-to-pay), sized to login-users + managed-devices (current figures at [rustdesk.com/pricing](https://rustdesk.com/pricing))
|
||||
- A VPS or on-prem host to run the ID/rendezvous and relay servers — a modest, predictable line item you already understand
|
||||
- Ops hours: the honest cost of self-hosting — initial setup (host, ports, TLS) plus ongoing patching and monitoring
|
||||
- A VPS or on-prem host to run the ID/rendezvous and relay servers — hardware requirements are low, so this is a small, predictable line item
|
||||
- Ops time: mostly the one-time setup (host, ports, TLS); once configured, routine patching and monitoring take little ongoing effort — and if any question comes up along the way, [RustDesk support](mailto:support@rustdesk.com) can help you through it
|
||||
- Concurrency is not a cost lever on standard plans, so growth in simultaneous sessions doesn't re-price the deal
|
||||
|
||||
The point isn't that self-hosting is free — it plainly isn't, and the ops-hours line is the one teams underestimate. The point is _where_ the money goes: into infrastructure and time you control, rather than a recurring rate someone else resets each year.
|
||||
Self-hosting has a cost too, but a small one: an inexpensive host (hardware requirements are low) and mostly one-time setup, with little ongoing upkeep. The difference is _where_ the money goes: into infrastructure and time you control, rather than a recurring rate someone else resets each year.
|
||||
|
||||
## What you stop paying for
|
||||
|
||||
@@ -93,7 +107,7 @@ Moving to a self-hosted model removes several recurring line items outright:
|
||||
- **Feature-tier tolls** — capabilities often gated behind higher cloud tiers ([device groups and a shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book), [LDAP/SSO](/blog/rustdesk-active-directory-ldap-sso) from the Basic plan and up) come with the plan you host.
|
||||
- **Some usage-based add-ons** — standard RustDesk plans do not meter concurrency, while Customized V2 does. RustDesk licenses still renew annually and current rates can change, so budget from the current terms rather than assuming a permanent price.
|
||||
|
||||
What you take on instead is the server itself — covered honestly in the caveat below.
|
||||
What you take on instead is running the server yourself — more on that below.
|
||||
|
||||
## You can prove the savings before you pay
|
||||
|
||||
@@ -105,13 +119,11 @@ Use a trial or proof of concept to validate the cost model and operational fit o
|
||||
|
||||
Cost includes overlapping tools, migration, infrastructure, and operations. Consolidation may help, but validate access-control and SSO requirements against the current plan matrix.
|
||||
|
||||
For large deployments, validate current capacity guidance against your workload. Pro provides a web console, while custom client generation and identity features depend on plan. Self-hosting controls server-side components but does not by itself guarantee in-country traffic or GDPR compliance.
|
||||
For large deployments, validate current capacity guidance against your workload. Pro provides a web console, while custom client generation and identity features are available from the Basic plan and up. Self-hosting controls server-side components but does not by itself guarantee in-country traffic or GDPR compliance.
|
||||
|
||||
## The honest caveat
|
||||
## The cost lands where you control it
|
||||
|
||||
Self-hosting changes the cost structure—and adds operating work. **Someone on your side has to run the server:** provision a host, open ports, set up TLS, monitor it, and keep it patched. If what you want is a [managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run, RustDesk Server Pro is not that. The upside is control of server-side services and unlimited concurrency on standard plans; Customized V2 and all user/device allowances still have to be sized from current terms.
|
||||
|
||||
For a lot of teams fed up with the renewal climb, that's a trade worth making. For a few, it isn't. Both answers are fine; we'd rather you know which one you are before you switch.
|
||||
Self-hosting puts remote-access cost onto infrastructure and a license you control, instead of a renewal a vendor resets each year — predictable, and yours to plan. For a shop already running servers, that predictability is the win.
|
||||
|
||||
## Try it
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-03T18:26:00Z
|
||||
lang: en
|
||||
translationKey: teamviewer-vs-anydesk-for-msps
|
||||
draft: false
|
||||
@@ -48,7 +48,7 @@ AnyDesk plan packaging and renewal terms can change. Its [official pricing page]
|
||||
|
||||
## Where each one actually fits
|
||||
|
||||
TeamViewer tends to win for MSPs that have outgrown ad hoc support: policy controls, structured reporting, mass deployment, and — as of the Business plan and up — built-in AI-assisted support tooling. If your service desk already lives in ServiceNow, Jira, or Microsoft Intune, TeamViewer Tensor's native integrations are hard for a smaller competitor to match. That structure has a cost, and it shows up as complexity and add-on pricing rather than a single clean number.
|
||||
TeamViewer tends to win for MSPs that have outgrown ad hoc support: policy controls, structured reporting, mass deployment, and additional support-desk tooling on its higher plans. If your service desk already lives in ServiceNow, Jira, or Microsoft Intune, TeamViewer Tensor's native integrations are hard for a smaller competitor to match. That structure has a cost, and it shows up as complexity and add-on pricing rather than a single clean number.
|
||||
|
||||
AnyDesk is often shortlisted by smaller shops that prioritize connection performance, a compact client, and branding. Whether its current packaging is economical depends on the quote and workload; model technician and concurrency growth rather than assuming it remains the cheapest option.
|
||||
|
||||
@@ -58,7 +58,7 @@ Neither vendor is going to solve the thing a lot of MSPs actually want, though:
|
||||
|
||||
This is the part where RustDesk makes its case, so read it as vendor-authored commentary.
|
||||
|
||||
**A different unit of pricing.** RustDesk licenses by **login-user plus managed-device**. Standard plans include unlimited concurrent connections; Customized V2 limits and prices them separately.
|
||||
**A different unit of pricing.** RustDesk licenses by **login-user plus managed-device**. Standard plans include unlimited concurrent connections; [Customized V2](https://rustdesk.com/pricing#custom2) limits and prices them separately.
|
||||
|
||||
**Self-hosted server-side services.** RustDesk Server Pro runs the ID/rendezvous, relay, console, and stored deployment data on infrastructure you control. Direct sessions still flow between endpoints. For regulated clients, this supplies architectural control, but it does not by itself satisfy data-residency or compliance requirements.
|
||||
|
||||
@@ -66,9 +66,9 @@ This is the part where RustDesk makes its case, so read it as vendor-authored co
|
||||
|
||||
**Built for the MSP workflow.** A self-hosted web console, a custom-branded client generator, device groups, and a shared address book cover the "one console, many technicians, many client devices" requirement. Feature availability varies by RustDesk plan, and Customized V2 has a concurrency allowance, so verify the current matrix. See [RustDesk for MSPs](/blog/rustdesk-for-msps) for the full picture, and our deeper head-to-heads: [RustDesk vs TeamViewer](/blog/rustdesk-vs-teamviewer) and [RustDesk vs AnyDesk](/blog/rustdesk-vs-anydesk). If TeamViewer is the incumbent you're actually trying to replace, [the self-hosted TeamViewer alternative](/blog/self-hosted-teamviewer-alternative) covers that migration specifically.
|
||||
|
||||
## The honest caveat
|
||||
## The third option neither vendor sells
|
||||
|
||||
Self-hosting isn't free of cost, it's free of a specific kind of cost. Running RustDesk Server Pro means **you** provision the server, patch it, and keep it secured — there's no vendor NOC doing that for you the way there is with TeamViewer's or AnyDesk's managed cloud. For an MSP that already runs infrastructure for clients, that's routine. For one with no appetite to run a server at all, a managed product may genuinely be the better fit, and that's a legitimate call to make.
|
||||
Both of these live in someone else's cloud. Self-hosting RustDesk is the other model — an MSP runs the coordination and keeps client data on its own infrastructure, priced by users and devices rather than per technician. That is why it earns a place on the shortlist.
|
||||
|
||||
## Try it
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-02T12:27:00Z
|
||||
lang: en
|
||||
translationKey: teamviewer-vs-splashtop
|
||||
draft: false
|
||||
@@ -93,7 +93,7 @@ The decision changes when infrastructure control, source visibility, or a differ
|
||||
|
||||
This is where we make RustDesk's case plainly, so read it as that.
|
||||
|
||||
**A published licensing model.** RustDesk Server Pro standard plans license **login users plus managed devices** and include unlimited concurrent connections. Customized V2 has a defined concurrency allowance, so confirm the current [pricing matrix](https://rustdesk.com/pricing) for the plan you are evaluating.
|
||||
**A published licensing model.** RustDesk Server Pro standard plans license **login users plus managed devices** and include unlimited concurrent connections. [Customized V2](https://rustdesk.com/pricing#custom2) has a defined concurrency allowance, so confirm the current [pricing matrix](https://rustdesk.com/pricing) for the plan you are evaluating.
|
||||
|
||||
**Self-hosted server-side services.** RustDesk Server Pro runs the ID/rendezvous, relay, console, and stored deployment data on infrastructure you control. When customer-operated infrastructure is mandatory, compare it with Splashtop On-Prem rather than with Splashtop's SaaS plans.
|
||||
|
||||
@@ -101,9 +101,9 @@ This is where we make RustDesk's case plainly, so read it as that.
|
||||
|
||||
**A third option for the MSP workflow.** A self-hosted web console, custom client generator, device groups, and a shared address book cover the "one console, many technicians" requirement. RustDesk still licenses login users and managed devices, and Customized V2 has a concurrency allowance. See [RustDesk for MSPs](/blog/rustdesk-for-msps), [RustDesk vs TeamViewer](/blog/rustdesk-vs-teamviewer), and [Self-Hosted Splashtop Alternative: What IT Teams Should Evaluate Before Switching](/blog/rustdesk-vs-splashtop).
|
||||
|
||||
## The honest caveat
|
||||
## Or skip the cloud altogether
|
||||
|
||||
Self-hosting does not remove operational cost. Running RustDesk Server Pro or Splashtop On-Prem means **your team** operates server infrastructure. TeamViewer and Splashtop SaaS shift more of that work to the vendor. If your team does not want to own TLS, monitoring, backup, upgrades, and availability, a managed product may be the better fit.
|
||||
Between two SaaS products sits the option neither sells: run the coordination yourself and keep data and cost on infrastructure you control. For teams weighing more than monthly price, that question is worth putting on the table.
|
||||
|
||||
## Try it
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-03T09:40:00Z
|
||||
lang: en
|
||||
translationKey: upgrade-rustdesk-license-mid-subscription
|
||||
draft: false
|
||||
title: 'Upgrade RustDesk License Mid-Subscription: How It Works'
|
||||
excerpt: 'Yes—you can upgrade your RustDesk license anytime to add users or devices as you grow. Learn how proration works and why you must refresh the license after.'
|
||||
excerpt: 'Yes—you can upgrade your RustDesk license anytime to add users or devices. Learn how proration works and how new limits apply: refresh in the web console for instant effect, or wait for the automatic 24-hour check.'
|
||||
image: ~/assets/images/blog/upgrade-rustdesk-license-mid-subscription-og.png
|
||||
category: Pricing
|
||||
tags:
|
||||
@@ -14,18 +14,20 @@ tags:
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'Can I upgrade my RustDesk license mid-subscription?'
|
||||
answer: 'Yes. You can upgrade your RustDesk license at any time during your subscription to add more managed devices or users. Upgrades are prorated, and after purchasing you must manually refresh the license in the web console for the new limits to take effect.'
|
||||
answer: 'Yes. You can upgrade your RustDesk license at any time during your subscription to add more managed devices or users. Upgrades are prorated. To apply the new limits immediately, refresh the license in the web console; otherwise they take effect automatically within about 24 hours, when the periodic license check runs.'
|
||||
- question: 'How is a RustDesk license upgrade prorated?'
|
||||
answer: 'The upgrade is prorated against the time left on your current term: the system charges the difference for the added users or devices based on the remaining days, rather than a full new price. See rustdesk.com/pricing for tier details.'
|
||||
- question: "Why don't my new devices appear after I upgrade my license?"
|
||||
answer: 'The new limits are not always applied instantly. After completing the upgrade you must manually refresh the license in the web console to pull the updated entitlement, after which the added devices or users become usable.'
|
||||
answer: 'The new limits are not always applied instantly. Refresh the license in the web console to pull the updated entitlement right away; if you do not, it refreshes automatically within about 24 hours, when the periodic license check runs.'
|
||||
- question: 'How do I refresh my license in the web console?'
|
||||
answer: 'Open the web console after purchasing the upgrade and use the license refresh action to pull your updated entitlement. This activates the higher user and device limits for your deployment.'
|
||||
- question: 'Where do I buy the upgrade or renew my license?'
|
||||
answer: 'Use the self-service license portal at rustdesk.com/self-host/account/. Log in with the email address you used on the payment page when you bought the license; if you no longer know which email that was, contact support@rustdesk.com. The portal also holds your invoices and renewals; after upgrading, refresh the license in your web console for immediate effect, or let the automatic 24-hour check apply it.'
|
||||
- question: 'Can I downgrade or reduce seats mid-subscription?'
|
||||
answer: 'This article covers upgrades, which you can make at any time. For reducing seats or downgrading mid-term, confirm the current handling with the RustDesk team at sales@rustdesk.com.'
|
||||
|
||||
metadata:
|
||||
description: 'Yes—you can upgrade your RustDesk license anytime to add users or devices as you grow. Learn how proration works and why you must refresh the license after.'
|
||||
description: 'Upgrade your RustDesk license anytime to add users or devices, prorated against your term. Refresh in the web console for immediate effect, or it applies automatically within about 24 hours.'
|
||||
keywords: 'upgrade RustDesk license mid-subscription, add more devices RustDesk license, RustDesk license proration, increase managed devices RustDesk, refresh license web console RustDesk, RustDesk per-user per-device licensing'
|
||||
---
|
||||
|
||||
@@ -33,7 +35,7 @@ Yes—you can upgrade your RustDesk license mid-subscription to add more [manage
|
||||
|
||||
## The short answer
|
||||
|
||||
You do not have to wait for renewal to scale up. RustDesk lets you upgrade your existing license at any point during the subscription year. The cost is prorated against the time left on your current term, and once the upgrade is complete you refresh the license in your [web console](/blog/rustdesk-web-console-custom-client-generator-port-21114) to activate the higher limits.
|
||||
You do not have to wait for renewal to scale up. RustDesk lets you upgrade your existing license at any point during the subscription year. The cost is prorated against the time left on your current term. Once the upgrade is complete, refresh the license in your [web console](/blog/rustdesk-web-console-custom-client-generator-port-21114) to activate the higher limits immediately — or leave it, and the change applies automatically within about 24 hours.
|
||||
|
||||
## In detail
|
||||
|
||||
@@ -41,7 +43,9 @@ RustDesk licensing is structured around per-user and per-device seats, and a gro
|
||||
|
||||
Because you have already paid for part of the year, the upgrade is prorated. In practice that means the system calculates the additional cost based on the time remaining on your subscription, so you are charged the difference for the new capacity rather than a full new price. If the amount ever looks higher than you expect, you can check the math against your remaining term and confirm you have not been overcharged.
|
||||
|
||||
One operational detail is easy to miss: the new limits are not always applied instantly. After you complete the upgrade, you need to manually refresh the license inside the web console. This pulls the updated entitlement so your added devices or users become usable. If you upgrade and the new seats do not appear right away, this refresh step is almost always the reason.
|
||||
You make the upgrade itself in the [self-service license portal](https://rustdesk.com/self-host/account/) — log in with the email you used on the payment page when you first bought the license. If you no longer know which email that was, email [support@rustdesk.com](mailto:support@rustdesk.com). The same portal is where you renew and download invoices.
|
||||
|
||||
One operational detail is easy to miss: the new limits are not always applied instantly. RustDesk re-checks the license about once every 24 hours, so an upgrade can take up to a day to appear on its own. To apply it right away, refresh the license inside the web console — that pulls the updated entitlement immediately. If you upgrade and the new seats do not appear at once, that is why, and a manual refresh fixes it.
|
||||
|
||||
For teams migrating from TeamViewer or AnyDesk, this flexibility is a meaningful difference: you can start with the capacity you need today and expand incrementally, paying only for what you add, without renegotiating a contract mid-term. Exact pricing tiers and seat definitions are on the official pricing page [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ tags:
|
||||
- release
|
||||
---
|
||||
|
||||
Rustdesk web client V1 hasn't been updated for over two years and lacks many features, our team has spent three months developing V2. Today, we are proud to introduce the V2 Preview, which offers numerous enhancements over V1. These improvements include stronger decoding capabilities, better international keyboard support, clipboard support (not just text but also image clipboards), and file transfer functionality etc. We have strived to ensure that the web version offers a synchronized feature set and user experience with the desktop version, despite the limitations imposed by browser capabilities.
|
||||
We are proud to introduce the RustDesk web client V2 Preview. It brings stronger decoding, better international keyboard support, clipboard support (not just text but also images), and file transfer. We have worked to keep the web version's feature set and user experience in sync with the desktop client, within the limits that browsers impose.
|
||||
|
||||
You can access the RustDesk web client V2 Preview by visiting https://rustdesk.com/web. If you wish to access your own server through V2, please configure WebSocket Secure (WSS) support according to the [documentation](https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/faq/#8-add-websocket-secure-wss-support-for-the-id-server-and-relay-server-to-enable-secure-communication-for-the-web-client), setting it up on ports 21118/21119.
|
||||
```
|
||||
@@ -38,6 +38,20 @@ You can access the RustDesk web client V2 Preview by visiting https://rustdesk.c
|
||||
proxy_set_header X-Forwarded-Proto $scheme;
|
||||
}
|
||||
```
|
||||
Once the V2 version is stable, we will also integrate the web client into the Pro version, allowing you to access it via `https://rustdesk.yourcompany.com/web`.
|
||||
The web client is also **integrated into RustDesk Server Pro**, so you can serve it from your own server at `https://rustdesk.yourcompany.com/web` instead of relying on the public one.
|
||||
|
||||
## Two ways to use the web client with your own server
|
||||
|
||||
- **Public web client (`rustdesk.com/web`), pointed at your server.** You can use RustDesk's hosted web client and connect it to your own ID/relay server, but you configure it yourself: the browser needs WebSocket Secure (WSS) and the right CORS headers to reach your server. See [WSS and CORS setup for the web client](https://github.com/rustdesk/rustdesk/wiki/FAQ#wss-and-cors-setup-for-web-client).
|
||||
- **Self-hosted web client (served by Server Pro at `https://your-server/web`).** The web client is [integrated into RustDesk Server Pro](https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro), so it runs from your own server rather than the public one. Self-hosting the web client is **not included in the entry-level plans** — it requires a plan large enough to satisfy **(number of users × 10) + number of devices ≥ 400** (for example 10 users / 300 devices, 30 users / 100 devices, or 20 users / 200 devices). A self-hosted web client can also be [customized](https://github.com/rustdesk/rustdesk/wiki/FAQ#how-to-customize-self-hosted-web-client).
|
||||
|
||||
Whichever route you take, the web client is a **controller**: you drive other devices from a browser tab, but a browser tab cannot act as an unattended host.
|
||||
|
||||
We are excited to bring these enhancements to our users and look forward to your feedback as we continue to refine and improve the RustDesk Web Client V2.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [RustDesk Web Console: Port 21114 and the Custom Client Generator](/blog/rustdesk-web-console-custom-client-generator-port-21114)
|
||||
- [RustDesk LDAP, Active Directory & SSO](/blog/rustdesk-active-directory-ldap-sso)
|
||||
- [RustDesk Pro Pricing: Cost & Buying Guide](/blog/rustdesk-pro-license-cost-how-to-pay)
|
||||
- [Self-Hosted vs Cloud Remote Desktop](/blog/rustdesk-self-hosted-vs-cloud-saas-option)
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-02T14:43:00Z
|
||||
lang: en
|
||||
translationKey: what-counts-as-a-managed-device
|
||||
draft: false
|
||||
title: 'What Counts as a Managed Device in RustDesk?'
|
||||
excerpt: 'Every device you reach counts once toward your RustDesk license, regardless of attended/unattended or connection frequency. Ad-hoc support has its own model.'
|
||||
excerpt: 'On standard RustDesk plans every device you set up to reach counts once. Customized V2 counts only devices assigned to a group or user; ad-hoc devices are not counted.'
|
||||
image: ~/assets/images/blog/what-counts-as-a-managed-device-og.png
|
||||
category: Pricing
|
||||
tags:
|
||||
@@ -14,40 +14,40 @@ tags:
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'How does RustDesk count managed devices?'
|
||||
answer: "Every device you want to be able to access counts as one managed device, counted a single time. It makes no difference whether a machine is attended or unattended, or whether you connect to it once or a thousand times. For pure ad-hoc, one-off support where you don't retain a permanent connection, RustDesk offers a separate quick-support license model."
|
||||
- question: 'What is the quick-support (ad-hoc) license model, and when should I use it?'
|
||||
answer: "Quick support is a separate model for spontaneous, one-off sessions where you don't keep a permanent connection to the machine. If your work is purely ad-hoc — you help someone once and move on — it fits better than counting every endpoint as a managed device."
|
||||
answer: "On standard plans, every device you set up to access counts as one managed device, a single time — attended or unattended, whether you connect once or a thousand times. Customized V2 counts differently: only devices assigned to a device group or a user count toward your licensed device number, so machines touched only for ad-hoc, one-off support are not counted and are not disabled."
|
||||
- question: 'How are ad-hoc, one-off support devices counted?'
|
||||
answer: "On the Customized V2 plan, only devices assigned to a device group or a user count as managed devices. A machine you connect to once for spontaneous support — and never assign — is not counted toward your licensed device number and is not disabled. For work that is mostly ad-hoc, that makes Customized V2 a better fit than counting every endpoint."
|
||||
- question: 'Do concurrent connections to the same device count more than once?'
|
||||
answer: 'No. A device is counted a single time no matter how many times, or how simultaneously, you connect to it. You pay for the device being reachable, not per connection to it.'
|
||||
- question: 'Does an attended device count differently from an unattended one?'
|
||||
answer: 'No. An unattended server and an attended employee laptop each count as one managed device. The attended/unattended split does not create two pricing buckets — what changes the model is whether support is permanent or ad-hoc.'
|
||||
answer: 'No. An unattended server and an attended employee laptop each count as one managed device. The attended/unattended split does not create two pricing buckets — what changes the count is the plan: Customized V2 counts only devices assigned to a group or user.'
|
||||
|
||||
metadata:
|
||||
description: 'Every device you reach counts once toward your RustDesk license, regardless of attended/unattended or connection frequency. Ad-hoc support has its own model.'
|
||||
description: 'How RustDesk counts managed devices: on standard plans every reachable device counts once; on Customized V2 only devices assigned to a group or user count toward your license.'
|
||||
keywords: 'what counts as a managed device, rustdesk device counting, rustdesk vs teamviewer licensing, unattended vs attended device license, rustdesk quick support license, msp remote support licensing'
|
||||
---
|
||||
|
||||
If you're coming from TeamViewer's per-seat model, the counting rule in RustDesk is refreshingly simple: **every device you want to access counts as one managed device, counted once.** Attended or unattended, connected once or constantly, it's the same single count. Pure ad-hoc support is handled by a separate quick-support model.
|
||||
If you're coming from TeamViewer's per-seat model, the counting rule on RustDesk's standard plans is refreshingly simple: **every device you want to access counts as one managed device, counted once.** Attended or unattended, connected once or constantly, it's the same single count. The **[Customized V2](https://rustdesk.com/pricing#custom2)** plan counts differently — only devices you assign to a group or user count — which is what makes it the fit for heavy ad-hoc support.
|
||||
|
||||
## The short answer
|
||||
|
||||
A "managed device" is any machine you want to be able to reach. The server counts each one a single time. It doesn't matter:
|
||||
On standard plans, a "managed device" is any machine you want to be able to reach, and the server counts each one a single time. It doesn't matter:
|
||||
|
||||
- whether the device is **attended** (someone is sitting at it) or **unattended** (a headless server, kiosk, or always-on workstation),
|
||||
- whether you'll connect **once** or **many times**,
|
||||
- how frequently you access it.
|
||||
|
||||
The server has no way of knowing your intent, so it simply counts the devices you have set up to access. If your work is purely spontaneous, one-off support, look at the **quick-support license model** instead — that's the path built for ad-hoc sessions.
|
||||
On standard plans the server has no way of knowing your intent, so it simply counts the devices you have set up to access. If your work is largely spontaneous, one-off support, look at **[Customized V2](https://rustdesk.com/pricing#custom2)** instead: it counts only the devices you assign to a group or user, so ad-hoc machines you never assign do not add to your device count.
|
||||
|
||||
## In detail
|
||||
|
||||
The reasoning follows directly from how the counting works. The server tracks the devices registered to be accessed; it cannot see the future, so it can't distinguish a machine you'll touch once from one you'll touch daily, nor an attended desk from an unattended server. Every reachable device therefore counts the same way: **once.**
|
||||
On standard plans, the reasoning follows directly from how the counting works. The server tracks the devices registered to be accessed; it cannot see the future, so it can't distinguish a machine you'll touch once from one you'll touch daily, nor an attended desk from an unattended server. Every reachable device therefore counts the same way: **once.**
|
||||
|
||||
That's a meaningful difference from per-seat or per-technician licensing. You aren't paying per concurrent session or per simultaneous connection to the same box — a device is a device. This makes capacity planning predictable: count the machines you intend to keep reachable, and that's your number.
|
||||
|
||||
The important nuance is the **attended/unattended split you may be used to elsewhere doesn't create two pricing buckets here.** An unattended server and an attended employee laptop each count as one device. What _does_ change the model is whether the support is permanent or ad-hoc. If you don't need a standing, always-available connection — you just help someone once and move on — the quick-support model is the right tool, and it's licensed differently from your fleet of managed devices — see [rustdesk.com/pricing](https://rustdesk.com/pricing) for current terms.
|
||||
The important nuance is the **attended/unattended split you may be used to elsewhere doesn't create two pricing buckets here.** An unattended server and an attended employee laptop each count as one device. What _does_ change things is the plan. On the **[Customized V2](https://rustdesk.com/pricing#custom2)** plan the definition of a managed device is narrower: only the devices you **assign to a device group or a user** count toward your licensed device number. Machines you reach only for ad-hoc, one-off support — and never assign — are not counted, and they are not disabled. If you would rather these unassigned devices not appear in the console at all, the [`register-device` client setting](https://rustdesk.com/docs/en/self-host/client-configuration/advanced-settings/#register-device) controls that, and it takes effect once the licensed concurrent-connection count is 2 or more. In practice such a quick-support session shows only an ID and a one-time password for a single attended connection, so a genuine one-off interaction never needs a permanent slot in your fleet. If a lot of your work looks like that, Customized V2 is usually the better fit — email [sales@rustdesk.com](mailto:sales@rustdesk.com) with your scenario for current terms, or check [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
For example, imagine an [MSP](/blog/rustdesk-for-msps) with 20 technicians supporting roughly 1,000 customer machines: it would need to satisfy **both** licensing dimensions — enough login users for all 20 technicians and enough managed devices for the machines kept reachable. If many endpoints are truly one-time support calls, ask RustDesk whether the current quick-support terms fit that workload better; you can check current allowances at [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
For example, imagine an [MSP](/blog/rustdesk-for-msps) with 20 technicians supporting roughly 1,000 customer machines: it would need to satisfy **both** licensing dimensions — enough login users for all 20 technicians and enough managed devices for the machines kept reachable. If many endpoints are truly one-time support calls that you never assign to a group or user, Customized V2 may fit that workload better; you can check current allowances at [rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
## Who asks this
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-06T00:00:00Z
|
||||
publishDate: 2026-07-07T18:21:00Z
|
||||
lang: en
|
||||
translationKey: why-self-host-remote-desktop-software
|
||||
draft: false
|
||||
@@ -11,6 +11,18 @@ tags:
|
||||
- RustDesk
|
||||
- self-hosting
|
||||
author: RustDesk Team
|
||||
faq:
|
||||
- question: 'What does it mean to self-host remote desktop software?'
|
||||
answer: "It means running the server that coordinates connections and relays traffic when direct connectivity fails on infrastructure you control, instead of routing sessions through a vendor's cloud. With RustDesk Server Pro, the ID/rendezvous server, relay, console, and stored deployment data run on your own infrastructure."
|
||||
- question: 'Why self-host instead of using a cloud remote-desktop tool?'
|
||||
answer: "Self-hosting gives you control over where the server-side data and relay run, more predictable cost, and no dependence on a vendor's cloud uptime or roadmap. RustDesk licensing is per login-user plus per managed-device, with unlimited concurrent connections on standard plans."
|
||||
- question: 'What does running a self-hosted RustDesk server actually involve?'
|
||||
answer: 'The hardware requirements are low and most of the work is one-time: you provision a small Linux host, open only the ports you use (native clients require TCP 21115-21117 and UDP 21116), set up TLS at a reverse proxy, and schedule backups; after that it is routine patching and monitoring, with RustDesk support available if you hit a snag.'
|
||||
- question: 'Does self-hosting help with data residency and GDPR compliance?'
|
||||
answer: 'Yes — it gives you real control here: you choose where the rendezvous, relay, console, and device data run. It is a foundation rather than an absolute guarantee, though, because direct connections still travel between endpoints — so keeping traffic in-country and meeting GDPR obligations also depends on how you route and operate the deployment.'
|
||||
- question: 'Is self-hosting right for every team?'
|
||||
answer: "Self-hosting suits teams that want control of their data and infrastructure. It does involve running a server — modest, and mostly one-time to set up — so if you would rather not run any server at all, a managed SaaS is the alternative model. But RustDesk Server Pro is self-hosted by design precisely so your data stays on your own infrastructure with no vendor cloud in the middle — and for teams that already run infrastructure, that ownership is the whole point."
|
||||
|
||||
metadata:
|
||||
description: 'The case for self-hosting remote desktop software: data control, predictable cost, no vendor lock-in, no cloud outage. RustDesk as the concrete example.'
|
||||
keywords: 'why self-host remote desktop, self-hosted remote desktop benefits, on-premise remote access, remote desktop without vendor cloud'
|
||||
@@ -36,7 +48,7 @@ Self-hosting lets you choose where rendezvous, relay, console, and device data r
|
||||
|
||||
A common pattern is that one renewal hike pushes a team off a cloud tool, and the next vendor increase makes them re-evaluate the model itself rather than just the brand.
|
||||
|
||||
RustDesk licensing is **per login-user plus per managed-device**. Standard plans include unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit); Customized V2 limits and prices them separately. For current numbers, [see rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
RustDesk licensing is **per login-user plus per managed-device**. Standard plans include unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit); [Customized V2](https://rustdesk.com/pricing#custom2) limits and prices them separately. For current numbers, [see rustdesk.com/pricing](https://rustdesk.com/pricing).
|
||||
|
||||
### 3. No vendor lock-in, no cloud outage dependency
|
||||
|
||||
@@ -44,7 +56,7 @@ Self-hosting moves the coordinating-service failure domain into your own operati
|
||||
|
||||
### 4. It scales, and it's built for IT teams
|
||||
|
||||
Self-hosting doesn't mean settling for a toy. RustDesk publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices) for teams that need to support bigger estates. For [MSPs](/blog/rustdesk-for-msps) and internal IT, there's a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114), a custom-branded client generator, and [device groups plus a shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book) for per-user access control. [LDAP/SSO](/blog/rustdesk-active-directory-ldap-sso) (OIDC) is available from the Basic plan and up.
|
||||
Self-hosting doesn't mean giving up scale or capability. RustDesk publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices) for teams that need to support bigger estates. For [MSPs](/blog/rustdesk-for-msps) and internal IT, there's a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114), a custom-branded client generator, and [device groups plus a shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book) for per-user access control. [LDAP/SSO](/blog/rustdesk-active-directory-ldap-sso) (OIDC) is available from the Basic plan and up.
|
||||
|
||||
## Cloud-only vs. self-hosted, at a glance
|
||||
|
||||
@@ -58,22 +70,22 @@ Self-hosting doesn't mean settling for a toy. RustDesk publishes [large-fleet pl
|
||||
| Outage dependency | Vendor uptime | Your own ops |
|
||||
| Who runs the server | Vendor | You |
|
||||
|
||||
## The honest caveat
|
||||
## Own the server, own the outcome
|
||||
|
||||
Self-hosting is a trade, not a free lunch. Someone on your side has to **run the server**: provision a host, open the right ports, set up TLS, and keep it patched. That's real, ongoing work. If what you actually want is a [zero-maintenance managed SaaS](/blog/rustdesk-self-hosted-vs-cloud-saas-option) with no server to run, be clear-eyed — RustDesk Server Pro is self-hosted by design, and it is not that. The upside of doing the ops is exactly the control described above; if your team can't own a server, this model isn't for you, and that's fine.
|
||||
|
||||
The good news is the bar to find out is low. You don't need a sales call to evaluate.
|
||||
That is the thesis in a line: run the server and the data, the cost, and the failure domain become yours to control rather than yours to rent. For an IT team already running infrastructure, it is a next step, not a leap.
|
||||
|
||||
## What running the server actually involves
|
||||
|
||||
The control described above is inseparable from the operational work that buys it. Before you commit, here's the concrete reality — not a feature list:
|
||||
The control comes with some operational work — less than most teams expect, and most of it one-time. Here's the concrete reality:
|
||||
|
||||
- **Provision a host.** A modest Linux VM — on-prem or a VPS you rent — runs the ID/rendezvous and relay services. Size it for your device count and how much traffic ends up relayed rather than peer-to-peer.
|
||||
- **Provision a host.** RustDesk's hardware requirements are low, so a modest Linux VM — on-prem or an inexpensive VPS — runs the ID/rendezvous and relay services. Size it for your device count and how much traffic ends up relayed rather than peer-to-peer.
|
||||
- **Open only the ports you use.** Native RustDesk clients require **TCP 21115-21117 and UDP 21116** for NAT testing, connection services, registration, heartbeat, and relay. Do not expose the whole 21114-21119 range. TCP 21118-21119 are WebSocket backends, and TCP 21114 is the Pro HTTP API/console backend. When an HTTPS/WSS reverse proxy fronts the Pro API and WebSocket services, expose only TCP 443 publicly for that traffic and keep 21114 and 21118-21119 internal. Public 443 does not replace the native-client core ports when native clients also connect. See the [official port reference](https://rustdesk.com/docs/en/self-host/).
|
||||
- **Set up TLS.** Terminate HTTPS and WSS at the reverse proxy so credentials, API calls, and browser-client traffic use public TCP 443 rather than exposing the plain-HTTP console/API or raw WebSocket backends.
|
||||
- **Back up.** The server holds your device inventory, user accounts, address book, and access rules. Schedule backups — and actually test that you can restore from them.
|
||||
- **Keep a patch cadence.** New server builds ship over time, and you own the OS underneath. Decide who applies updates and how often.
|
||||
- **Monitor it.** The coordinating service is now yours, so you watch uptime, disk, and relay throughput. When it goes down, nobody else is paged.
|
||||
- **Monitor it.** The coordinating service is now yours, so you watch uptime, disk, and relay throughput, and you own the alerting and recovery.
|
||||
|
||||
None of this is exotic, and most of it is one-time setup. If a question comes up at any point, [RustDesk support](mailto:support@rustdesk.com) can help you through it.
|
||||
|
||||
## How to evaluate self-hosting
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
publishDate: 2026-07-07T00:00:00Z
|
||||
publishDate: 2026-06-30T10:01:00Z
|
||||
lang: en
|
||||
translationKey: zoho-assist-alternative-self-hosted
|
||||
draft: false
|
||||
@@ -29,7 +29,7 @@ metadata:
|
||||
|
||||
[Zoho Assist](https://www.zoho.com/assist/) is a capable, cloud-based remote support and remote access product, and part of the broader Zoho suite. If you have landed here, you are probably not unhappy with what it does — you are asking a different question: **can I run something like this on my own infrastructure, and stop routing every session through a vendor's cloud?**
|
||||
|
||||
This page is an honest comparison. RustDesk is a genuinely different model, with real advantages and one real trade-off. Here is where it fits as a self-hosted Zoho Assist alternative, and where it doesn't.
|
||||
RustDesk is a genuinely different model from Zoho Assist's cloud: you run the server, so brokering and data stay yours. Here is where it fits as a self-hosted alternative.
|
||||
|
||||
## What Zoho Assist does well
|
||||
|
||||
@@ -53,7 +53,7 @@ And **RustDesk's core client is [open source under the AGPL](/blog/case-for-open
|
||||
| Source code | Proprietary | Open source (AGPL) core |
|
||||
| Where sessions are brokered | Zoho's infrastructure | Infrastructure you control |
|
||||
| Licensing model | Per-technician / per-computer cloud subscription | [Per login-user + per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Plan-dependent | Unlimited on standard plans; limited on Customized V2 |
|
||||
| [Concurrent connections](/blog/rustdesk-concurrent-connections-limit) | Plan-dependent | Unlimited on standard plans; limited on [Customized V2](https://rustdesk.com/pricing#custom2) |
|
||||
| Custom branding | Yes, on cloud plans | Yes, [self-hosted client generator](/blog/rustdesk-web-console-custom-client-generator-port-21114) |
|
||||
| Server maintenance | None (Zoho runs it) | Yours to run |
|
||||
|
||||
@@ -69,11 +69,9 @@ RustDesk licenses **login users plus managed devices** and runs on a server you
|
||||
|
||||
Self-hosting does not mean going without the tooling a support desk expects. RustDesk Pro includes a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114), a **custom-branded client generator**, and **device groups with a [shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book)** for per-user access control. [LDAP/AD and OIDC single sign-on](/blog/rustdesk-active-directory-ldap-sso) are available from the Basic plan and up. For teams supporting many clients, that rebuilds the "one console, many technicians, many managed devices" workflow Zoho Assist users expect — on infrastructure you own. If you run a managed-services practice, our [guide for MSPs](/blog/rustdesk-for-msps) goes deeper.
|
||||
|
||||
## The honest caveat: someone has to run the server
|
||||
## Off Zoho's cloud, onto your server
|
||||
|
||||
Here is the trade-off, stated plainly. Self-hosting means **someone on your side runs the server** — you provision a host, open ports, set up TLS, and keep it patched over time. For most IT teams and MSPs that is a modest lift, but it is real work.
|
||||
|
||||
Zoho Assist, by contrast, is a mature managed SaaS with a large ecosystem, mobile apps, deep Zoho integrations, and **nothing for you to maintain**. If what you actually want is a zero-maintenance cloud product and you are comfortable with sessions brokered through a vendor, Zoho Assist may be the better fit — and we would rather say so than oversell. RustDesk Server Pro is [self-hosted by design](/blog/rustdesk-self-hosted-vs-cloud-saas-option) and is not a managed cloud service. The upside of owning your infrastructure is inseparable from the responsibility of operating it.
|
||||
Rather than logging into Zoho's infrastructure, you run the ID and relay yourself — so brokering and your device list stay on hardware you control, behind an open-source client you can inspect. That is the trade a SaaS cannot make.
|
||||
|
||||
## Evaluate it on your own infrastructure
|
||||
|
||||
@@ -83,4 +81,4 @@ You don't need a sales call to find out whether this fits:
|
||||
- **Want the Pro features?** Email [sales@rustdesk.com](mailto:sales@rustdesk.com) about current evaluation terms, or check [rustdesk.com/pricing](https://rustdesk.com/pricing) for standard plan rates.
|
||||
- **Prefer to see it first?** Watch a full [video demo](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk) — no booking required.
|
||||
|
||||
If control and open source are why you are looking past Zoho Assist, a self-hosted alternative is worth an afternoon of evaluation.
|
||||
If control and open source are why you are looking past Zoho Assist, a self-hosted alternative is worth a short pilot before you renew.
|
||||
|
||||
@@ -56,7 +56,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'هل تم دمج web client في RustDesk Server Pro؟',
|
||||
description:
|
||||
'نعم، هو مدمج، لكنه يتطلب خطة بقيمة $47.88/شهريًا أو أعلى. يُرجى مراجعة <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">إدخال الأسئلة الشائعة هذا</a> للتفاصيل. للتوضيح، يشير <b>web client</b> إلى استخدام RustDesk مباشرةً داخل تبويب المتصفح لبدء جلسات اتصال عن بُعد، بينما يشير <b>web console</b> إلى موقع إدارة RustDesk Server Pro لإدارة المستخدمين والأجهزة والأذونات والسياسات والتراخيص.',
|
||||
'نعم، هو مدمج، لكنه يتطلب خطة تحقق (عدد المستخدمين × 10) + عدد الأجهزة ≥ 400. يُرجى مراجعة <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">إدخال الأسئلة الشائعة هذا</a> للتفاصيل. للتوضيح، يشير <b>web client</b> إلى استخدام RustDesk مباشرةً داخل تبويب المتصفح لبدء جلسات اتصال عن بُعد، بينما يشير <b>web console</b> إلى موقع إدارة RustDesk Server Pro لإدارة المستخدمين والأجهزة والأذونات والسياسات والتراخيص.',
|
||||
},
|
||||
{
|
||||
title: 'ماذا عن حالات الدعم العرضية؟ لدينا بعض الأجهزة التي تحتاج إلى دعم من حين لآخر دون الوصول غير المراقب.',
|
||||
|
||||
@@ -57,7 +57,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'Ist der web client in RustDesk Server Pro integriert?',
|
||||
description:
|
||||
'Ja, er ist integriert, aber er erfordert den Plan für $47.88/Monat oder höher. Bitte lesen Sie diesen <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ-Eintrag</a> für Details. Zur Klarstellung bedeutet <b>web client</b>, RustDesk direkt in einem Browser-Tab zu verwenden, um Remote-Sitzungen zu starten, während <b>web console</b> die RustDesk Server Pro-Admin-Website zur Verwaltung von Benutzern, Geräten, Berechtigungen, Strategien und Lizenzen bedeutet.',
|
||||
'Ja, er ist integriert, aber er erfordert einen Plan, der (Benutzer × 10) + Geräte ≥ 400 erfüllt. Bitte lesen Sie diesen <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ-Eintrag</a> für Details. Zur Klarstellung bedeutet <b>web client</b>, RustDesk direkt in einem Browser-Tab zu verwenden, um Remote-Sitzungen zu starten, während <b>web console</b> die RustDesk Server Pro-Admin-Website zur Verwaltung von Benutzern, Geräten, Berechtigungen, Strategien und Lizenzen bedeutet.',
|
||||
},
|
||||
{
|
||||
title:
|
||||
|
||||
@@ -57,7 +57,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: '¿Está integrado el web client en RustDesk Server Pro?',
|
||||
description:
|
||||
'Sí, está integrado, pero requiere el plan de $47.88/mes o superior. Consulte esta <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">entrada de FAQ</a> para más detalles. Para mayor claridad, <b>web client</b> significa usar RustDesk directamente en una pestaña del navegador para iniciar sesiones remotas, mientras que <b>web console</b> significa el sitio de administración de RustDesk Server Pro para gestionar usuarios, dispositivos, permisos, estrategias y licencias.',
|
||||
'Sí, está integrado, pero requiere un plan que cumpla (usuarios × 10) + dispositivos ≥ 400. Consulte esta <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">entrada de FAQ</a> para más detalles. Para mayor claridad, <b>web client</b> significa usar RustDesk directamente en una pestaña del navegador para iniciar sesiones remotas, mientras que <b>web console</b> significa el sitio de administración de RustDesk Server Pro para gestionar usuarios, dispositivos, permisos, estrategias y licencias.',
|
||||
},
|
||||
{
|
||||
title:
|
||||
|
||||
@@ -57,7 +57,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'Le web client est-il intégré à RustDesk Server Pro ?',
|
||||
description:
|
||||
'Oui, il est intégré, mais il nécessite le plan à $47.88/mois ou supérieur. Veuillez consulter cette <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">entrée de FAQ</a> pour plus de détails. Pour clarifier, <b>web client</b> signifie utiliser RustDesk directement dans un onglet du navigateur pour démarrer des sessions à distance, tandis que <b>web console</b> signifie le site d\'administration de RustDesk Server Pro pour gérer les utilisateurs, les appareils, les autorisations, les stratégies et les licences.',
|
||||
'Oui, il est intégré, mais il nécessite un plan qui satisfait (utilisateurs × 10) + appareils ≥ 400. Veuillez consulter cette <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">entrée de FAQ</a> pour plus de détails. Pour clarifier, <b>web client</b> signifie utiliser RustDesk directement dans un onglet du navigateur pour démarrer des sessions à distance, tandis que <b>web console</b> signifie le site d\'administration de RustDesk Server Pro pour gérer les utilisateurs, les appareils, les autorisations, les stratégies et les licences.',
|
||||
},
|
||||
{
|
||||
title:
|
||||
|
||||
@@ -57,7 +57,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'Il web client è integrato in RustDesk Server Pro?',
|
||||
description:
|
||||
'Sì, è integrato, ma richiede il piano da $47.88/mese o superiore. Per i dettagli, consulta questa <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">voce delle FAQ</a>. Per chiarezza, <b>web client</b> significa usare RustDesk direttamente in una scheda del browser per avviare sessioni remote, mentre <b>web console</b> significa il sito di amministrazione di RustDesk Server Pro per gestire utenti, dispositivi, permessi, strategie e licenze.',
|
||||
'Sì, è integrato, ma richiede un piano che soddisfi (utenti × 10) + dispositivi ≥ 400. Per i dettagli, consulta questa <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">voce delle FAQ</a>. Per chiarezza, <b>web client</b> significa usare RustDesk direttamente in una scheda del browser per avviare sessioni remote, mentre <b>web console</b> significa il sito di amministrazione di RustDesk Server Pro per gestire utenti, dispositivi, permessi, strategie e licenze.',
|
||||
},
|
||||
{
|
||||
title:
|
||||
|
||||
@@ -57,7 +57,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'web client は RustDesk Server Pro に統合されていますか？',
|
||||
description:
|
||||
'はい、統合されていますが、$47.88/月以上のプランが必要です。詳細はこの<a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQエントリ</a>をご確認ください。わかりやすく言うと、<b>web client</b> はブラウザタブで RustDesk を直接使ってリモートセッションを開始する機能で、<b>web console</b> はユーザー、デバイス、権限、戦略、ライセンスを管理する RustDesk Server Pro の管理サイトです。',
|
||||
'はい、統合されていますが、(ユーザー数 × 10) + デバイス数 ≥ 400 を満たすプランが必要です。詳細はこの<a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQエントリ</a>をご確認ください。わかりやすく言うと、<b>web client</b> はブラウザタブで RustDesk を直接使ってリモートセッションを開始する機能で、<b>web console</b> はユーザー、デバイス、権限、戦略、ライセンスを管理する RustDesk Server Pro の管理サイトです。',
|
||||
},
|
||||
{
|
||||
title: '臨時のサポートケースについてはどうですか？無人アクセスなしで時々サポートが必要なデバイスがあります。',
|
||||
|
||||
@@ -55,7 +55,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'web client가 RustDesk Server Pro에 통합되어 있나요?',
|
||||
description:
|
||||
'예, 통합되어 있지만 $47.88/월 이상의 요금제가 필요합니다. 자세한 내용은 이 <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ 항목</a>을 확인해 주세요. 혼동을 줄이기 위해 설명하면, <b>web client</b>는 브라우저 탭에서 RustDesk를 직접 사용해 원격 세션을 시작하는 기능이고, <b>web console</b>은 사용자, 장치, 권한, 정책, 라이선스를 관리하는 RustDesk Server Pro 관리자 웹사이트입니다.',
|
||||
'예, 통합되어 있지만 (사용자 수 × 10) + 장치 수 ≥ 400을 충족하는 요금제가 필요합니다. 자세한 내용은 이 <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ 항목</a>을 확인해 주세요. 혼동을 줄이기 위해 설명하면, <b>web client</b>는 브라우저 탭에서 RustDesk를 직접 사용해 원격 세션을 시작하는 기능이고, <b>web console</b>은 사용자, 장치, 권한, 정책, 라이선스를 관리하는 RustDesk Server Pro 관리자 웹사이트입니다.',
|
||||
},
|
||||
{
|
||||
title: '가끔 지원이 필요한 장치가 있습니다. 무인 액세스 없이 지원이 가능한가요?',
|
||||
|
||||
@@ -57,7 +57,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'Is web client integrated into RustDesk Server Pro?',
|
||||
description:
|
||||
'Yes, it is integrated, but it requires the $47.88/month plan or higher. Please check this <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ entry</a> for details. For clarity, <b>web client</b> means using RustDesk directly in a browser tab to start remote sessions, while <b>web console</b> means the RustDesk Server Pro admin website for managing users, devices, permissions, strategies, and licenses.',
|
||||
'Yes, it is integrated, but it requires a plan that satisfies (users × 10) + devices ≥ 400. Please check this <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ entry</a> for details. For clarity, <b>web client</b> means using RustDesk directly in a browser tab to start remote sessions, while <b>web console</b> means the RustDesk Server Pro admin website for managing users, devices, permissions, strategies, and licenses.',
|
||||
},
|
||||
{
|
||||
title:
|
||||
|
||||
@@ -57,7 +57,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'O web client está integrado ao RustDesk Server Pro?',
|
||||
description:
|
||||
'Sim, ele é integrado, mas requer o plano de $47.88/mês ou superior. Consulte esta <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">entrada de FAQ</a> para mais detalhes. Para maior clareza, <b>web client</b> significa usar o RustDesk diretamente em uma aba do navegador para iniciar sessões remotas, enquanto <b>web console</b> significa o site administrativo do RustDesk Server Pro para gerenciar usuários, dispositivos, permissões, estratégias e licenças.',
|
||||
'Sim, ele é integrado, mas requer um plano que satisfaça (usuários × 10) + dispositivos ≥ 400. Consulte esta <a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">entrada de FAQ</a> para mais detalhes. Para maior clareza, <b>web client</b> significa usar o RustDesk diretamente em uma aba do navegador para iniciar sessões remotas, enquanto <b>web console</b> significa o site administrativo do RustDesk Server Pro para gerenciar usuários, dispositivos, permissões, estratégias e licenças.',
|
||||
},
|
||||
{
|
||||
title:
|
||||
|
||||
@@ -55,7 +55,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'web client 是否已集成到 RustDesk Server Pro？',
|
||||
description:
|
||||
'是的，已集成，但需要 $47.88/月 或更高的计划。详情请查看此<a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ 条目</a>。为避免混淆，<b>web client</b> 指在浏览器标签页中直接使用 RustDesk 发起远程会话，<b>web console</b> 指 RustDesk Server Pro 的管理后台网站，用于管理用户、设备、权限、策略和许可证。',
|
||||
'是的，已集成，但需要满足（用户数 × 10）+ 设备数 ≥ 400 的计划。详情请查看此<a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ 条目</a>。为避免混淆，<b>web client</b> 指在浏览器标签页中直接使用 RustDesk 发起远程会话，<b>web console</b> 指 RustDesk Server Pro 的管理后台网站，用于管理用户、设备、权限、策略和许可证。',
|
||||
},
|
||||
{
|
||||
title: '临时支持案例怎么办？我们有一些无需无人值守的设备需要偶尔支持',
|
||||
|
||||
@@ -53,7 +53,7 @@ const faqRawItems = [
|
||||
{
|
||||
title: 'web client 是否已整合到 RustDesk Server Pro？',
|
||||
description:
|
||||
'是的，已整合，但需要 $47.88/月 或更高方案。詳情請查看此<a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ 條目</a>。為避免混淆，<b>web client</b> 指在瀏覽器分頁中直接使用 RustDesk 發起遠端工作階段，<b>web console</b> 指 RustDesk Server Pro 的管理後台網站，用於管理使用者、裝置、權限、策略與授權。',
|
||||
'是的，已整合，但需要滿足（使用者數 × 10）+ 裝置數 ≥ 400 的方案。詳情請查看此<a class="underline" target="_blank" href="https://github.com/rustdesk/rustdesk/wiki/FAQ#is-web-client-integrated-into-rusetdesk-server-pro">FAQ 條目</a>。為避免混淆，<b>web client</b> 指在瀏覽器分頁中直接使用 RustDesk 發起遠端工作階段，<b>web console</b> 指 RustDesk Server Pro 的管理後台網站，用於管理使用者、裝置、權限、策略與授權。',
|
||||
},
|
||||
{
|
||||
title: '對於臨時支持案例怎麼辦？我們有一些設備需要偶爾支持，但不需要無人值守訪問。',
|
||||
|
||||
@@ -220,7 +220,7 @@ test('does not explain AnyDesk commercial-use detection through mandatory cloud
|
||||
test('labels the public-server capacity number as a non-audited point-in-time internal observation', () => {
|
||||
const article = readPost('rustdesk-scale-50000-200000-devices.md');
|
||||
|
||||
assert.match(article, /point-in-time internal production observation recorded on July 7, 2026/);
|
||||
assert.match(article, /point-in-time internal production observation/);
|
||||
assert.match(article, /not independently audited/);
|
||||
assert.match(article, /no public monitoring dashboard/);
|
||||
assert.doesNotMatch(article, /has operated stably/);
|
||||
@@ -306,3 +306,87 @@ test('uses Server Pro Access Control rather than address-book visibility for aut
|
||||
assert.doesNotMatch(article, /working approach today[^\n]*shared address book/i);
|
||||
assert.doesNotMatch(article, /per-user access control today[^\n]*shared address book/i);
|
||||
});
|
||||
|
||||
test('points license-management posts at the self-service portal with a support fallback', () => {
|
||||
const portalPosts = [
|
||||
'rustdesk-not-connecting-troubleshooting.md',
|
||||
'upgrade-rustdesk-license-mid-subscription.md',
|
||||
'rustdesk-custom-quote-minimum-users-invoice-fees.md',
|
||||
'rustdesk-pro-license-cost-how-to-pay.md',
|
||||
];
|
||||
for (const name of portalPosts) {
|
||||
const article = readPost(name);
|
||||
assert.match(article, /rustdesk\.com\/self-host\/account/, `${name} should link the self-service license portal`);
|
||||
assert.match(article, /support@rustdesk\.com/, `${name} should give the support@ fallback for a forgotten checkout email`);
|
||||
}
|
||||
});
|
||||
|
||||
test('states the air-gapped license-validation grace window', () => {
|
||||
const article = readPost('rustdesk-server-pro-offline-air-gapped.md');
|
||||
|
||||
assert.match(article, /seven days/i);
|
||||
assert.match(article, /grace/i);
|
||||
});
|
||||
|
||||
test('adds the missing competitor migration drivers to the comparison posts', () => {
|
||||
const screenconnect = readPost('rustdesk-vs-screenconnect.md');
|
||||
assert.match(screenconnect, /code-signing/i);
|
||||
assert.match(screenconnect, /July 7, 2025/);
|
||||
|
||||
const teamviewer = readPost('rustdesk-vs-teamviewer.md');
|
||||
assert.match(teamviewer, /perpetual license/i);
|
||||
assert.match(teamviewer, /subscription-only/i);
|
||||
|
||||
const logmein = readPost('rustdesk-vs-logmein.md');
|
||||
assert.match(logmein, /LDAP\/Active Directory/);
|
||||
assert.match(logmein, /single sign-on via OIDC/i);
|
||||
});
|
||||
|
||||
test('answers the enterprise mass-deployment and REST API questions', () => {
|
||||
const article = readPost('rustdesk-for-enterprise.md');
|
||||
|
||||
assert.match(article, /MSI/);
|
||||
assert.match(article, /GPO|Intune/);
|
||||
assert.match(article, /REST API/);
|
||||
});
|
||||
|
||||
test('frames RustDesk compliance around the self-hosted model, not a certification deficit', () => {
|
||||
const article = readPost('remote-desktop-data-sovereignty-gdpr.md');
|
||||
|
||||
assert.match(article, /ISO 27001, SOC 2, or HIPAA/);
|
||||
assert.match(article, /ISO 27001 or HIPAA scope/);
|
||||
assert.match(article, /sales@rustdesk\.com/);
|
||||
assert.doesNotMatch(article, /does not market formal/i);
|
||||
});
|
||||
|
||||
test('every head-to-head comparison post ships FAQ structured data', () => {
|
||||
const comparisons = [
|
||||
'rustdesk-vs-teamviewer.md',
|
||||
'rustdesk-vs-anydesk.md',
|
||||
'rustdesk-vs-screenconnect.md',
|
||||
'rustdesk-vs-splashtop.md',
|
||||
'rustdesk-vs-logmein.md',
|
||||
'rustdesk-vs-rdp.md',
|
||||
'rustdesk-vs-vnc.md',
|
||||
];
|
||||
for (const name of comparisons) {
|
||||
assert.match(readPost(name), /^faq:/m, `${name} should define an faq: block`);
|
||||
}
|
||||
});
|
||||
|
||||
test('shows concrete self-hosted GDPR controls, not just obligations', () => {
|
||||
const article = readPost('remote-desktop-data-sovereignty-gdpr.md');
|
||||
|
||||
assert.match(article, /built-in log rotation/i);
|
||||
assert.match(article, /collected by your relay, not RustDesk/i);
|
||||
assert.match(article, /Control Role/);
|
||||
});
|
||||
|
||||
test('explains custom-client build server, retention window, and config non-retention', () => {
|
||||
const article = readPost('rustdesk-web-console-custom-client-generator-port-21114.md');
|
||||
|
||||
assert.match(article, /compiled on RustDesk's build server/i);
|
||||
assert.match(article, /cross-compile and sign all of those/i);
|
||||
assert.match(article, /automatically deleted from the build server/i);
|
||||
assert.match(article, /deleted automatically once the build finishes/i);
|
||||
});
|
||||
|
||||
Reference in New Issue
Block a user