rustdesk/doc.rustdesk.com
1
0
Fork 0
mirror of https://github.com/rustdesk/doc.rustdesk.com.git synced 2026-07-13 02:04:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix review

Browse Source
This commit is contained in:
rustdesk
2026-07-10 11:45:03 +08:00
parent 2f3564e7dd
commit 8375c220aa
52 changed files with 350 additions and 419 deletions
Download Patch File Download Diff File Expand all files Collapse all files
v3/src/content/post/en/anydesk-alternative-self-hosted.md
+9 -15
View File
@@ -15,7 +15,7 @@ tags:
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."
answer: "RustDesk is open-source and self-hosted: the ID/rendezvous server, relay, console, and stored data run on your own infrastructure, and it's AGPL-licensed, 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?'
@@ -30,17 +30,15 @@ metadata:
keywords: 'AnyDesk alternative, self-hosted AnyDesk alternative, open source AnyDesk alternative, AnyDesk replacement'
---
## Why people are searching for an AnyDesk alternative
## Why people leave AnyDesk: rising bills and lost control
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.
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 — sharpened, for security-conscious buyers, by the fact that AnyDesk publicly disclosed a security incident in early 2024 (evaluate that event through public reporting and AnyDesk's own disclosure).
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. 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.
If that's roughly where you are, you're in the right place. RustDesk takes a genuinely different approach from AnyDesk's cloud — you host it, so the data and the access stay yours — and this page lays out exactly how, and where it fits best.
## The core difference: rent access, or own it
AnyDesk is a cloud service. Your sessions route through infrastructure the vendor owns, and you pay a subscription to keep the lights on. When they change the price or the terms, you adapt.
AnyDesk is a cloud service. Sessions are brokered through vendor infrastructure by default (media can be direct or relayed), and you pay a subscription to keep the lights on. When they change the price or the terms, you adapt.
RustDesk flips that. **RustDesk Server Pro is self-hosted** — the ID/rendezvous server, relay, console, and stored deployment data run on _your_ infrastructure. Direct sessions still flow between endpoints; relayed traffic uses the relay you configure.
@@ -55,7 +53,7 @@ And **RustDesk's core is [open source (AGPL)](/blog/case-for-open-source-remote-
| 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](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 |
| Try without sales call | Varies | Free server today; ask sales about evaluation terms |
For exact AnyDesk pricing and plan tiers, check their current pricing page — we don't quote competitor numbers we can't verify.
@@ -63,7 +61,7 @@ For exact AnyDesk pricing and plan tiers, check their current pricing page — w
You choose where the rendezvous, relay, console, and device data run. Direct connections still travel between endpoints, and relayed traffic uses your configured relay, so self-hosting alone does not guarantee in-country traffic or GDPR compliance. See the [data-sovereignty guide](/blog/remote-desktop-data-sovereignty-gdpr).
## Benefit 2: Choose the concurrency model
## Benefit 2: A different concurrency model
A common licensing question is how simultaneous work is counted. RustDesk standard plans include unlimited concurrent connections, while Customized V2 has a defined concurrency allowance and charges for additional connections. All paid plans must also fit login-user and managed-device counts.
@@ -92,12 +90,8 @@ Do not start by removing AnyDesk. Run both tools during a controlled pilot and v
That pilot tells you whether the control gained through self-hosting is worth the operating work. It also exposes feature or platform dependencies before they become a migration outage.
## Try it without a sales call
## Prove it on your own hardware first
You don't have to book a demo to find out if this fits.
- **Self-host the free open-source community server today** — no cost, no expiry.
- **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.
Stand up the free, open-source community server and point a few test devices at it — it costs nothing and never expires. When you want to evaluate the Pro console, branding, and access controls, email [sales@rustdesk.com](mailto:sales@rustdesk.com) about current evaluation terms and compare standard plan rates at [rustdesk.com/pricing](https://rustdesk.com/pricing). If you'd rather watch before you install, there's a [video demo](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
Start at [rustdesk.com](https://rustdesk.com) and see the code for yourself on [GitHub](https://github.com/rustdesk/rustdesk).
v3/src/content/post/en/anydesk-commercial-use-detected.md
+7 -13
View File
@@ -21,7 +21,7 @@ faq:
answer: "No. AnyDesk's free version is for personal, non-commercial use. Remote work, organizational device administration, and support for customers or colleagues require commercial terms. Check AnyDesk's current terms for the authoritative definition."
- question: 'What counts as commercial use on AnyDesk?'
answer: 'Supporting clients or colleagues, remote work (including checking work email), server administration, managing devices for an organization, or any use you are paid for. Helping family and friends or reaching your own personal devices is personal use.'
- question: 'How does RustDesk avoid commercial-use detection?'
- question: 'Does RustDesk have a commercial-use detector?'
answer: "RustDesk's open-source community server does not implement AnyDesk's commercial-use classifier. Server Pro is commercially licensed and self-hosted, with limits determined by the purchased RustDesk plan rather than an AnyDesk free-tier detector. Standard RustDesk plans include unlimited concurrent connections; Customized V2 does not."
metadata:
description: "AnyDesk flagging your personal use as commercial? Here's the official whitelist fix, what counts as commercial use, and how self-hosted RustDesk avoids it."
@@ -53,11 +53,11 @@ Per AnyDesk's own terms, **personal use** is non-professional — reaching your
- Administering servers or managing multiple devices for an organization
- Any use for which you are paid, directly or indirectly
If you are doing any of that, AnyDesk's detection is working as intended, and the real fix is choosing a tool licensed for how you actually use it — which is where the rest of this guide picks up.
If you are doing any of that, AnyDesk's flag is accurate, and the durable answer is a tool whose license matches how you actually work — which the rest of this guide gets into.
## Why AnyDesk flags "commercial use"
AnyDesk's free tier is licensed for personal use only, and [its terms allow enforcement](https://anydesk.com/en/terms) when use appears professional. AnyDesk does not publish a formula users can safely rely on, so connection counts, session lengths, device limits, or timeout durations from third-party posts should not be presented as official thresholds.
AnyDesk's free tier is licensed for personal use only, and [its terms allow enforcement](https://anydesk.com/en/terms) when use appears professional. AnyDesk publishes no official threshold, so treat any specific connection count, session length, device limit, or timeout from third-party posts as unverified rather than a rule you can rely on.
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.
@@ -69,7 +69,7 @@ AnyDesk supports direct client-to-client connections as well as sessions routed
**RustDesk changes the enforcement point.** The ID/rendezvous server, relay, console, and stored deployment data run on infrastructure you control, so a remote-access SaaS is not classifying each session as personal or commercial. Direct sessions still flow between endpoints, and RustDesk's own commercial license terms still apply to Server Pro.
On top of that, 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 it does on your machines, build it yourself, and run the free community server indefinitely. That is the opposite of a black box watching your connection habits.
On top of that, RustDesk is open source under the [AGPL](/blog/case-for-open-source-remote-access). You can read the code, audit exactly what it does on your machines, build it yourself, and run the free community server indefinitely. That is the opposite of a black box watching your connection habits.
## How the two models compare
@@ -80,7 +80,7 @@ On top of that, RustDesk's core client is open source under the [AGPL](/blog/cas
| 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](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) |
| Pricing model | Free for personal use; paid plans per seat | [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 |
For exact AnyDesk pricing and current free-tier limits, check their own terms directly — we won't quote numbers we can't stand behind.
@@ -112,14 +112,8 @@ Self-host RustDesk and nothing is scanning your sessions for "commercial use" to
| You need a free tool for business use | Compare the license terms of open-source servers; do not assume every free download permits commercial use |
| You need infrastructure and policy control | Pilot a self-hosted option, including server operations, access rules, logging, and client deployment |
For a RustDesk pilot, test the actual workflow that triggered the flag: the same technicians, endpoints, unattended sessions, and support volume. Also size both licensing dimensions—login users and managed devices—before treating “no commercial-use detection” as “no licensing requirements.”
For a RustDesk pilot, test the actual workflow that triggered the flag: the same technicians, endpoints, unattended sessions, and support volume. Also size both licensing dimensions — login users and managed devices — before treating “no commercial-use detection” as “no licensing requirements.”
## What to do next
You don't need a sales call to find out if this works for you:
- **Self-host the free community server today.** It's open source, runs indefinitely, and has no commercial-use detection to trip.
- **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.
Test the free community server or request current Pro evaluation terms before committing to an annual purchase.
If the flag was a mistake, the whitelist request above is your fix. If your use really is commercial, move to licensing that matches it: the free, open-source community server runs indefinitely with no usage classifier to trip, and you can request current evaluation terms for the Pro features from [sales@rustdesk.com](mailto:sales@rustdesk.com) — plan rates are listed at [rustdesk.com/pricing](https://rustdesk.com/pricing). Whichever route you take, test on the community server before committing to an annual purchase.
v3/src/content/post/en/anydesk-price-increase-alternatives.md
+9 -9
View File
@@ -20,8 +20,8 @@ faq:
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: 'Can I audit what the RustDesk client does?'
answer: 'Yes — RustDesk is AGPL open source. You can read exactly what runs on your endpoints, build the client from source, and run the free community server for as long as you like.'
- 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.'
@@ -30,11 +30,11 @@ metadata:
keywords: 'AnyDesk price increase, AnyDesk renewal cost, AnyDesk pricing alternatives, AnyDesk three-year TCO'
---
If you searched for "AnyDesk price increase," compare your dated renewal quote with current alternatives and include migration and operating costs. Compare current public or written quotes.
If you searched for "AnyDesk price increase," you have two real options: renew and negotiate, or switch to a model whose cost you control. This guide weighs both — comparing your dated renewal quote against current written quotes, migration, and operating costs — and shows where self-hosting RustDesk changes the math.
That is the trap of the subscription remote-desktop market. Your tooling cost is set by a vendor's roadmap, not yours. This guide is for teams — [MSPs](/blog/rustdesk-for-msps), internal IT, support desks — who are tired of that cycle and want a remote support solution with a cost they actually control. We'll be honest about the trade-offs, but the short version is: self-hosting changes who holds the pricing power.
That is the trap of the subscription remote-desktop market. Your tooling cost is set by a vendor's roadmap, not yours. This guide is for teams — [MSPs](/blog/rustdesk-for-msps), internal IT, support desks — who are tired of that cycle and want a remote support solution with a cost they actually control. The short version: self-hosting changes who holds the pricing power.
## Why the AnyDesk price increase keeps happening
## Why subscription renewals climb
A cloud subscription is a recurring lever. The vendor owns the infrastructure your sessions run through, so renewal pricing, seat tiers, and channel counts are theirs to adjust. When they do, your only options are pay more or migrate — and migration is painful enough that most teams just pay.
@@ -59,7 +59,7 @@ RustDesk licensing is **per login-user plus per managed-device**, and you can [u
| What you're evaluating | Cloud subscription tools | RustDesk Server Pro |
| -------------------------- | ------------------------ | --------------------------------------------------------------------------------- |
| Where sessions run | Vendor's cloud | Your server (on-prem or your VPS) |
| Who sets renewal pricing | The vendor | You host it; cost is your infrastructure + license |
| Who sets renewal pricing | The vendor | You for the infrastructure; the license renews annually at current rates |
| Concurrent connections | Often tiered/limited | Unlimited on standard plans; limited on Customized V2 |
| Licensing model | Per seat / per channel | [Per login-user + per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) |
| Source code | Closed | [Open source (AGPL)](/blog/case-for-open-source-remote-access), auditable |
@@ -100,7 +100,7 @@ Put each option into the same worksheet instead of comparing one renewal quote w
| Cost input | AnyDesk renewal | Self-hosted alternative |
| ------------------------------------------ | -------------------------: | --------------------------------------------------: |
| Required licensed users and endpoints | Your dated quote | Login users plus managed devices |
| Required concurrency or channels | Plan allowance and add-ons | Standard-plan or Customized V2 allowance |
| Required concurrency or channels | Plan allowance and add-ons | Unlimited on standard plans; defined Customized V2 allowance |
| Hosting, backup, monitoring, and bandwidth | Usually included in SaaS | Your infrastructure cost |
| Deployment and migration labor | Policy/client changes | Server setup, client rollout, access mapping |
| Ongoing administration | Vendor/account management | Patching, certificates, capacity, incident response |
@@ -110,6 +110,6 @@ Run a base case and a growth case for the same 36-month period. A self-hosted op
## Run the comparison on your own infrastructure
You do not need to book a demo to find out if this fits. **Self-host the free community server today**, or email [sales@rustdesk.com](mailto:sales@rustdesk.com) for current Pro evaluation terms. Point a couple of technicians and a handful of devices at it, run real sessions, and see whether owning your infrastructure feels like the right trade for your team. Prefer to watch first? There's a full [video walkthrough](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
You do not need to book a demo to find out if this fits. Give the free community server a couple of technicians and a handful of devices, run real sessions for a week, and see whether owning the infrastructure feels like the right trade — it is open source and costs nothing to keep running. For Pro evaluation terms, write to [sales@rustdesk.com](mailto:sales@rustdesk.com), and feed the per-user and per-device numbers from [rustdesk.com/pricing](https://rustdesk.com/pricing) into the three-year worksheet above.
The next price-increase email is a matter of when, not if. Self-hosting is how you stop being on the receiving end of it.
If another price-increase email comes, self-hosting is how you stop being on the receiving end of it.
v3/src/content/post/en/avoid-remote-desktop-scams.md
+2 -2
View File
@@ -39,7 +39,7 @@ The [U.S. Federal Trade Commission](https://consumer.ftc.gov/articles/how-spot-a
4. **Read out the code.** You are told to read them the connection ID or one-time code on your screen. That single step is the moment they get in.
5. **Take control.** They fake a virus scan, open your banking site, move money, or set up new accounts. The [FBI's Boston field office](https://www.fbi.gov/contact-us/field-offices/boston/news/press-releases/fbi-warns-public-to-beware-of-tech-support-scammers-targeting-financial-accounts-using-remote-desktop-software) has warned that scammers use this access to open virtual-currency accounts and liquidate victims' genuine bank balances.
The losses are not theoretical. In that same FBI warning, investigators described a Maine couple who lost roughly **$1.1 million** after a pop-up told them to call a number for "Fidelity," were instructed to install remote-desktop software, and let fake "Microsoft" and "Fidelity" representatives watch their accounts.
The losses are not theoretical. In that same FBI warning, investigators described a Maine couple who, after a pop-up told them to call a number for "Fidelity," were instructed to install remote-desktop software and let fake "Microsoft" and "Fidelity" representatives watch their accounts — losing roughly **$1.1 million**.
## The red flags
@@ -89,7 +89,7 @@ Prevention comes down to a few habits:
It is worth repeating: the software is not the villain. Remote-desktop tools are how IT teams keep the world's computers running, and the exact same app can be a lifeline or a weapon depending on who is holding it. Blaming any one product misses the point — the defense is controlling who you let in.
That said, if you _run_ remote support professionally, a few structural choices reduce your exposure. Self-hosting the RustDesk server means the ID and relay servers run on infrastructure you control, so you decide exactly which clients are allowed to connect rather than trusting a vendor cloud to arbitrate it. For your own fleet, practice basic [unattended-access hygiene](/blog/rustdesk-unattended-access-setup): strong, unique permanent passwords, connections restricted to your device groups and [shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book), and two-factor authentication. And because the RustDesk client is [open source](/blog/case-for-open-source-remote-access), you or a security team can audit exactly what it does on your machines.
That said, if you _run_ remote support professionally, a few structural choices reduce your exposure. Self-hosting the RustDesk server means the ID and relay servers run on infrastructure you control, so you decide exactly which clients are allowed to connect rather than trusting a vendor cloud to arbitrate it. For your own fleet, practice basic [unattended-access hygiene](/blog/rustdesk-unattended-access-setup): strong, unique permanent passwords, connections restricted to your device groups and [shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book), and two-factor authentication. And because RustDesk is [open source](/blog/case-for-open-source-remote-access), you or a security team can audit exactly what it does on your machines.
None of that makes RustDesk — or anything else — scam-proof. A user tricked into installing a client and reading out a code can be victimized on any platform. Structure lowers certain risks; it never replaces the simple rule at the center of every warning above: do not hand control of your computer to someone who contacted _you_.
v3/src/content/post/en/best-free-remote-desktop-software.md
+8 -10
View File
@@ -4,7 +4,7 @@ lang: en
translationKey: best-free-remote-desktop-software
draft: false
title: 'Best Free Remote Desktop Software for Business (2026)'
excerpt: 'Genuinely free remote desktop tools — including ones you can use for business without a commercial-use flag. Six honest options, each with its catch.'
excerpt: 'Genuinely free remote desktop tools — including ones you can use for business without a commercial-use flag. Six real options, each with its catch.'
image: ~/assets/images/blog/best-free-remote-desktop-software-og.png
category: Guides
tags:
@@ -16,7 +16,7 @@ faq:
- question: 'What is the best free remote desktop software for business use?'
answer: 'RustDesk stands out when a business needs open-source code and a self-hosted community server with no commercial-use classifier. Chrome Remote Desktop is also free and Google documents enterprise administration policies for it, but it uses Google accounts and a Google-operated control plane. Apache Guacamole and MeshCentral are business-friendly infrastructure projects with different operating models.'
- 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."
answer: "Yes. RustDesk's open-source software 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 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?'
@@ -28,7 +28,7 @@ metadata:
## What "free" should actually mean
Search "free remote desktop software" and you'll get a wall of tools that are free — right up until they aren't. TeamViewer and AnyDesk both offer free tiers, but they're licensed for personal use, and their software watches your connection patterns. Do anything that looks like work and you can get [flagged for commercial use on TeamViewer](/blog/teamviewer-commercial-use-detected) or [the same thing on AnyDesk](/blog/anydesk-commercial-use-detected) — sessions time out, and you're pushed toward a paid plan.
Search "free remote desktop software" and you'll get a wall of tools that are free — right up until they aren't. TeamViewer and AnyDesk both offer free tiers, but they're licensed for personal use, and both enforce that boundary with automated commercial-use detection. Do anything that looks like work and you can get [flagged for commercial use on TeamViewer](/blog/teamviewer-commercial-use-detected) or [the same thing on AnyDesk](/blog/anydesk-commercial-use-detected) — sessions time out, and you're pushed toward a paid plan.
So this guide applies a stricter test. To make the list, a tool has to be **genuinely free to run** — and ideally free for **business** use with no commercial-use trip wire. That rules out the "free until we decide it isn't" tier and leaves the tools you can actually build a workflow on.
@@ -40,7 +40,7 @@ The order below starts with the tools that are genuinely free for business use a
### RustDesk — free, open source, no commercial-use nag
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.
RustDesk sits first here because it 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, and Linux hosts it includes file transfer and permanent-password unattended access; Android can host attended sessions, and the iOS app is controller-only. The source can be inspected and built independently.
**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).
@@ -78,7 +78,7 @@ VNC is the granddaddy of open remote access. Free implementations like [TigerVNC
| Tool | Free for business? | Self-host a server? | Best for |
| -------------------------------- | ----------------------------------------- | ------------------------------ | ------------------------------------------------ |
| **RustDesk** | Yes (AGPL client + free community server) | Yes (free server / Server Pro) | Cross-platform access with no commercial-use nag |
| **RustDesk** | Yes (AGPL + free community server) | Yes (free server / Server Pro) | Cross-platform access with no commercial-use nag |
| Chrome Remote Desktop | Yes; enterprise policies available | No self-hosted control plane | Simple access with Google-managed coordination |
| VNC (TigerVNC/TightVNC/UltraVNC) | Yes (open protocol) | Yes (you assemble it) | LAN/DIY access with a VPN |
| Apache Guacamole | Yes (Apache 2.0) | Yes (gateway) | Browser access to existing RDP/VNC/SSH |
@@ -91,7 +91,7 @@ For exact TeamViewer and AnyDesk terms, check their current pages — we don't q
Most of the free options make you choose between Google-managed simplicity (CRD), heavier infrastructure (Guacamole and MeshCentral), or DIY networking (VNC). RustDesk's pitch is that you don't have to trade away business use, cross-platform reach, self-hosting, or auditability to run something free.
- **Open source you can audit.** The client is [AGPL](/blog/case-for-open-source-remote-access) — read it, build it, verify it.
- **Open source you can audit.** The code is [AGPL](/blog/case-for-open-source-remote-access) — read it, build it, verify it.
- **A community server without a license fee.** Self-host it under its open-source license; infrastructure and operating costs remain yours.
- **No black-box vendor.** Sessions run through infrastructure you control, not a cloud that can meter or flag you.
- **Every major platform.** Windows, macOS, Linux, and Android hosts; iOS is a controller app.
@@ -102,10 +102,8 @@ When your team outgrows the free server, [Server Pro](/blog/rustdesk-pro-license
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
## Start free, stay free if it fits
- **Self-host the free, open-source community server today** — no cost, no expiry, no commercial-use flag.
- **Want the Pro team features?** Email [sales@rustdesk.com](mailto:sales@rustdesk.com) for current evaluation terms, or see [rustdesk.com/pricing](https://rustdesk.com/pricing).
- **Prefer to see it first?** Watch a [video walkthrough](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
The community server is the rare kind of free that stays free: open source, no expiry, and no commercial-use flag waiting to trip. Run it for as long as it serves you; if your team later wants the Pro console and branded clients, [sales@rustdesk.com](mailto:sales@rustdesk.com) handles evaluation-terms questions and [rustdesk.com/pricing](https://rustdesk.com/pricing) has the current rates.
Read the code on [GitHub](https://github.com/rustdesk/rustdesk), stand up a server, and decide for yourself.
v3/src/content/post/en/best-screenconnect-alternative-msps.md
+8 -16
View File
@@ -15,7 +15,7 @@ tags:
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.'
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 (Basic plan and up) 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?'
@@ -30,21 +30,19 @@ metadata:
keywords: 'ScreenConnect alternative, ConnectWise Control alternative for MSPs, self-hosted ScreenConnect replacement, MSP remote support alternative'
---
## Why MSPs are evaluating ScreenConnect alternatives
## The short answer for MSPs weighing ScreenConnect alternatives
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.
[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) 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.
## The core difference: you host it, so you control it
The biggest structural difference between RustDesk and ScreenConnect's cloud offering is who operates the server-side services. 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; sessions use your relay only when direct connectivity fails or relay is forced.
The biggest structural difference between RustDesk and ScreenConnect's cloud offering is who operates the server-side services. 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; sessions use your relay only when direct connectivity fails or relay is forced — and you can prove the concept on the free community server first.
The free community server supports a self-hosted proof of concept before a buyer evaluates paid Server Pro features.
On top of that, RustDesk's core client is **[open source (AGPL)](/blog/case-for-open-source-remote-access)**. You can read the code, audit exactly what the client does on a customer's machine, build it yourself, and run the free community server indefinitely. For an MSP that has to answer a hospital's or a bank's security questionnaire, "here's the source, and it runs on our servers" is a much stronger answer than "trust our cloud."
On top of that, RustDesk is **[open source (AGPL)](/blog/case-for-open-source-remote-access)**. You can read the code, audit exactly what the client does on a customer's machine, build it yourself, and run the free community server indefinitely. For an MSP that has to answer a hospital's or a bank's security questionnaire, "here's the source, and it runs on our servers" is a much stronger answer than "trust our cloud."
## RustDesk vs ScreenConnect at a glance
@@ -54,16 +52,14 @@ On top of that, RustDesk's core client is **[open source (AGPL)](/blog/case-for-
| 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](https://rustdesk.com/pricing#custom2) limited |
| Custom-branded client | Available (see vendor) | Custom-branded client generator |
| Custom-branded client | Available (see vendor) | Custom-branded client generator (Basic plan and up) |
| [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 |
| Evaluate without sales call | Varies | Free server today; ask sales about evaluation terms |
For exact RustDesk prices and plan-by-plan feature availability, [see rustdesk.com/pricing](https://rustdesk.com/pricing).
## No per-channel tax, no concurrency ceiling on standard plans
Compare the products through a proof of concept that covers features, cost, usability, migration, and operating effort.
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. Upgrades can be prorated.
## Built for MSP operations: branding, console, access control
@@ -96,8 +92,4 @@ Keep ScreenConnect available during the pilot. A passing scorecard and a tested
## Run an MSP proof of concept
You do not need a full migration to test the model.
- **Self-host the free open-source community server today** — open source, no cost, no expiry.
- **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 walkthrough](/blog/see-rustdesk-in-action).
You do not need a full migration to test the model. Work the scorecard above against the free, open-source community server, which costs nothing and has no expiry date. When branded clients, scoped technician access, and SSO enter the picture, ask [sales@rustdesk.com](mailto:sales@rustdesk.com) what evaluation terms are currently offered, and size the plans at [rustdesk.com/pricing](https://rustdesk.com/pricing).
v3/src/content/post/en/chrome-remote-desktop-alternative.md
+9 -15
View File
@@ -15,13 +15,13 @@ tags:
author: RustDesk Team
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.'
answer: 'Yes. Self-hosted RustDesk needs no third-party account at all (the public demo server requires a free controller sign-in), using 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 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?'
answer: "RustDesk's client core is open source under the AGPL, and you can run the free community server indefinitely at no cost. The commercial Server Pro adds team features and is self-hosted; see rustdesk.com/pricing for current terms."
answer: "RustDesk is open source under the AGPL, and you can run the free community server indefinitely at no cost. The commercial Server Pro adds team features and is self-hosted; see rustdesk.com/pricing for current terms."
metadata:
description: 'Chrome Remote Desktop is free and simple but ties you to Google and lacks key features. Compare it with RustDesk, an open-source, self-hosted alternative.'
keywords: 'Chrome Remote Desktop alternative, self-hosted Chrome Remote Desktop alternative, remote desktop without Google account, RustDesk vs Chrome Remote Desktop'
@@ -33,8 +33,6 @@ 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.
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
Credit where it's due. [TechRadar's review](https://www.techradar.com/reviews/chrome-remote-desktop-review) calls it "completely free with no subscriptions or premium tiers," easy to set up, and a solid fit for personal use. It runs on Windows, macOS, and Linux, needs no license negotiation, and there's nothing to host. If you want to check on your home PC from your phone, CRD is close to zero-effort.
@@ -45,7 +43,7 @@ That simplicity is the product. The trouble starts when you ask it to do the thi
### Missing features: self-hosted control, device management, and team workflows
Google's help pages document remote access to files and applications and let administrators control access and network behavior, but they still describe a Google-account-based service with Google-operated coordination. The network guide shows sessions are negotiated through Google services first, then carried as Direct, STUN, or TURN/relay P2P traffic. In other words: CRD is fine for simple access, but it is not a self-hosted support console with RustDesk-style device groups or custom branding.
Google's help pages document remote access to files and applications and let administrators control access and network behavior, but they still describe a Google-account-based service with Google-operated coordination — the signaling-and-relay split covered in the intro. In other words: CRD is fine for simple access, but it is not a self-hosted support console with RustDesk-style device groups or custom branding.
### Unattended access and sleeping machines
@@ -53,27 +51,27 @@ CRD can do unattended access, but the target still has to be **powered on and on
### Managing users and the Google-account requirement
Every participant needs a Google account, and for shared (non-unattended) sessions someone has to be present to grant access. Google Workspace administrators can [enable or disable CRD and constrain firewall traversal](https://support.google.com/chrome/a/answer/2799701), but that is not the same as a self-hosted support console with device groups and scoped technician access. Google services still handle identity and initial negotiation; media may be direct or relayed depending on ICE/WebRTC connectivity. (For the security angle specifically, see [is Chrome Remote Desktop safe?](/blog/is-chrome-remote-desktop-safe))
Every participant needs a Google account, and for shared (non-unattended) sessions someone has to be present to grant access. Google Workspace administrators can [enable or disable CRD and constrain firewall traversal](https://support.google.com/chrome/a/answer/2799701), but that is not the same as a self-hosted support console with device groups and scoped technician access — and Google still sits in the identity and session-setup path, as described in the intro. (For the security angle specifically, see [is Chrome Remote Desktop safe?](/blog/is-chrome-remote-desktop-safe))
## Chrome Remote Desktop vs. RustDesk at a glance
| | Chrome Remote Desktop | RustDesk |
| ----------------------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Cost | Free | Open-source client (AGPL); free community server; paid Server Pro |
| Cost | Free | Open source (AGPL); free community server; paid Server Pro |
| Control plane and traffic | Google identity/signaling; direct, STUN, or Google-relayed media | [Self-hosted](/blog/why-self-host-remote-desktop-software) server roles; direct or self-relayed media |
| Source code | Proprietary | Open source ([AGPL](/blog/case-for-open-source-remote-access)), auditable |
| Account needed | Google account on both ends | Your own ID; no third-party account required |
| File transfer / transfer workflows | Google documents access to files and applications | Built in |
| File transfer / transfer workflows | Upload/download only (no drag-and-drop) | Built in |
| [Unattended access](/blog/rustdesk-unattended-access-setup) | Same Google account, machine must be awake | Permanent-password access to a fleet you manage |
| Central management | Google Admin policies; no self-hosted support console | Web console, [device groups, shared address book](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book) |
| Custom branding | No | Custom-branded client generator |
| Custom branding | No | Custom-branded client generator (Basic plan and up) |
| Platforms | Win/macOS/Linux (in Chrome) | Win/macOS/[Linux](/blog/rustdesk-for-linux)/Android; iOS controller app |
## Where RustDesk fits: self-hosted and open source
RustDesk is built around the two things CRD structurally can't offer: **you host the infrastructure, and you can read the code.**
RustDesk's client core is open source under the **[AGPL](/blog/case-for-open-source-remote-access)** — you can audit exactly what runs on your machines, build it yourself, and run the **free community server indefinitely**. When you move to Server Pro, it's **[self-hosted by design](/blog/why-self-host-remote-desktop-software)**: the ID/rendezvous and relay servers run on your own machine or a VPS you rent, so there's no Google (or any vendor) cloud in the middle. Note the honest nuance for compliance planning: direct connections still travel between endpoints, and relayed traffic uses your relay, so review the [data-sovereignty implications](/blog/remote-desktop-data-sovereignty-gdpr) rather than assuming server location controls every packet.
RustDesk is open source under the **[AGPL](/blog/case-for-open-source-remote-access)** — you can audit exactly what runs on your machines, build it yourself, and run the **free community server indefinitely**. When you move to Server Pro, it's **[self-hosted by design](/blog/why-self-host-remote-desktop-software)**: the ID/rendezvous and relay servers run on your own machine or a VPS you rent, so there's no Google (or any vendor) cloud in the middle. One nuance for compliance planning: direct connections still travel between endpoints, and relayed traffic uses your relay, so review the [data-sovereignty implications](/blog/remote-desktop-data-sovereignty-gdpr) rather than assuming server location controls every packet.
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.
@@ -83,10 +81,6 @@ The step up from Chrome Remote Desktop is control: brokering, access policy, and
## Try it without a sales call
You can evaluate RustDesk on your own terms:
- **Self-host the free, open-source community server today** — no cost, no expiry, no Google account.
- **Want the Pro team features?** Email [sales@rustdesk.com](mailto:sales@rustdesk.com) for current evaluation terms, or compare plans at [rustdesk.com/pricing](https://rustdesk.com/pricing).
- **Prefer to see it first?** Watch a [video walkthrough](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
You can evaluate RustDesk on your own terms, with no Google account anywhere in the loop. The open-source community server is free to run for as long as you like; when the Pro team features matter, [sales@rustdesk.com](mailto:sales@rustdesk.com) can tell you the current evaluation terms, and [rustdesk.com/pricing](https://rustdesk.com/pricing) lists the plan rates.
Read the code for yourself on [GitHub](https://github.com/rustdesk/rustdesk), point a couple of devices at your own server, and decide whether the trade-offs fit before committing anything.
v3/src/content/post/en/gotomypc-alternative-self-hosted.md
+7 -9
View File
@@ -15,13 +15,13 @@ tags:
author: RustDesk Team
faq:
- question: 'Is there a self-hosted alternative to GoToMyPC?'
answer: 'Yes. GoToMyPC is a vendor-hosted remote access service. RustDesk is self-hosted by design: the ID/rendezvous, relay, and management services run on infrastructure you control. Direct sessions still flow between endpoints, while relayed sessions use your configured relay. The RustDesk client is also open source under the AGPL.'
answer: 'Yes. GoToMyPC is a vendor-hosted remote access service. RustDesk is self-hosted by design: the ID/rendezvous, relay, and management services run on infrastructure you control. Direct sessions still flow between endpoints, while relayed sessions use your configured relay. RustDesk is also open source under the AGPL.'
- question: "How does RustDesk licensing compare to GoToMyPC's per-computer pricing?"
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 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.'
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 the usual server duties — patching, certificates, key backup, monitoring — are 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.
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.
RustDesk is a different model from GoToMyPC's per-computer cloud: you host it, so you own the access and the data. Here is how it maps onto the GoToMyPC workflow.
## What GoToMyPC is (and isn't)
@@ -41,7 +41,7 @@ Two things send people looking for an alternative. First, it is **cloud-only**:
GoToMyPC operates the service for you. With RustDesk, you deploy the ID/rendezvous and relay services, configure each endpoint to use them, and own server uptime. Direct sessions flow between the two endpoints when NAT traversal works; otherwise they use your relay.
That introduces work GoToMyPC normally hides: server patching, certificates, firewall rules, key backup, monitoring, and recovery. In return, you choose where the server-side services and device administration run. The RustDesk client is [open source under the AGPL](/blog/case-for-open-source-remote-access), and the community server is available for a no-license-cost proof of concept.
That introduces work GoToMyPC normally hides: server patching, certificates, firewall rules, key backup, monitoring, and recovery. In return, you choose where the server-side services and device administration run. RustDesk is [open source under the AGPL](/blog/case-for-open-source-remote-access), and the community server is available for a no-license-cost proof of concept.
## GoToMyPC vs. RustDesk at a glance
@@ -73,14 +73,12 @@ 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.
## Own the server, not a per-seat bill
## Own the server, not a per-computer bill
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
## Stand up your own server this week
- **Self-host the free, open-source community server today** — no cost, no expiry.
- **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.
The free, open-source community server is enough to test the whole unattended workflow: install it, enroll a machine you own, and try reaching that machine after a reboot. Nothing expires, and no bill arrives per computer. When you are ready to look at the Pro console and access controls, email [sales@rustdesk.com](mailto:sales@rustdesk.com) for the current evaluation terms and check the standard rates at [rustdesk.com/pricing](https://rustdesk.com/pricing).
If cost and control are why you are looking past GoToMyPC, a self-hosted, open-source alternative is worth standing up and testing.
v3/src/content/post/en/is-anydesk-safe.md
+5 -5
View File
@@ -21,11 +21,11 @@ faq:
- question: "Is AnyDesk's encryption secure?"
answer: "AnyDesk's security documentation describes TLS 1.2 with AEAD, an RSA-2048 asymmetric key exchange, and 256-bit AES transport encryption, plus perfect forward secrecy. Those are industry-standard protections. The caveat is that you are trusting a closed-source client and, by default, AnyDesk's cloud to broker the connection, so you rely on the vendor's operational security rather than being able to audit the code yourself."
metadata:
description: 'Is AnyDesk safe? A fair look at its encryption, the 2024 production-systems breach, and why scammers abuse it — plus how open source compares.'
description: 'Is AnyDesk safe? Sourced review of its TLS/AES encryption, the 2024 production-systems breach, scam abuse, and closed-source trade-offs.'
keywords: 'is AnyDesk safe, AnyDesk security, AnyDesk breach 2024, AnyDesk scam, AnyDesk encryption, is AnyDesk safe to use, AnyDesk hacked'
---
Short version: yes, AnyDesk is a legitimate, generally secure commercial remote-desktop product for people using it on purpose. The risks worth understanding aren't that AnyDesk is malware — it isn't — but that it's closed source, cloud-brokered by default, had a notable breach in 2024, and is one of the tools scammers most love to abuse. Here's the fair, sourced version.
The quick answer: yes, AnyDesk is a legitimate, generally secure commercial remote-desktop product for people using it on purpose. The risks worth understanding aren't that AnyDesk is malware — it isn't — but that it's closed source, cloud-brokered by default, had a notable breach in 2024, and is one of the tools scammers most love to abuse. What follows is the fair, sourced picture.
## The short answer
@@ -59,13 +59,13 @@ Here's where AnyDesk's model and RustDesk's part ways — not on whether the enc
AnyDesk is proprietary. You cannot read the client's source, build it yourself, or independently verify what it does; you trust AnyDesk that the binary behaves as advertised. And by default your sessions are brokered through AnyDesk's cloud, so the availability and security of that infrastructure are the vendor's to manage — as 2024 illustrated. AnyDesk's higher tiers offer an on-premises appliance, which narrows this gap for those who buy in.
RustDesk approaches the same problem from a different assurance basis. The client is [open source under the AGPL](/blog/case-for-open-source-remote-access), so the code is auditable and buildable. Self-hosting also lets you operate the ID/rendezvous, relay, console, and stored deployment data. That can support a [data-sovereignty design](/blog/remote-desktop-data-sovereignty-gdpr), but endpoint locations, direct-session routing, retention, and legal obligations still have to be assessed.
RustDesk approaches the same problem from a different assurance basis. RustDesk is [open source under the AGPL](/blog/case-for-open-source-remote-access), so the code is auditable and buildable. Self-hosting also lets you operate the ID/rendezvous, relay, console, and stored deployment data. That can support a [data-sovereignty design](/blog/remote-desktop-data-sovereignty-gdpr), but endpoint locations, direct-session routing, retention, and legal obligations still have to be assessed.
To be equally fair: open source is not a magic shield. RustDesk's own defects are public too, so track the [latest releases](https://github.com/rustdesk/rustdesk/releases) and current vulnerability records. Self-hosting alone does not make a deployment compliant or secure; direct session traffic still flows between endpoints, and you are responsible for patching the server.
## The verdict
## So, is AnyDesk safe?
Is AnyDesk safe? For deliberate, legitimate use: yes — it's a mature product with standard-grade encryption and sensible account controls, and it's used safely at scale every day. Rate it as reasonably secure, because that's accurate.
For deliberate, legitimate use: yes — it's a mature product with standard-grade encryption and sensible account controls, and it's used safely at scale every day. Treat it as reasonably secure, because that's what the record supports.
The qualifiers are the honest part. Its default cloud-brokered, closed-source model means you're trusting AnyDesk's operational security, which took a real hit in 2024. And its most common real-world harm comes from scammers exploiting how easy it is to install — a human problem, not a cryptographic one. If those trade-offs sit wrong with you, an [open-source, self-hosted alternative](/blog/anydesk-alternative-self-hosted) changes the assurance basis: auditable code and brokering you control, at the cost of running a server yourself.
v3/src/content/post/en/is-chrome-remote-desktop-safe.md
+3 -3
View File
@@ -21,7 +21,7 @@ faq:
- question: 'Can I self-host Chrome Remote Desktop?'
answer: "No. Chrome Remote Desktop is brokered entirely through Google's infrastructure and tied to your Google account; there is no option to run the connection service on your own server or to audit the client code. If self-hosting and code you can inspect matter to you, an open-source alternative is a different assurance model."
metadata:
description: 'Is Chrome Remote Desktop safe? A fair look at its encryption, PIN and Google-account model, the real risks, and where self-hosting differs.'
description: 'Is Chrome Remote Desktop safe? What Google documents about CRD encryption, PIN protection, the practical risks, and the Google-account trust model.'
keywords: 'is Chrome Remote Desktop safe, Chrome Remote Desktop security, Chrome Remote Desktop encryption, Chrome Remote Desktop PIN, Chrome Remote Desktop risks, CRD safe'
---
@@ -37,7 +37,7 @@ Where you should pause is anything beyond casual use. CRD is tied to your Google
Three mechanisms do the real work, all documented on [Google's help pages](https://support.google.com/chrome/answer/1649523):
- **Encryption.** Google states that "all remote desktop sessions are fully encrypted." Independent reviews describe the connection as using standard web transport security (TLS with AES). Google doesn't publish a detailed protocol breakdown on its consumer pages, so treat the encryption as adequate but not something you can independently audit.
- **Encryption.** Google states that "all remote desktop sessions are fully encrypted." Third-party analyses generally describe the connection as using standard web transport security (TLS with AES). Google doesn't publish a detailed protocol breakdown on its consumer pages, so treat the encryption as adequate but not something you can independently audit.
- **PIN for unattended access.** To reach a computer you've set up for ongoing remote access, you enter a PIN. This is what stops a random person with your Google session from silently connecting.
- **One-time access codes for support.** When you're helping someone in real time, the host generates a code that, per Google, works only once, and continued sharing requires re-confirmation periodically.
@@ -59,7 +59,7 @@ CRD is deliberately minimal, and for a lot of people that's the appeal. But it's
You can't self-host it. Every CRD connection is brokered through Google's cloud and tied to a Google account; there's no option to run the rendezvous service on your own server, and no source code to audit — you trust Google that the host behaves as described. There's also little in the way of team administration, centralized policy, access-control lists, session logging, or device grouping. That's not a knock on Google; it's just not what CRD is for. If you need those, you've outgrown it, and a [more capable free remote-desktop tool](/blog/best-free-remote-desktop-software) or a [dedicated Chrome Remote Desktop alternative](/blog/chrome-remote-desktop-alternative) is the honest next step.
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.
This is where an open-source, self-hosted model offers a different _kind_ of assurance rather than just more features. With RustDesk, the software 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.
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.
v3/src/content/post/en/open-source-remote-desktop-software.md
+4 -4
View File
@@ -22,7 +22,7 @@ faq:
- 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.'
answer: 'RustDesk offers Windows, macOS, Linux, and Android host/controller clients, plus iOS and web-client controller options. Desktop hosts (Windows, macOS, Linux) support permanent-password unattended access managed from a self-hosted web console, alongside ad-hoc attended sessions; Android control is best treated as attended support, and iOS and the web client 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.'
@@ -58,7 +58,7 @@ Those concerns are structural: closed tools can change price, packaging, and hos
| Apache Guacamole | Yes | Yes | Clientless gateway; needs setup |
| RustDesk | Yes (AGPL core) | Yes (Server Pro / free community server) | Yes — device groups, address book, custom client |
| TeamViewer | No | No | Yes (vendor cloud) |
| AnyDesk | No | On-premises offering available | Yes |
| AnyDesk | No | On-premises appliance on top tier only | Yes |
VNC variants are proven and genuinely open, but you're building the connection, NAT traversal, and access control around them. Guacamole is a great browser-based gateway if you want clientless access, though it's an infrastructure project in its own right. RustDesk aims to give you the auditable, self-hostable core _plus_ the support-team features that closed tools sell — without the closed part.
@@ -82,7 +82,7 @@ Open source doesn't have to mean "bring your own everything." RustDesk ships a s
- **Unlimited [concurrent connections](/blog/rustdesk-concurrent-connections-limit) on standard plans; limited on Customized V2.** Several technicians can run sessions at the same time — you pay [per login-user and per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay), not per channel.
- **Server-side services you host and control.** Run the ID/relay and management services on your infrastructure; direct sessions still flow between endpoints.
- **Open source.** The client core is [AGPL](/blog/case-for-open-source-remote-access) — audit it, build it yourself, and run the free community server for as long as you like.
- **Open source.** RustDesk is [AGPL](/blog/case-for-open-source-remote-access)-licensed — audit it, build it yourself, and run the free community server for as long as you like.
- **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.
@@ -92,7 +92,7 @@ Open source doesn't have to mean "bring your own everything." RustDesk ships a s
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
### Prove it on a spare VM today
You can evaluate on your own terms. Self-host the free, open-source community server today, or email [sales@rustdesk.com](mailto:sales@rustdesk.com) for current evaluation terms for the Pro features — or compare plans at [rustdesk.com/pricing](https://rustdesk.com/pricing). Stand it up, point a couple of devices at it, and see whether the trade-offs fit before you commit a cent of real budget. Prefer to watch first? There's a full [video walkthrough](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
v3/src/content/post/en/remote-desktop-alternatives-dameware-bomgar-supremo-parsec-remotepc.md
+23 -20
View File
@@ -3,8 +3,8 @@ publishDate: 2026-07-09T16:08:00Z
lang: en
translationKey: remote-desktop-alternatives-dameware-bomgar-supremo-parsec-remotepc
draft: false
title: 'RustDesk vs Dameware, BeyondTrust, Supremo, Parsec, RemotePC'
excerpt: 'A comparison hub for teams evaluating RustDesk against Dameware, BeyondTrust/Bomgar, Supremo, Parsec, and RemotePC.'
title: 'RustDesk vs Dameware, BeyondTrust, Supremo, Parsec, RemotePC, HelpWire'
excerpt: 'A comparison hub for teams evaluating RustDesk against Dameware, BeyondTrust/Bomgar, Supremo, Parsec, RemotePC, and HelpWire.'
image: ~/assets/images/blog/remote-desktop-alternatives-dameware-bomgar-supremo-parsec-remotepc-og.png
category: Alternatives
tags:
@@ -13,14 +13,14 @@ tags:
- comparison
faq:
- question: 'Which of these tools is closest to a self-hosted RustDesk deployment?'
answer: 'The products serve different jobs, so there is no single closest match. Dameware and BeyondTrust are commonly evaluated for enterprise administration and support, Supremo and RemotePC for general remote access, and Parsec for low-latency visual workloads. RustDesk is differentiated by its open-source client and self-hosted ID and relay services.'
answer: 'The products serve different jobs, so there is no single closest match. Dameware and BeyondTrust are commonly evaluated for enterprise administration and support, Supremo and RemotePC for general remote access, and Parsec for low-latency visual workloads. RustDesk is differentiated by its open-source software and self-hosted ID and relay services.'
- question: 'Can RustDesk replace Parsec for CAD or creative work?'
answer: 'Do not assume so from a feature list. Codec support, color behavior, input latency, GPU use, display topology, and WAN conditions all affect creative workloads. Benchmark the exact applications and hardware before choosing.'
- question: 'Is RustDesk cheaper than Dameware, BeyondTrust, Supremo, or RemotePC?'
answer: 'It depends on the same users, managed devices, concurrency, support, features, hosting, and operating labor. Compare current written quotes and include self-hosting costs; list prices from different packaging models are not directly comparable.'
metadata:
description: 'A comparison hub for teams evaluating RustDesk against Dameware, BeyondTrust/Bomgar, Supremo, Parsec, and RemotePC.'
keywords: 'Dameware alternative, BeyondTrust alternative, Supremo alternative, Parsec alternative, RemotePC alternative'
description: 'How RustDesk compares with Dameware, BeyondTrust/Bomgar, Supremo, Parsec, RemotePC, and HelpWire on hosting, licensing, and proof-of-concept risk.'
keywords: 'Dameware alternative, BeyondTrust alternative, Supremo alternative, Parsec alternative, RemotePC alternative, HelpWire alternative'
author: RustDesk Team
---
@@ -30,39 +30,44 @@ TeamViewer, AnyDesk, and ScreenConnect are not the only tools buyers compare wit
| Product | Typical evaluation focus | What RustDesk changes | Main proof-of-concept risk |
| -------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------------------------- |
| Dameware | Windows administration, on-premises control, SolarWinds environment | Open-source client and self-hosted ID/relay services | Administrative workflow and integration parity |
| Dameware | Windows administration, on-premises control, SolarWinds environment | Open source and self-hosted ID/relay services | Administrative workflow and integration parity |
| BeyondTrust Remote Support | Enterprise support, privileged workflows, governance | Different licensing and infrastructure model | Security, audit, approval, and integration requirements |
| Supremo | Simple attended and unattended support | Self-hosted control and centralized Pro administration | Technician workflow and deployment effort |
| Parsec | Low-latency graphics and creative work | Infrastructure ownership and general remote support | Codec, GPU, color, audio, and input performance |
| RemotePC | Cloud-based access to managed computers | Self-hosted brokering and open-source client | Remote printing, browser/mobile workflow, and server operations |
| RemotePC | Cloud-based access to managed computers | Open source and self-hosted brokering | Remote printing, browser/mobile workflow, and server operations |
| HelpWire | Proprietary cloud remote support | Open source and self-hosted ID/relay services | Pricing tiers, support workflow, and data residency |
This table describes evaluation intent, not full feature parity. Use each vendor's current documentation and test the workflows that are mandatory in your environment.
## Replacing Dameware (SolarWinds)
Dameware comparisons usually focus on open-source availability, administrative visibility, deployment platform, and total cost. Confirm the RustDesk Server Pro installation requirements before reusing existing server hardware.
Teams weighing Dameware against RustDesk usually care about open-source availability, administrative visibility, deployment platform, and total cost.
That maps closely to what RustDesk offers: a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114) showing every connected device, unattended access for fleets IT never has to babysit in person, and — because the core client is open source — the "cheaper and auditable" combination Dameware switchers are usually looking for.
That maps closely to what RustDesk offers: a [self-hosted web console](/blog/rustdesk-web-console-custom-client-generator-port-21114) showing every connected device, unattended access to fleets IT never has to babysit in person, and — because RustDesk itself is open source — the "cheaper and auditable" combination Dameware switchers are usually looking for.
## Replacing BeyondTrust (Bomgar)
BeyondTrust/Bomgar comparisons often focus on cost and consolidation. Use current written quotes and a feature-by-feature requirements list.
With BeyondTrust/Bomgar, the evaluation is usually driven by cost and consolidation, so work from current written quotes and a feature-by-feature requirements list.
RustDesk's [per login-user and per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) licensing, on infrastructure you control, is a direct answer to "the cost has gone out of control": you're not paying an escalating [enterprise](/blog/rustdesk-for-enterprise)-support contract for a cloud you don't own.
RustDesk's [per login-user and per managed-device](/blog/rustdesk-pro-license-cost-how-to-pay) licensing, on infrastructure you control, is a direct answer to runaway per-seat cost: licensing follows your own users and devices, on infrastructure you own.
## 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](https://rustdesk.com/pricing#custom2) is limited.
Supremo buyers tend to ask two questions — is it fast, and what does it cost? 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 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.
Parsec evaluations revolve around VDI, CAD, and creative workloads, where codec behavior, color, and input latency decide the outcome. Rather than inferring from someone else's benchmarks, run the RustDesk native client on your own hardware and validate real-world latency and performance before committing at scale.
## Replacing RemotePC
RemotePC comparisons typically cover price, reliability, and self-hosting. Test the exact workflows you depend on before committing.
RemotePC is per-computer cloud remote access aimed at individuals and small teams reaching a fixed set of machines, so the self-hosted contrast is direct: RustDesk moves that brokering onto a server you run, using open-source software. Test the exact workflows you depend on — remote printing, browser and mobile access, unattended reliability — before committing.
## Replacing HelpWire
HelpWire is a proprietary, cloud-hosted remote-support tool from Electronic Team, Inc., with published plans of roughly \$10–\$70/month across operator and device tiers. Evaluate it on the terms you will actually operate under. RustDesk, by contrast, is open source and lets you self-host the ID and relay services and run the [client](/blog/open-source-remote-desktop-software) on infrastructure you control.
For teams weighing HelpWire, the RustDesk community server is open source and self-hostable, and it never routes sessions through a third-party host. Confirm platform coverage and unattended-access needs against the current [pricing matrix](https://rustdesk.com/pricing) before switching.
## Use a weighted replacement scorecard
@@ -82,8 +87,6 @@ RustDesk standard plans include unlimited concurrent connections, while Customiz
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
## Test RustDesk alongside your shortlist
- **Self-host the free community server today** — open source, no cost, no expiry.
- **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.
Whichever brands make your final round, add the free community server to the bench test — open source, zero cost, and it never expires. Ask [sales@rustdesk.com](mailto:sales@rustdesk.com) about evaluation terms when you are ready to score the Pro features, and pull the current per-user and per-device rates from [rustdesk.com/pricing](https://rustdesk.com/pricing).
v3/src/content/post/en/remote-desktop-data-sovereignty-gdpr.md
+6 -6
View File
@@ -15,7 +15,7 @@ tags:
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.'
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 software 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?'
@@ -73,13 +73,13 @@ The architecture also scales with your estate: RustDesk publishes [large-fleet p
## How RustDesk fits ISO 27001, SOC 2, or HIPAA requirements
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.
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 RustDesk 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.
- Because RustDesk 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.
@@ -90,7 +90,7 @@ Self-hosting is the foundation, and on top of it RustDesk provides concrete cont
- **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.
- **Privacy mode and per-connection consent.** The controlled side can require confirmation for an incoming connection and can blacken its screen (privacy mode, supported on Windows and macOS) 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.
@@ -111,10 +111,10 @@ Self-hosting gives you choices; the deployment has to turn those choices into co
- Record the purpose, retention period, and access policy for device, account, audit, and connection metadata.
- Apply least-privilege device groups, MFA/SSO where available, and a joiner-mover-leaver process for technicians.
- Put the web console behind HTTPS, restrict administrative network access, and test backup restoration.
- Complete the appropriate legal assessment—such as records of processing, processor review, transfer assessment, and DPIA—based on your use case.
- Complete the appropriate legal assessment — such as records of processing, processor review, transfer assessment, and DPIA — based on your use case.
RustDesk can support a sovereignty architecture, but the controller remains responsible for the architecture and its legal basis.
## Try it without a sales call
## Evaluate it inside your own perimeter
You can evaluate on your own terms. Self-host the free, open-source community server today, or email [sales@rustdesk.com](mailto:sales@rustdesk.com) for current evaluation terms for the Pro features. Check current plans and exact features at [rustdesk.com/pricing](https://rustdesk.com/pricing). Prefer to watch first? There's a full [video walkthrough](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
v3/src/content/post/en/rustdesk-active-directory-ldap-sso.md
+2 -2
View File
@@ -39,13 +39,13 @@ LDAP is gated to the Basic plan and above rather than included in every paid tie
The most important operational detail is how RustDesk keys user identity. It uses the **username as the unique identifier**, not the full Distinguished Name (DN). That distinction matters in real AD environments where objects get reorganized. If you move a user between Organizational Units (OUs), their DN changes, but as long as the username stays the same their RustDesk identity remains stable and their access is unaffected. Conversely, renaming a username can create a mismatch. The practical rule: reorganize your directory freely, but treat usernames as immutable once provisioned.
One current limitation to plan around: **LDAPS with a custom PKI certificate is not yet supported**. If your security policy requires LDAP over TLS validated against your own internal certificate authority, that specific configuration is on RustDesk's feature-request list rather than shipping today. It is worth raising with the team so your use case is counted. [rustdesk.com](https://rustdesk.com)
One current limitation to plan around: **LDAPS with a custom PKI certificate is not yet supported**. If your security policy requires LDAP over TLS validated against your own internal certificate authority, that is not a documented configuration today — the console offers StartTLS and a skip-verification option (NoTLSVerify), but no field to trust your own private CA. It is worth raising with the team so your use case is counted. [rustdesk.com](https://rustdesk.com)
For setup, you point Server Pro's LDAP configuration at your directory server (bind account, base DN, user search filter) through the admin console. Because the exact fields and console layout evolve between releases, follow the current [RustDesk LDAP documentation](https://rustdesk.com/docs) rather than relying on a static screenshot.
## Who asks this
This comes up most from IT admins, [MSPs](/blog/rustdesk-for-msps), and businesses standardizing on a single identity source. If users move to another Active Directory OU and their DN changes, preserve the username used as RustDesk's unique identifier and validate synchronization in a test environment.
Directory admins — in-house or at an [MSP](/blog/rustdesk-for-msps) — wiring RustDesk into an existing Active Directory or OIDC identity source raise this while planning SSO, usually because policy forbids a second set of credentials. If users move to another Active Directory OU and their DN changes, preserve the username used as RustDesk's unique identifier and validate synchronization in a test environment.
## Related questions
v3/src/content/post/en/rustdesk-concurrent-connections-limit.md
+2 -2
View File
@@ -45,13 +45,13 @@ For current allowances and per-connection pricing on Customized V2, check [rustd
## Who asks this
This question comes up most from IT admins and [MSPs](/blog/rustdesk-for-msps) evaluating a move from tools that price simultaneous channels separately. The important step is to compare the exact RustDesk plan: standard plans and Customized V2 handle concurrency differently.
Support desks and [MSPs](/blog/rustdesk-for-msps) that have been rationing simultaneous sessions under channel-priced tools are the classic askers here. The important step is to compare the exact RustDesk plan: standard plans and Customized V2 handle concurrency differently.
## Related questions
- [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 control which users can connect to which devices?](/blog/rustdesk-per-user-access-control-device-groups-shared-address-book)
- [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)
v3/src/content/post/en/rustdesk-connected-waiting-for-image.md
+14 -15
View File
@@ -15,9 +15,9 @@ faq:
- question: 'Why does RustDesk say "Connected, waiting for image"?'
answer: "The session established successfully, but the remote machine is not producing a screen image to send. The most common reason is that there is no active display to capture — a headless server with no monitor, a screen that has gone to sleep or locked, or a display the OS won't let RustDesk record. Fix the capture source and the image appears."
- question: 'How do I fix RustDesk waiting for image on a headless computer?'
answer: 'A machine with no monitor has no framebuffer to capture, so RustDesk has nothing to send. Attach a real monitor, plug in an inexpensive HDMI dummy plug that makes the GPU think a display is connected, or on Linux use the documented headless support path. Waking or keeping the display awake resolves most cases.'
answer: 'A machine with no monitor has no framebuffer to capture, so RustDesk has nothing to send. Attach a real monitor, plug in an inexpensive HDMI dummy plug that makes the GPU think a display is connected, or on Linux use the documented headless setup (github.com/rustdesk/rustdesk/wiki/Headless-Linux-Support). Waking or keeping the display awake resolves most cases.'
- question: 'Does changing the video codec fix the black screen?'
answer: 'Often, yes. In the remote session toolbar or settings you can switch between H.264, VP8, and VP9. A codec the remote hardware cannot encode will show a blank or frozen image. On Linux the matching hardware codec library must be present for your CPU or GPU, because it is not always installed automatically.'
answer: 'Often, yes. In the remote session toolbar or settings you can switch codecs — VP8, VP9, AV1, or H.264/H.265 where hardware supports them. A codec the remote hardware cannot encode will show a blank or frozen image, and falling back to a software codec such as VP9 usually restores the picture.'
- question: 'RustDesk shows the image on one PC but not another. Why?'
answer: "That points to something local on the failing machine — an asleep or absent display, missing screen-recording permission on macOS, an outdated GPU driver, a hardware-acceleration conflict, or a codec the hardware can't handle. Work through the per-cause fixes in this guide on the machine that fails, not the one that works."
- question: 'Could my self-hosted server cause "waiting for image"?'
@@ -42,7 +42,7 @@ Three ways to give it something to capture:
- **Attach a monitor** and make sure it's powered on and awake.
- **Use an HDMI (or DisplayPort) dummy plug.** These inexpensive adapters make the GPU believe a display is connected, so it keeps rendering a framebuffer for RustDesk to grab. This is the standard fix for headless desktops and home servers.
- **On Linux, use the documented headless path.** RustDesk supports headless Linux setups, but the configuration differs from a normal desktop session — see the [Linux client documentation](https://rustdesk.com/docs/en/client/linux/).
- **On Linux, use the documented headless path.** RustDesk supports headless Linux setups, but the configuration differs from a normal desktop session — see the [Headless Linux Support wiki](https://github.com/rustdesk/rustdesk/wiki/Headless-Linux-Support).
If a monitor _is_ attached, the next suspect is that it went to sleep.
@@ -51,10 +51,10 @@ If a monitor _is_ attached, the next suspect is that it went to sleep.
| Cause | Signal | Fix |
| ------------------------------ | ----------------------------------- | ------------------------------------------------------------------------------------- |
| Headless / no display | Black screen on a server or mini-PC | Attach a monitor, add an HDMI dummy plug, or use the Linux headless path |
| Screen asleep / locked | Worked earlier, black after idle | Wake the screen; disable sleep/screensaver; on macOS keep it awake with `caffeinate` |
| Screen asleep / locked | Worked earlier, black after idle | Wake the screen; disable sleep/screensaver; on macOS stop the display sleeping in Settings |
| Missing permission (macOS) | Connects, permanent black | Grant Screen Recording in Privacy & Security; install the helper for the login screen |
| 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` |
| Codec mismatch | Blank or frozen image | Switch codec (VP8 / VP9 / AV1 / H.264 / H.265); fall back to a software codec |
| Hardware acceleration conflict | Black on specific GPUs | Turn off hardware codec in the session toolbar or Settings, or switch codec |
| Outdated GPU driver | Black after a driver/OS update | Update the GPU driver (NVIDIA especially) |
| 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 |
@@ -64,8 +64,8 @@ If a monitor _is_ attached, the next suspect is that it went to sleep.
If it worked earlier and went black after the machine sat idle, the display went to sleep.
- **Windows:** set the power plan so the display and the machine never sleep during the hours you need remote access, and disable the screensaver (or set it not to require a password mid-session).
- **macOS:** keep the display awake with the built-in `caffeinate` command over SSH, e.g. `caffeinate -u -t 3600` to simulate user activity for an hour. Community threads note this reliably wakes a dozing Mac so RustDesk can capture again ([discussion #12574](https://github.com/rustdesk/rustdesk/discussions/12574)).
- **Android:** the screen must be on to be shared. Touch the display to wake it, and on Android 9+ enable **"Disable permission monitoring"/screen-share protections in Developer options** so the OS doesn't block capture. iOS-to-Android connections to a dozing device with the screen off are a [known "waiting for image" case](https://github.com/rustdesk/rustdesk/issues/11479).
- **macOS:** stop the display from sleeping during the hours you need remote access — set it in **System Settings → Displays** (or Lock Screen / Energy settings), and keep the Mac on a power adapter, since sleep behaves differently on battery.
- **Android:** the screen must be on to be shared, so touch the display to wake it before connecting. Connecting from iOS to a dozing Android device with the screen off is a [known "waiting for image" case](https://github.com/rustdesk/rustdesk/issues/11479) — wake the target first.
### macOS permissions
@@ -73,19 +73,18 @@ macOS refuses to let any app record the screen without explicit consent. If Rust
### Video codec mismatch
RustDesk can encode the stream several ways, and the default doesn't always suit the remote hardware. In the session toolbar (or Settings), switch the codec between **H.264, VP8, and VP9** and watch for the image to appear ([discussion #12574](https://github.com/rustdesk/rustdesk/discussions/12574)). On Linux there's an extra wrinkle: hardware codecs rely on a library matched to your CPU/GPU, and it is **not always installed automatically**, so a hardware codec can silently produce nothing until the right package is present ([Linux docs](https://rustdesk.com/docs/en/client/linux/)).
RustDesk can encode the stream several ways, and the default doesn't always suit the remote hardware. In the session toolbar (or Settings), switch the codec — **VP8, VP9, AV1, or H.264/H.265 where hardware supports them** — and watch for the image to appear. If a hardware codec produces a blank image on a particular GPU, dropping back to a software codec such as VP9 is the reliable move.
### Hardware acceleration and GPU drivers
Some GPUs — NVIDIA configurations come up most often — clash with RustDesk's hardware-accelerated capture and render paths. Two levers help:
- **Disable hardware acceleration** by launching with `--hwaccel=0`, or force software rendering with `--render=software`.
- **On Windows, try the DirectX path** with `--render=d3d`, which lets the OS grab the screen more dependably on some setups.
- **Update the GPU driver.** A black screen that started after a driver or OS update is frequently fixed by moving to a current driver, particularly on NVIDIA hardware ([discussion #12574](https://github.com/rustdesk/rustdesk/discussions/12574)).
- **Turn off the hardware codec.** In the session toolbar (or Settings), disable **Use hardware codec** so encoding falls back to a software path — this clears the black screen on many problem GPUs.
- **Update the GPU driver.** A black screen that started after a driver or OS update is frequently fixed by moving to a current driver, particularly on NVIDIA hardware.
### Linux and Wayland
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.
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 [headless configuration](https://github.com/rustdesk/rustdesk/wiki/Headless-Linux-Support). 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.
### Network and relay
@@ -97,8 +96,8 @@ Old builds carry old capture bugs. Update **both** the controlling client and th
## The open-source advantage
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.
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.
## Fewer variables when the server is yours
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.
Run [your own relay and ID server](/blog/why-self-host-remote-desktop-software), 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.
v3/src/content/post/en/rustdesk-custom-quote-minimum-users-invoice-fees.md
+10 -6
View File
@@ -15,12 +15,12 @@ author: RustDesk Team
faq:
- question: 'How do I get a custom RustDesk Pro quote?'
answer: 'RustDesk publishes Basic, Customized, and Customized V2 self-hosting plans. Size a quote by login users and managed devices, plus concurrent connections for Customized V2. For invoice, bank transfer, taxes, or billing workflow, confirm the current terms on the pricing page or with sales.'
- question: 'Does RustDesk license per user or per device?'
- question: 'Which counts does a custom quote size on — users, devices, or both?'
answer: 'Both. A Customized quote scales along login-user and managed-device counts, and Customized V2 adds a defined number of concurrent connections as a third input. See rustdesk.com/pricing for current allowances.'
- question: 'What is the difference between the Basic and Customized self-hosted Pro plans?'
answer: 'Basic includes fixed login-user and managed-device allowances. Customized starts from the Basic feature set and adds separately priced users and devices, while Customized V2 also lets you select a limited number of concurrent connections.'
- 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.'
answer: 'RustDesk does not publish a fixed minimum on the pricing page. 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: '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)?'
@@ -43,20 +43,24 @@ Choose capacity for both login users and managed devices. If you use Customized
Because Customized licensing scales along login-user and managed-device counts, there is no single total for every organization. Customized V2 adds a third input: concurrent connections.
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.
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 for current figures.
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).
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). One thing buyers often ask about: aside from the bank-transfer processing fee noted above, there are no hidden fees beyond the displayed plan cost.
Billing is **annual** — there is no monthly option and no auto-renewal, though RustDesk emails a renewal reminder 14 days before expiry, and multi-year terms can be arranged through [sales@rustdesk.com](mailto:sales@rustdesk.com). 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.
## Who asks this
This comes up most often with IT admins, MSPs, and businesses evaluating RustDesk against tools like TeamViewer or AnyDesk, where per-seat pricing can climb quickly at scale. These buyers typically know their headcount and endpoint counts and want a concrete, volume-based number they can take to finance — which is exactly what the custom-quote process is built to deliver.
Procurement-minded buyers drive this question: an MSP pricing a multi-client rollout, or an internal IT lead sizing capacity beyond the fixed Basic allowances. These buyers typically know their headcount and endpoint counts and want a concrete number they can take to finance — which is exactly what the custom-quote process is built to deliver.
## Related questions
- [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)
- [How does concurrency work across the different plans?](/blog/rustdesk-concurrent-connections-limit)
- [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)
v3/src/content/post/en/rustdesk-for-enterprise.md
+5 -5
View File
@@ -14,7 +14,7 @@ tags:
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.'
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 (Basic plan and up) 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?'
@@ -28,7 +28,7 @@ metadata:
keywords: 'RustDesk for enterprise, RustDesk enterprise deployment, AD-integrated remote support, enterprise RustDesk architecture'
---
## RustDesk for enterprise: keep your remote access on your own infrastructure
## Keep remote access on infrastructure you control
Enterprise evaluations usually focus on infrastructure control, identity, access policy, auditability, scale, and licensing predictability. Those requirements can be compared directly against public product capabilities and documentation.
@@ -68,7 +68,7 @@ Operational monitoring must include unexpected registrations. If a new device ap
| Identity integration | LDAP/SSO (OIDC), available from the Basic plan and up ([see rustdesk.com/pricing](https://rustdesk.com/pricing)) |
| Scale planning | Large-fleet guidance is available; validate capacity against your rollout design and operating model. |
| Source availability | Core is open source (AGPL) — auditable and self-buildable. |
| Evaluation | Free community server today, or email sales@rustdesk.com for a Pro trial (or watch a [video walkthrough](https://www.youtube.com/@rustdesk) first). |
| Evaluation | Free community server today, or email sales@rustdesk.com to ask about current evaluation terms (or watch a [video walkthrough](https://www.youtube.com/@rustdesk) first). |
## Data control and compliance
@@ -106,7 +106,7 @@ At scale the case sharpens: the ID/relay, console, and stored data live inside y
You can evaluate **[without a sales call](/blog/see-rustdesk-in-action)**. Two paths:
- **Self-host the free, open-source community server today.** It's yours to run indefinitely — good for validating the architecture on your own network.
- **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.
- **Validate the architecture with the free, open-source community server.** It runs indefinitely on your own network — a low-stakes way to prove the self-hosted model to your security team.
- **For the Pro capabilities — identity, access control, client generation —** review current plans at [rustdesk.com/pricing](https://rustdesk.com/pricing), then email [sales@rustdesk.com](mailto:sales@rustdesk.com) for the evaluation terms available to your organization.
Either way, stand up a server against your own environment and validate it before you commit.
v3/src/content/post/en/rustdesk-for-linux.md
+4 -4
View File
@@ -22,7 +22,7 @@ faq:
- 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:
description: 'Install and run RustDesk on Linux: .deb, .rpm, Flatpak and AppImage, X11 vs Wayland, headless and unattended access, and self-hosting the server.'
description: 'RustDesk on Linux, end to end: package choices for every distro and ARM board, Wayland and X11 capture, headless setup, and running your own server.'
keywords: 'RustDesk for Linux, RustDesk Ubuntu, RustDesk Wayland, RustDesk X11, RustDesk Linux install'
---
@@ -44,7 +44,7 @@ RustDesk ships packages for every common Linux packaging format, so you rarely h
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, 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.
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.
## X11 vs Wayland: the part that matters
@@ -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. 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.
3. For access before or across user logins, use the headless virtual-display configuration below (the Wayland greeter gap covered above applies here).
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.
One Wayland reality to plan for: the consent-based portal described in the Wayland section makes fully unattended capture harder than on X11 until the in-development unattended support lands, so plan on the headless virtual-display setup for hands-off machines.
## Headless Linux: servers with no monitor
v3/src/content/post/en/rustdesk-for-mac.md
+2 -2
View File
@@ -21,7 +21,7 @@ faq:
- question: 'Can RustDesk transfer files to and from a Mac?'
answer: 'Yes. RustDesk supports two-way file transfer between the local and remote machine, including to and from macOS, alongside remote view and control. Granting Full Disk Access can help RustDesk reach protected locations.'
metadata:
description: 'Install RustDesk on Apple Silicon or Intel Macs, grant the right macOS permissions, set up unattended access and file transfer, and connect to your own server.'
description: 'RustDesk on macOS: pick the right build for your chip, fix the black-screen permission quirk, enable unattended access, and point it at your own server.'
keywords: 'RustDesk for Mac, RustDesk macOS, RustDesk Apple Silicon, RustDesk mac permissions, RustDesk screen recording accessibility, RustDesk mac unattended access, RustDesk mac install'
---
@@ -65,7 +65,7 @@ Unattended access lets you connect to a Mac when nobody's there to click "accept
1. Open RustDesk and click **Install** to register it as a background service (this is what lets it accept connections without a logged-in user clicking through).
2. Set a strong **permanent password** in the connection settings, and enable **two-factor authentication** if you want the extra layer.
3. Confirm RustDesk is set to **start at boot**, and that Screen Recording plus Accessibility are granted — without them the service runs but control silently fails.
3. Confirm the RustDesk **service is installed and running** — once installed it starts at boot via its LaunchDaemon — and that Screen Recording plus Accessibility are granted; without them the service runs but control silently fails.
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.
v3/src/content/post/en/rustdesk-for-msps.md
+9 -13
View File
@@ -31,23 +31,19 @@ metadata:
Most MSPs are not looking for another remote-support tool. They are looking for _fewer_ of them.
MSPs often evaluate consolidation when multiple remote-support tools create separate consoles, contracts, and operating procedures. Build the comparison from current contracts and technical requirements.
This is a guide to **RustDesk for MSPs**: how one self-hosted, open-source, brandable tool can replace that pile — and, just as important, where the trade-offs are.
## Why consolidation keeps stalling
The reason MSPs run three tools is rarely preference. It is that each vendor's pricing and limits push you toward a workaround.
The recurring decision factors are price, security, hosting control, and workflow consolidation. Public disclosures and current vendor documentation provide a reliable basis for comparison.
Different vendors, same three complaints: cost that climbs, licensing that limits how you work, and control you never actually had.
So the stack accretes — a cloud remote-support seat here, a per-technician tool there, a standalone quick-support utility for one-off jobs. Different vendors, same three complaints: cost that climbs, licensing that limits how you work, and control you never actually had.
## The core difference: you host it, you own it
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 the relay you operate.
The client core is **[open source (AGPL)](/blog/case-for-open-source-remote-access)**. You can read the code, audit exactly what it does on a customer's machine, build it yourself, and run the free community server indefinitely. For an MSP that has to answer "what is this agent doing on our endpoints?" during a security review, that is a materially different conversation than pointing at a closed binary.
RustDesk is **[open source (AGPL)](/blog/case-for-open-source-remote-access)**. You can read the code, audit exactly what it does on a customer's machine, build it yourself, and run the free community server indefinitely. For an MSP that has to answer "what is this agent doing on our endpoints?" during a security review, that is a materially different conversation than pointing at a closed binary.
Here is how that maps against the tools MSPs commonly consolidate away from:
@@ -58,7 +54,7 @@ Here is how that maps against the tools MSPs commonly consolidate away from:
| 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 |
| Branding | Add-on or unavailable | Custom-branded client generator (Basic plan and up) |
For exact plan tiers and current prices, see [rustdesk.com/pricing](https://rustdesk.com/pricing).
@@ -72,7 +68,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 available from the Basic plan and up, so verify the current matrix before relying on them.
The branded client matters because your clients see your brand on the tool they install, not a vendor's. Access control can scope technicians to assigned device groups. Verify the current plan matrix before relying on these features.
## Control over server-side data location
@@ -84,14 +80,14 @@ It also scales beyond proof-of-concept. RustDesk publishes large-fleet planning
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
## Put it to the test on your own terms
You can evaluate RustDesk today with no meeting booked:
- **Self-host the free community server** — open source, run it indefinitely, no time limit.
- **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?** [See RustDesk in action](/blog/see-rustdesk-in-action), or head to the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk) — no booking required.
- **Stand up the free community server on a spare VM.** It is open source and never expires, so you can validate a real client workflow before spending anything.
- **When branding and access control enter the picture,** compare tiers at [rustdesk.com/pricing](https://rustdesk.com/pricing) and ask [sales@rustdesk.com](mailto:sales@rustdesk.com) what evaluation terms currently apply.
- **Short on lab time?** [See RustDesk in action](/blog/see-rustdesk-in-action) first, or browse the walkthroughs on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
Licensing is per login-user + per managed-device, and you can **[upgrade any time](/blog/upgrade-rustdesk-license-mid-subscription) (prorated)** — no per-channel model, no per-seat cloud subscription stacked on top. Start at [rustdesk.com/pricing](https://rustdesk.com/pricing).
You can **[upgrade any time](/blog/upgrade-rustdesk-license-mid-subscription) (prorated)** as your client base grows — start at [rustdesk.com/pricing](https://rustdesk.com/pricing).
If you are running several remote-support tools today, spin up the community server on a test VM and validate a representative client session before planning migration.
v3/src/content/post/en/rustdesk-lifetime-perpetual-license.md
+4 -4
View File
@@ -16,11 +16,11 @@ 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: '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.'
answer: 'Yes. Multi-year terms are available — contact sales@rustdesk.com to arrange one. Confirm the available term, per-year rate, renewal date, and cancellation or transfer 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: "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."
description: "Does RustDesk offer a lifetime license? No — pricing is term-based, with annual and multi-year terms available (multi-year arranged through sales)."
keywords: 'RustDesk lifetime license, RustDesk perpetual license, RustDesk multi-year license, RustDesk license term'
---
@@ -28,7 +28,7 @@ RustDesk's public Server Pro pricing is term-based and does not include a lifeti
## Lifetime and multi-year are not the same
A lifetime license is a one-time payment for indefinite use. A multi-year purchase still ends on a defined date and may have specific renewal, refund, transfer, or capacity-change conditions. Do not describe a long prepaid term as perpetual.
A lifetime license is a one-time payment for indefinite use. A multi-year purchase still ends on a defined date and may have specific renewal, refund, transfer, or capacity-change conditions. Budget a long prepaid term as term-based, not perpetual.
The open-source components are separate from Server Pro. You can run the community ID and relay server under its open-source license; the commercial Server Pro features require the applicable license term.
@@ -42,7 +42,7 @@ Use the current [pricing page](https://rustdesk.com/pricing) for standard annual
- 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.
- renewal, cancellation, and transfer conditions.
Budget Server Pro as a recurring software line unless the signed terms state otherwise. A long term can reduce procurement work, but it also reduces flexibility if requirements change.
v3/src/content/post/en/rustdesk-not-connecting-troubleshooting.md
+4 -4
View File
@@ -41,7 +41,7 @@ A session that never connects almost always comes down to one of three things: t
| Symptom | Most likely layer | First check |
| ----------------------------------------------- | ------------------------------------------ | -------------------------------------------------------------------------------------- |
| Client shows “Not ready” or cannot obtain an ID | ID server or DNS reachability | Resolve the server name and test TCP/UDP 21116 from that client network |
| “Key mismatch” or “invalid public key” | Client/server configuration | Compare the client key with the server's current `id_ed25519.pub` |
| “Key Mismatch” or “invalid public key” | Client/server configuration | Compare the client key with the server's current `id_ed25519.pub` |
| Peer is found but the session times out | Firewall, NAT, or relay path | Test TCP 21117 and review cloud security groups, host firewall, and NAT rules |
| Direct connection fails but forced relay works | NAT traversal | Check UDP 21116 and accept relay for symmetric NAT or restrictive networks |
| Both direct and relay fail | Server address, key, or relay availability | Confirm both peers use the same ID server and inspect `hbbs`/`hbbr` logs |
@@ -91,17 +91,17 @@ Open only what your deployment uses: **TCP 21115-21117 and UDP 21116** are the c
## Step 4: Understand direct vs. relayed connections
RustDesk tries a **direct peer-to-peer** connection first, using the ID server to coordinate NAT hole punching. When both peers sit behind cooperative NATs, you get a fast direct link. When hole punching fails—symmetric NAT, strict corporate firewalls, carrier-grade NAT—traffic **falls back to the relay** when that path is reachable, usually with extra latency ([self-hosting architecture](https://rustdesk.com/docs/en/self-host/)).
RustDesk tries a **direct peer-to-peer** connection first, using the ID server to coordinate NAT hole punching. When both peers sit behind cooperative NATs, you get a fast direct link. When hole punching fails — symmetric NAT, strict corporate firewalls, carrier-grade NAT — traffic **falls back to the relay** when that path is reachable, usually with extra latency ([self-hosting architecture](https://rustdesk.com/docs/en/self-host/)).
If direct connections are flaky, you can **force relay mode** to make sessions more deterministic. That trades a little latency for reliability — and it makes relay capacity matter, which is the next point.
Direct IP access is also available for LAN or port-forwarded scenarios: you can enter a target's IP directly to bypass the ID server, though you then lose automatic NAT traversal and relay failover, so both ends must be reachable on the network you configure.
Direct IP access is also available for LAN or port-forwarded scenarios: enable **Direct IP access** on the controlled device first, then enter its IP to bypass the ID server — though you then lose automatic NAT traversal and relay failover, so both ends must be reachable on the network you configure.
## Step 5: Stop fighting the public server
The public rendezvous and relay are shared infrastructure and are not a substitute for a capacity plan or service commitment. If connections are unreliable and the client, network, and endpoint checks above pass, compare the result with a self-hosted test server before attributing the failure to the public service.
The durable fix is to **self-host**. Running your own server on a small VPS or a local machine gives you dedicated capacity, a stable key you control, and no dependence on someone else's uptime. The **free community server runs indefinitely** at no cost, and you don't need a container runtime to do it — see [running the server without Docker](/blog/rustdesk-server-pro-without-docker). Because the [client is open source](/blog/open-source-remote-desktop-software) and the server is yours, there's no black-box vendor deciding whether your session goes through.
The durable fix is to **self-host**. Running your own server on a small VPS or a local machine gives you dedicated capacity, a stable key you control, and no dependence on someone else's uptime. The **free community server runs indefinitely** at no cost, and you don't need a container runtime to do it — see [running the server without Docker](/blog/rustdesk-server-pro-without-docker). Because [RustDesk is open source](/blog/open-source-remote-desktop-software) and the server is yours, there's no black-box vendor deciding whether your session goes through.
## Step 6: Update everything
v3/src/content/post/en/rustdesk-per-user-access-control-device-groups-shared-address-book.md
+2 -2
View File
@@ -75,7 +75,7 @@ When the work ends, disable the contractor user in the console. RustDesk documen
## Who asks this
This comes up most from IT admins, [MSPs](/blog/rustdesk-for-msps), and businesses that need to give a contractor, vendor, or auditor access to one machine without authorizing access to the rest of the environment.
The scenario behind this question is almost always a scoped outsider: an [MSP](/blog/rustdesk-for-msps) or internal IT team needs to give a contractor, vendor, or auditor access to one machine without authorizing access to the rest of the environment.
## Related questions
@@ -83,6 +83,6 @@ This comes up most from IT admins, [MSPs](/blog/rustdesk-for-msps), and business
- [What are device groups and cross-group access rules?](/blog/enhanced-acl-in-rustdesk-server-pro-1-5-0)
- [How do I create and later disable a temporary user account for external access?](/blog/rustdesk-for-enterprise)
- [How does RustDesk handle per-device passwords and controlled-device 2FA?](/blog/rustdesk-unattended-access-setup)
- [Does per-user access control require RustDesk Server Pro or a self-hosted server?](/blog/rustdesk-for-enterprise)
- [Does per-user access control require RustDesk Server Pro or a self-hosted server?](/blog/rustdesk-self-hosted-vs-cloud-saas-option)
Need to give an outside contractor access to one machine? Configure Access Control with a dedicated account, test both the allow and deny paths, and disable the account when the work is done.
v3/src/content/post/en/rustdesk-pro-license-cost-how-to-pay.md
+6 -6
View File
@@ -16,16 +16,16 @@ faq:
- question: 'How much does RustDesk Pro cost?'
answer: 'A RustDesk Pro license is priced by the number of users and devices you need, so there is no single flat number — check rustdesk.com/pricing. Use the current pricing page for plan details, checkout options, and evaluation terms.'
- question: 'Is the RustDesk client free, and what does Pro add?'
answer: 'Yes. The RustDesk client is open source and free, and you can self-host the basic relay and signal server at no license cost. A Pro license unlocks the Server Pro feature set — the management, control, and scale features aimed at businesses.'
answer: 'Yes. RustDesk is open source and free, and you can self-host the basic relay and signal server at no license cost. A Pro license unlocks the Server Pro feature set — the management, control, and scale features aimed at businesses.'
- question: 'Does RustDesk license per user or per device?'
answer: 'Both. Pricing is tied to how many login users need seats and how many managed devices you connect to, so your total reflects your own configuration. See rustdesk.com/pricing for current figures.'
- question: 'Do you offer volume or annual pricing for MSPs and larger teams?'
answer: 'Because pricing scales with your user and device counts, larger deployments are quoted per configuration rather than a fixed sticker. For volume or annual terms, check rustdesk.com/pricing or email sales@rustdesk.com.'
answer: 'Because pricing scales with your user and device counts, larger deployments are quoted per configuration rather than a fixed sticker. For larger deployments or annual terms, check rustdesk.com/pricing or email sales@rustdesk.com.'
- question: 'What are the current evaluation terms for RustDesk Server Pro?'
answer: 'Evaluation terms are not fixed in this article. Check the current evaluation path on rustdesk.com/pricing, or email sales@rustdesk.com to confirm what is available for your setup.'
answer: 'Evaluation terms are set by the RustDesk team and can change. Check the current path on rustdesk.com/pricing, or email sales@rustdesk.com to confirm what is available for your setup.'
metadata:
description: 'How much does RustDesk Pro cost? Pricing scales with users and devices, with current plans and checkout options listed on rustdesk.com/pricing.'
description: 'RustDesk Pro pricing explained: per-user and per-device licensing, what the license covers, and where to buy — with evaluation and billing pointers.'
keywords: 'RustDesk Pro cost, RustDesk Pro price, RustDesk license cost, how to buy RustDesk license, RustDesk pricing per user and device, RustDesk Server Pro pricing'
---
@@ -43,11 +43,11 @@ If you want to evaluate the paid features before committing, check the current e
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.
It is also worth remembering the free/paid split. RustDesk 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 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.
Budget owners — and the admins preparing numbers for them — land on this question when an evaluation turns into a purchase request. 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
v3/src/content/post/en/rustdesk-remote-control-android-ios.md
+5 -5
View File
@@ -4,7 +4,7 @@ lang: en
translationKey: rustdesk-remote-control-android-ios
draft: false
title: 'RustDesk Android & iOS Remote Control: What Works'
excerpt: 'How RustDesk remote-controls Android phones, uses mobile apps as controllers, and the honest truth about controlling an iPhone or iPad.'
excerpt: 'How RustDesk remote-controls Android phones, turns iPhones and iPads into controllers, and why no vendor can remote-control iOS.'
image: ~/assets/images/blog/rustdesk-remote-control-android-ios-og.png
category: Guides
tags:
@@ -23,7 +23,7 @@ faq:
- question: 'Can I leave an Android device set up for unattended control?'
answer: 'Partially. RustDesk can keep its capture service alive with a foreground notification and restart it on boot, but the screen-capture consent, a blocked lock-screen keyboard, and needing to unlock manually after a reboot make truly unattended Android control unreliable. Treat Android control as attended support rather than set-and-forget access.'
metadata:
description: 'How RustDesk remote-controls Android phones, uses mobile apps as controllers, and the honest truth about controlling an iPhone or iPad.'
description: 'RustDesk on Android and iOS: control Android remotely, use either mobile app to drive your desktops, and what Apple permits on iPhone and iPad.'
keywords: 'RustDesk Android iOS remote control, remote control phone with RustDesk, RustDesk Android host, control Android remotely, RustDesk iOS, control iPhone remotely, RustDesk mobile app'
---
@@ -59,7 +59,7 @@ This is where RustDesk does something most remote tools can't: it can turn an An
**Staying alive.** RustDesk keeps a foreground-service notification and, optionally, a floating overlay window so Android doesn't kill the capture process, and it can restart the service on boot.
Now the honest limitations, because Android's security model imposes real ones:
Now the limitations, because Android's security model imposes real ones:
- **Consent is required to start capture.** Someone (or a pre-approval) has to accept the screen-recording prompt.
- **The lock screen blocks input.** Android does not let an accessibility service type into the secure lock screen, so if the device locks you generally can't enter the unlock code remotely — a limitation [documented by hands-on users](https://blog.wirelessmoves.com/2025/10/remote-android-support-with-rustdesk-part-1.html).
@@ -68,11 +68,11 @@ Now the honest limitations, because Android's security model imposes real ones:
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
## Controlling an iOS device: what Apple allows
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.
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 that is app-initiated broadcasting, not something a remote party can pull — so third-party remote viewing of iOS remains unavailable, and full remote control of iOS from another device isn't something the OS permits to third parties.
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.
v3/src/content/post/en/rustdesk-reseller-partner-program.md
+4 -4
View File
@@ -16,14 +16,14 @@ faq:
- question: 'Can I resell RustDesk licenses or get a partner discount?'
answer: 'The public pricing page does not describe a formal reseller tier or discount. Ask RustDesk to confirm current partner terms, whether an MSP can purchase for a client, and who owns the account and renewal before quoting.'
- question: 'Does RustDesk offer volume or bulk discounts for large orders?'
answer: 'No public bulk-discount schedule is stated here. Size login users, managed devices, and any plan-specific concurrency, then request written terms for a large order.'
answer: 'RustDesk does not publish a bulk-discount schedule. Size login users, managed devices, and any plan-specific concurrency, then request written terms for a large order.'
- question: 'Does RustDesk integrate with WHMCS or other billing platforms?'
answer: 'Public pricing does not document WHMCS integration, deal registration, or automated reseller provisioning. If those are required, confirm current support and API options directly before designing the workflow.'
- question: 'Who should own the RustDesk license, the MSP or the client?'
answer: 'Decide before purchase. If a client will eventually control renewals or hold the license under their own account, confirm that account-ownership and renewal workflow up front so the billing path matches your service model.'
metadata:
description: "RustDesk's public pricing does not describe a formal reseller program. Confirm partner, account-ownership, and renewal terms before quoting clients."
description: "Reselling RustDesk to clients? No formal partner tier is published — get written confirmation on discounts, account ownership, and renewals first."
keywords: 'RustDesk reseller program, RustDesk partner program, RustDesk reseller discount, buy RustDesk on behalf of clients, RustDesk for MSPs, resell RustDesk licenses'
---
@@ -45,13 +45,13 @@ A practical note on pricing: build the proposal around services you can deliver
## Who asks this
This question comes mostly from MSPs, IT service providers, and regional distributors that want to standardize deployments across clients. They need a documented answer about channel contracts, discounts, deal registration, account ownership, support, and renewals; public silence is not a substitute for those terms.
Channel businesses raise this — MSPs, IT service providers, and regional distributors that want to standardize deployments across their client base. They need a documented answer about channel contracts, discounts, deal registration, account ownership, support, and renewals; public silence is not a substitute for those terms.
## Related questions
- [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?](/blog/upgrade-rustdesk-license-mid-subscription)
- [How do license renewals and the self-service portal work?](/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)
v3/src/content/post/en/rustdesk-scale-50000-200000-devices.md
+2 -2
View File
@@ -18,7 +18,7 @@ faq:
- question: 'What has to be tuned to reach 200,000 devices?'
answer: 'Validate online-device churn, simultaneous remote sessions, relay bandwidth, caching, database write performance, and management-console activity against your own workload. The public-server result demonstrates endpoint-presence scale; it does not reproduce every Server Pro workload.'
- question: 'Does RustDesk Server Pro support high availability or load balancing?'
answer: 'For very large fleets, high availability and load balancing are worth designing in, but the specifics such as relay redundancy, database failover, and how sessions are distributed should be validated with RustDesk against your workload rather than assumed as out-of-the-box defaults.'
answer: 'The architecture supports scaling out — deployments can run multiple relays and place them regionally — but high availability is a design exercise rather than an out-of-the-box default: validate relay redundancy, database failover, and session distribution with RustDesk against your workload.'
- question: 'Is public RustDesk infrastructure sized the same as a self-hosted deployment?'
answer: 'Not necessarily. The public-server figure measures online endpoints, not two million simultaneous remote-control sessions. A self-hosted Server Pro deployment can add different database, console, policy, audit, and relay loads, so reproduce your expected concurrency and traffic profile before final sizing.'
@@ -51,7 +51,7 @@ For planning purposes, use the public server's more than two million online endp
## Who asks this
This question typically comes from enterprises, [MSPs](/blog/rustdesk-for-msps), and public-sector IT teams planning multi-year rollouts. These buyers are usually leaving a commercial tool for cost or data-sovereignty reasons and need confidence that a self-hosted platform will grow with them rather than hit a wall mid-contract.
Fleet architects planning multi-year rollouts — at enterprises, large [MSPs](/blog/rustdesk-for-msps), and public-sector IT programs — put this near the top of their diligence list. These buyers are usually leaving a commercial tool for cost or data-sovereignty reasons and need confidence that a self-hosted platform will grow with them rather than hit a wall mid-contract.
## Related questions
v3/src/content/post/en/rustdesk-self-hosted-vs-cloud-saas-option.md
+7 -7
View File
@@ -18,12 +18,12 @@ faq:
- 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; 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.'
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, and a shared address book; the custom branded client generator and identity features such as LDAP/AD and OIDC SSO are available from the Basic plan and up.'
- question: 'Does RustDesk offer a monthly Server Pro plan?'
answer: 'RustDesk Server Pro licenses are sold annually rather than month to month. Self-hosting and billing cadence are separate: you operate the server on infrastructure you control, while the commercial license is renewed yearly. Check the pricing page for current terms.'
metadata:
description: "Does RustDesk offer a cloud or SaaS option? No. RustDesk Server Pro is self-hosted only — you deploy it on your own infrastructure. Here's what that means."
description: "RustDesk has no hosted SaaS tier: Server Pro runs on infrastructure you control, on-prem or cloud VM. What self-hosting covers and how billing works."
keywords: 'does RustDesk host the server, RustDesk self-hosted vs cloud, RustDesk monthly plan, RustDesk SaaS option'
---
@@ -31,15 +31,15 @@ No — RustDesk does not host the server for you. RustDesk Server Pro is a self-
## The short answer
RustDesk Server Pro is self-hosted. There is no managed cloud or SaaS tier where RustDesk operates the server on your behalf. If you buy Server Pro, you are responsible for deploying it on your own server — whether that's an on-premises machine or a cloud VM (like a VPS, AWS, Azure, or GCP instance) that you provision and administer yourself.
"Self-hosted" fixes the division of labor: RustDesk supplies the server software and the license; you supply the host — an on-premises machine or a cloud VM (a VPS, AWS, Azure, or GCP instance) you provision and administer — and you operate the ID/rendezvous service, the relay, and the web console on it. There is no tier where RustDesk takes over that operating role for you.
## In detail
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 — 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.
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 is yours, and the hardware requirements are low.
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.
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 — mostly one-time setup, then light ongoing patching — 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,12 +51,12 @@ 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 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.
Shoppers arriving from SaaS remote-desktop products — IT admins and [MSPs](/blog/rustdesk-for-msps) alike — raise this early, often right 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
- [What do I need to deploy RustDesk Server Pro on my own server?](/blog/self-host-rustdesk-server-hardware-at-scale)
- [How is RustDesk licensing structured — per user versus per device?](/blog/rustdesk-pro-license-cost-how-to-pay)
- [How is RustDesk licensing structured — per user versus per device?](/blog/what-counts-as-a-managed-device)
- [Does self-hosting RustDesk keep my session data on my own infrastructure?](/blog/remote-desktop-data-sovereignty-gdpr)
- [How much does Server Pro cost, and how do I buy it?](/blog/rustdesk-pro-license-cost-how-to-pay)
v3/src/content/post/en/rustdesk-server-pro-free-trial.md
+7 -9
View File
@@ -13,16 +13,16 @@ tags:
author: RustDesk Team
faq:
- question: 'Does RustDesk Server Pro have a free trial?'
answer: 'The public pricing page asks prospective buyers to contact RustDesk for current trial-license availability and terms. Do not assume a fixed duration, price, or feature set until sales confirms it in writing.'
answer: 'There is no self-serve free trial. Email sales@rustdesk.com for the current evaluation options, and do not assume a fixed duration, price, or feature set until sales confirms it in writing.'
- question: 'How can I evaluate RustDesk Server Pro?'
answer: 'Email sales@rustdesk.com to confirm the current evaluation path, duration, and included features in writing before you plan your proof of concept. Scope the pilot around the workflows you care about, such as custom branding, if you need to validate them.'
- question: 'Why are trial terms not listed in this article?'
answer: 'Evaluation availability, duration, price, and included features can change. This article avoids inventing a fixed policy and directs buyers to the current pricing page or written confirmation from RustDesk.'
- question: "What are RustDesk's current evaluation terms?"
answer: 'Evaluation terms are set by the RustDesk sales team and change over time, so there is no fixed public policy to quote. Email sales@rustdesk.com for the current availability, duration, price, and included features, and do not assume a fixed duration or feature set until sales confirms it in writing.'
- question: 'What happens to my server and connections when a test license expires?'
answer: 'This article does not specify what happens at expiry, and you should not assume connections keep working. Confirm the exact end-of-trial behavior for your server and active sessions with sales@rustdesk.com before you rely on a test license in production.'
answer: 'Do not assume connections keep working after a test license expires — confirm expiry behavior with sales before your pilot. Ask sales@rustdesk.com exactly what happens to your server and active sessions at the end of the evaluation window before you rely on a test license in production.'
metadata:
description: 'RustDesk Server Pro does not publish a fixed free trial. Email sales@rustdesk.com to ask about current evaluation terms.'
description: 'Is there a RustDesk Server Pro free trial? No fixed public trial — evaluation terms come from the sales team and change; confirm them in writing first.'
keywords: 'RustDesk free trial, RustDesk Server Pro trial, RustDesk test license, evaluate RustDesk Server Pro, RustDesk trial license'
---
@@ -36,15 +36,13 @@ Email [sales@rustdesk.com](mailto:sales@rustdesk.com) for current trial-license
RustDesk Server Pro is a self-hosted platform, meaning you run the server on your own infrastructure. The public pricing page does not publish a fixed self-serve trial policy, and this article does not speculate about the reason.
For genuine evaluators, the practical takeaway is simple: confirm the current evaluation path, duration, and included features in writing before you plan your proof of concept. Do not assume a fixed number of days, a specific price, or custom-client availability unless the current offer says so.
If custom branding or a preconfigured client is part of what you need to validate — common for [MSPs](/blog/rustdesk-for-msps) and businesses rolling RustDesk out to end users — ask whether your evaluation can include those workflows. That way you test something representative of what you'd actually run in production.
The practical takeaway: scope your proof of concept around the workflows you actually care about, then confirm the current evaluation terms before you start.
For genuine evaluators, the practical takeaway is simple: scope your proof of concept around the workflows you actually care about, then confirm the current evaluation path, duration, and included features in writing before you start — and do not assume a fixed number of days, a specific price, or custom-client availability unless the current offer says so.
## Who asks this
This question comes overwhelmingly from IT admins, MSPs, and businesses evaluating remote-desktop tools — often teams migrating away from TeamViewer or AnyDesk who want to pilot a self-hosted alternative before signing off. The people asking generally want a low-risk way to prove the platform works in their environment before purchasing an annual license.
Pilot planners ask this one first — the team assigned to stand up a proof of concept and report back before any budget is signed off. The people asking generally want a low-risk way to prove the platform works in their environment before purchasing an annual license.
## Related questions
v3/src/content/post/en/rustdesk-server-pro-offline-air-gapped.md
+1 -1
View File
@@ -44,7 +44,7 @@ For a strictly air-gapped network, this is the deciding detail. A truly isolated
## Who asks this
This question comes up repeatedly from IT admins, [MSPs](/blog/rustdesk-for-msps), and security teams standing up RustDesk in locked-down or regulated environments, often while migrating away from cloud-dependent tools like TeamViewer or AnyDesk. Their networks may sit behind strict egress firewalls, or they simply want to minimize external dependencies. Knowing that the license needs an ongoing outbound path — but only that — lets them write a precise firewall rule rather than either over-opening the network or wrongly assuming the product will run in a total vacuum.
Operators of isolated or regulated networks ask this before RustDesk is even installed — security teams and [MSPs](/blog/rustdesk-for-msps) serving locked-down environments alike. Their networks may sit behind strict egress firewalls, or they simply want to minimize external dependencies. Knowing that the license needs an ongoing outbound path — but only that — lets them write a precise firewall rule rather than either over-opening the network or wrongly assuming the product will run in a total vacuum.
## Related questions
v3/src/content/post/en/rustdesk-server-pro-without-docker.md
+4 -4
View File
@@ -13,17 +13,17 @@ tags:
- self-hosting
author: RustDesk Team
faq:
- question: 'Can I run RustDesk Server Pro without Docker?'
- question: 'Do I need Docker to run RustDesk Server Pro?'
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.'
answer: 'Only the hbbs ID server carries the license — the hbbr relay does not — and it binds to one machine at a time. 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."
description: "Run RustDesk Server Pro straight on a VM or bare metal with install.sh — no container runtime needed; keep one outbound HTTPS path for license activation."
keywords: 'RustDesk Server Pro without Docker, install RustDesk Server Pro on a VM, RustDesk Server Pro offline install, RustDesk Server Pro bare metal, RustDesk license activation offline, RustDesk Server Pro Debian'
---
@@ -47,7 +47,7 @@ So the honest summary for an IT admin is: install however you like, on whatever
## Who asks this
This comes up constantly with IT admins and [MSPs](/blog/rustdesk-for-msps) standardizing on their own stack — teams that already manage VMs, hypervisors, or bare-metal hosts and do not want to add a container layer just to run one service. It is especially common among businesses migrating off TeamViewer or AnyDesk who want a self-hosted server on infrastructure they already control, and among security-conscious shops probing whether a fully offline deployment is possible before they commit.
Sysadmins and [MSP](/blog/rustdesk-for-msps) engineers with an established VM, hypervisor, or bare-metal estate ask this because they see no reason to add a container layer just to run one more service. It is especially common among businesses migrating off TeamViewer or AnyDesk who want a self-hosted server on infrastructure they already control, and among security-conscious shops probing whether a fully offline deployment is possible before they commit.
## Related questions
v3/src/content/post/en/rustdesk-unattended-access-setup.md
+7 -7
View File
@@ -16,13 +16,13 @@ faq:
- question: 'How do I set up unattended access in RustDesk?'
answer: "Two things are required: set a permanent password under Settings, Security so you don't need someone to approve each connection, and install RustDesk as a system service so it runs before login and survives logout. With both in place you can reach the machine any time, including at the login screen, without a person present."
- question: 'Why does my RustDesk connection drop when the user logs out?'
answer: 'That happens when RustDesk is run as a portable executable instead of installed as a service. A portable session ends when the user logs out or a UAC prompt appears. Install RustDesk and enable the service (Start on boot) so it runs in the background independent of any logged-in user, which is what makes unattended access reliable.'
answer: 'That happens when RustDesk is run as a portable executable instead of installed as a service. A portable session ends when the user logs out or a UAC prompt appears. Install RustDesk (rather than running the portable executable) and keep its service enabled — the installed service starts with the system — so it runs in the background independent of any logged-in user, which is what makes unattended access reliable.'
- question: 'Is unattended access with a permanent password safe?'
answer: 'It can be deployed safely when configured well. Use a long, unique permanent password, restrict who can connect, enable available identity and access controls, patch clients, and review logs. Self-hosting controls server-side services and stored deployment data; the endpoint still protects its local credentials.'
- question: 'Can I deploy RustDesk unattended access to many computers at once?'
answer: "Yes. On Basic and higher self-hosted plans, the Custom Client Generator produces a pre-configured installer with your server address, key, and settings baked in, so end users don't type anything. Push it with your existing deployment tooling and each device installs the service and registers against your server automatically."
- question: 'Does unattended access work at the Windows login screen?'
answer: 'Yes, once RustDesk is installed as a service with Start on boot enabled. Because the service runs before any user logs in, you can connect to the login screen, authenticate, and even trigger a reboot and reconnect. Running the portable executable cannot do this because it only exists inside a user session.'
answer: 'Yes, once RustDesk is installed as a service. The installed service starts with the system before any user logs in, so you can connect to the login screen, authenticate, and even trigger a reboot and reconnect. Running the portable executable cannot do this because it only exists inside a user session.'
metadata:
description: 'Set up RustDesk unattended access: permanent password, run as a service for start on boot, per-platform notes for Windows/macOS/Linux, and fleet deployment.'
@@ -33,7 +33,7 @@ Unattended access means reaching a computer when no one is sitting in front of i
## The short answer
Set a **permanent password** (Settings → Security) and **install RustDesk as a system service** with _Start on boot_ enabled. The password removes the need for a human to accept the prompt; the service makes RustDesk run independently of any logged-in user, so you can connect at any time — including at the login screen. To deploy at scale, generate a pre-configured client so every machine installs itself against your server automatically.
Set a **permanent password** (Settings → Security) and **install RustDesk as a system service** — the installed service starts with the machine. The password removes the need for a human to accept the prompt; the service makes RustDesk run independently of any logged-in user, so you can connect at any time — including at the login screen. To deploy at scale, generate a pre-configured client so every machine installs itself against your server automatically.
## Step 1: Set a permanent password
@@ -50,7 +50,7 @@ The [RustDesk client documentation](https://rustdesk.com/docs/en/client/) descri
This is the step people miss. If you just run the portable `.exe` or `.app`, the session **ends the moment the user logs out or a UAC/permission prompt appears** — because that process only exists inside the user's session. To be truly unattended, RustDesk must run as a background **system service**.
- Run the RustDesk **installer** (not the portable build) and complete installation.
- In **Settings → General**, make sure the **Service** toggle is **on** and **Start on boot** is enabled.
- In **Settings → General**, make sure the **Service** is running — use **Start** if it shows as stopped. Once installed, the service starts with the machine automatically.
Once RustDesk runs as a service, it loads before anyone logs in, which is what lets you connect to the **login screen**, authenticate remotely, and even reboot and reconnect without a person present. Community write-ups on [proper Windows service setup](https://www.smolkin.org/blog/2026/03/rustdesk-unattended-service-windows.html) stress the same distinction: portable equals attended-only; installed service equals unattended.
@@ -58,10 +58,10 @@ Once RustDesk runs as a service, it loads before anyone logs in, which is what l
| Platform | What to do | Watch out for |
| -------- | -------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Windows | Install, enable Service + Start on boot | Portable exe drops on logout/UAC; use the installer |
| Windows | Install; keep the service running (starts with the machine) | 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 | 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 |
| Android | Set permanent password; enable capture | Screen must be awake; grant the screen-capture (MediaProjection) consent and input permission |
### Windows
@@ -87,7 +87,7 @@ Unattended access is a standing door into a machine, so treat the credentials se
- **Strong, unique permanent password**, rotated periodically.
- **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.
- **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 [RustDesk is open source under AGPL](/blog/open-source-remote-desktop-software), its authentication implementation can be reviewed.
## Unattended access you actually control
v3/src/content/post/en/rustdesk-unknown-devices-antivirus-scanning.md
+3 -3
View File
@@ -18,7 +18,7 @@ faq:
- question: 'How do I stop unknown devices from registering entirely?'
answer: 'If your device list is stable and you are not regularly adding machines, disable new-device registration in the console under Settings → Others → Disable new devices on web console. Nothing new can register after that, sandboxed or otherwise. If you still onboard devices regularly, use a deployment token instead so real rollouts keep working.'
- question: 'How do I require a deployment token for new devices?'
answer: 'Enable Require deployment for new devices in the console, generate a deploy token, and have your install process run the deploy command. The RustDesk client supports a deploy/token flag, but verify the exact flag in the current Server Pro docs, as syntax changes between releases. Only devices that present a valid token get added, so a sandboxed AV scan cannot register while your RMM or scripted rollout continues normally.'
answer: 'Enable Settings → Others → Require deployment for new devices in the web console, create an API token with the Devices permission set to Read and write, and have your install process run rustdesk --deploy --token <api_token> on each new device (with sudo on macOS and Linux). Only devices that present a valid token can register, so a sandboxed AV scan cannot add itself while your RMM or scripted rollout continues normally.'
- question: 'How do I tell a benign AV scan from a real intrusion?'
answer: 'A short-lived registration that lines up with a known security scan and shows no subsequent session may support the sandbox explanation. Unexpected sessions, repeated enrollment, use of valid credentials, or a configured client distributed outside its intended channel is not benign and warrants incident response.'
@@ -47,7 +47,7 @@ Two console settings solve this, and which one fits depends on whether you're st
**Option 1 — disable new-device registration entirely.** If your device list is basically stable and you're not regularly adding machines, this is the simplest fix: go to **Settings → Others → Disable new devices on web console**. Nothing new can register at all, sandboxed or otherwise.
**Option 2 — require a deployment token.** If you're still rolling out new devices regularly (an MSP onboarding clients, an IT team imaging new machines), a blanket "disable new devices" setting gets in your own way. Instead, enable **"Require deployment for new devices"**, generate a deploy token from the console, and have your install process run a deploy command such as:
**Option 2 — require a deployment token.** If you're still rolling out new devices regularly (an MSP onboarding clients, an IT team imaging new machines), a blanket "disable new devices" setting gets in your own way. Instead, enable **Settings → Others → Require deployment for new devices**, create an API token (Devices permission, Read and write), and have your install process run the documented [deployment command](https://rustdesk.com/docs/en/self-host/client-deployment/#explicit-deployment-for-new-devices) on each device:
```
rustdesk --deploy --token <api_token>
@@ -63,7 +63,7 @@ Registration alone does not prove that an attacker controlled another endpoint,
## Who asks this
This comes up most from IT admins and MSPs shortly after standing up a new self-hosted server, before registration controls have been tightened. Early investigation matters because benign scanning and unauthorized enrollment can look similar in the console.
New server operators — IT admins and MSPs alike — tend to hit this within days of standing up a self-hosted server, before registration controls have been tightened. Early investigation matters because benign scanning and unauthorized enrollment can look similar in the console.
## Related questions
v3/src/content/post/en/rustdesk-vs-anydesk.md
+17 -17
View File
@@ -13,11 +13,11 @@ tags:
- comparison
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."
description: "RustDesk vs AnyDesk compared in depth: features, OS support, security (including AnyDesk's 2024 security incident), pricing models, and clear pros and 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."
answer: "Yes. RustDesk 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?'
@@ -26,7 +26,7 @@ faq:
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.
RustDesk and AnyDesk approach remote desktop from opposite ends: AnyDesk is a proprietary product brokered through the vendor's cloud, while RustDesk is open source and built to run on a server you control. That difference — who hosts the infrastructure and who can read the code — runs through everything else in this comparison, from the security model to how concurrency is priced.
## Table of contents
@@ -44,9 +44,9 @@ Buyers commonly compare RustDesk with AnyDesk after reviewing renewal cost, host
## 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 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.
**AnyDesk** is a proprietary, commercial remote-desktop product from AnyDesk Software GmbH (formerly 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 is both its biggest strength and the main thing to weigh before you commit.
**RustDesk** is an open-source remote-desktop platform 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 it 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.
@@ -61,15 +61,15 @@ Both tools cover the core remote-support workflow. The differences are less abou
| File transfer | Yes (both directions) | Yes (file-browser mode) |
| 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) |
| Remote printing | Yes — remote printer for incoming connections (Windows) | Yes (AnyDesk printer) |
| 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) |
| Open source | Yes (AGPL) | No (proprietary) |
| Custom-branded client | Yes (built-in generator, Basic plan and up) | 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](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.
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** — standard plans include unlimited concurrent connections, while Customized V2 is the exception that meters them.
## OS and platform support
@@ -81,12 +81,12 @@ Both products are genuinely cross-platform on the desktop. The meaningful gaps a
| 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) |
| iOS / iPadOS | Controller only (no host, per Apple restrictions) | Controller only (cannot be controlled, per Apple restrictions) |
| Raspberry Pi | Yes — official ARM64/ARM32 Linux builds | Yes (Raspberry Pi OS 12+) |
| Chrome OS | — (no ChromeOS client; Android builds ship via GitHub releases / F-Droid, not Google Play) | View-only (control not supported) |
| tvOS / Apple TV | Not offered | Outgoing only (limited file transfer/recording) |
RustDesk officially lists Windows, macOS, Linux, Android, and iOS. AnyDesk's supported-OS documentation covers a slightly wider spread of niche targets (Raspberry Pi OS, Chrome OS viewing, tvOS), but with the same Apple-imposed limitation everyone hits: on iOS/iPadOS you can control _out_ to another machine, but you can't be fully controlled _from_ one. If your fleet includes Raspberry Pi appliances or you specifically need a Chrome OS or Apple TV client, verify the current state on each vendor's page before deciding — those targets change.
RustDesk officially lists Windows, macOS, Linux, Android, and iOS. AnyDesk's supported-OS documentation covers a couple of niche targets (Chrome OS viewing, tvOS), but with the same Apple-imposed limitation everyone hits: on iOS/iPadOS you can control _out_ to another machine, but you can't be fully controlled _from_ one. Raspberry Pi appliances are covered on the RustDesk side by the official ARM64/ARM32 Linux builds; if you specifically need a Chrome OS or Apple TV client, verify the current state on the vendor's page before deciding — those targets change.
## Security and identity
@@ -96,7 +96,7 @@ This is the section where the two products diverge philosophically, not just on
That last point stopped being abstract in 2024, when AnyDesk publicly disclosed a security incident affecting its production systems. By its own account, the response included rotating its code-signing certificate, pushing a re-signed client build, and resetting web-portal passwords as a precaution; exact dates and scope were reported variously at the time, so confirm the specifics against AnyDesk's own advisories. The episode illustrates vendor-concentration risk when a third party operates remote-access infrastructure.
**RustDesk's security model.** The client is open source under the AGPL, and Server Pro lets you operate the rendezvous, relay, and console. This removes a vendor-operated service from those roles, but it does not eliminate endpoint, credential, configuration, or software-vulnerability risk. Review the [latest RustDesk releases](https://github.com/rustdesk/rustdesk/releases) and public vulnerability records as part of deployment hardening.
**RustDesk's security model.** RustDesk is open source under the AGPL, and Server Pro lets you operate the rendezvous, relay, and console. This removes a vendor-operated service from those roles, but it does not eliminate endpoint, credential, configuration, or software-vulnerability risk. Review the [latest RustDesk releases](https://github.com/rustdesk/rustdesk/releases) and public vulnerability records as part of deployment hardening.
**Identity and directory integration.** For teams that live in Active Directory or an OIDC identity provider, LDAP and SSO matter. RustDesk offers **LDAP and SSO (OIDC) from the Basic plan and up**. AnyDesk's [official pricing page](https://anydesk.com/en/pricing), checked July 7, 2026, lists SSO on Ultimate; confirm directory requirements in a written quote. If single sign-on is mandatory, note which tier each vendor requires rather than treating identity as a generic checkbox. RustDesk's [LDAP and Active Directory setup guide](/blog/rustdesk-active-directory-ldap-sso) walks through its configuration.
@@ -125,7 +125,7 @@ Because RustDesk pricing itself shifts, this article deliberately doesn't quote
_Pros:_
- Open-source client (AGPL) — auditable, buildable, no black box
- Open source (AGPL) — auditable, buildable, no black box
- Self-hosted server keeps session brokering and traffic on your own infrastructure
- Unlimited concurrent connections on standard plans; Customized V2 is limited
- Per-user + per-device licensing with prorated upgrades
@@ -165,7 +165,7 @@ The teams that move to RustDesk after evaluating AnyDesk tend to cite the same h
**Open source is auditable trust.** You don't have to _believe_ the vendor about what the client does — you can read it, build it, and verify it. After a year like 2024 in the remote-access category, "we can inspect the code ourselves" resonates.
**The concurrency model changes the math at scale.** Standard RustDesk plans include unlimited concurrent connections; Customized V2 has a defined allowance and prices additional concurrency. All plans must also fit login-user and managed-device limits. RustDesk publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices), but capacity still needs validation against the actual rollout.
**The concurrency model changes the math at scale.** The plan mechanics are covered under [licensing](#licensing-and-pricing-models) above; what remains at fleet size is fitting login-user and managed-device limits. RustDesk publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices), but capacity still needs validation against the actual rollout.
**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.
v3/src/content/post/en/rustdesk-vs-logmein.md
+7 -9
View File
@@ -4,7 +4,7 @@ lang: en
translationKey: rustdesk-vs-logmein
draft: false
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."
excerpt: "Replacing LogMeIn Central or Pro? Here's how RustDesk compares on cost, self-hosting, and data control — trade-offs included."
image: ~/assets/images/blog/rustdesk-vs-logmein-og.png
category: Comparisons
tags:
@@ -26,9 +26,7 @@ faq:
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.
If you're comparing RustDesk and LogMeIn, here's an honest look at how they differ.
LogMeIn and RustDesk sit at opposite ends of the same job: one is a vendor-hosted subscription, the other an open-source platform you run on your own server. This comparison covers what that split means for cost, data control, identity integration, and the work of migrating.
## The short version
@@ -37,13 +35,13 @@ If you're comparing RustDesk and LogMeIn, here's an honest look at how they diff
| **Hosting** | Vendor cloud (SaaS) | Self-hosted on your own server |
| **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 |
| **Licensing model** | Subscription; unit varies by product (per computer for Pro/Central, per technician for Rescue) | Per login-user **+** per managed-device |
| **[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 |
| **How you evaluate** | Vendor trial | Self-host free, or ask sales about evaluation terms |
## Why teams start looking
Cost comparisons should use current written quotes for the same technician, device, concurrency, and feature requirements. Do not infer current pricing from another organization's private deployment details.
The first trigger is cost — a renewal total that no longer matches what the team actually uses.
The second trigger is control. LogMeIn is a pure cloud product — your sessions and device list live on LogMeIn's servers, on LogMeIn's terms. Some of the teams evaluating RustDesk specifically wanted a self-hosted option instead, so the server (and their data) sits on infrastructure they manage.
@@ -83,10 +81,10 @@ Before removing the incumbent agent, verify external direct and relay connection
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
## See it running before you decide
- **Self-host the free community server today** — open source, no cost, no expiry.
- **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.
- **Want to try the Pro features?** Email [sales@rustdesk.com](mailto:sales@rustdesk.com) to ask about current evaluation terms.
- **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.
Licensing is per login-user + per managed-device, and you can [upgrade any time](/blog/upgrade-rustdesk-license-mid-subscription). Start at [rustdesk.com/pricing](https://rustdesk.com/pricing).
v3/src/content/post/en/rustdesk-vs-rdp.md
+3 -3
View File
@@ -4,7 +4,7 @@ lang: en
translationKey: rustdesk-vs-rdp
draft: false
title: 'RustDesk vs RDP: Cross-Platform vs Windows-Native'
excerpt: 'RustDesk vs Microsoft RDP: an honest comparison of cross-platform reach, internet access without a VPN, LAN speed, and security trade-offs.'
excerpt: 'RustDesk vs Microsoft RDP: a practical comparison of cross-platform reach, internet access without a VPN, LAN speed, and security trade-offs.'
image: ~/assets/images/blog/rustdesk-vs-rdp-og.png
category: Comparisons
tags:
@@ -22,7 +22,7 @@ faq:
- question: 'Can RustDesk connect to a Mac or Linux machine?'
answer: 'Yes. RustDesk can control macOS and Linux hosts from its supported desktop and mobile controller apps. RDP is primarily a Windows host protocol, so reaching macOS or Linux hosts usually means adding third-party servers or clients. RustDesk for iOS can control other devices but cannot expose an iPhone or iPad as a remote-control host.'
metadata:
description: 'RustDesk vs Microsoft RDP compared honestly: cross-platform reach, internet access without a VPN, LAN performance, AD integration, and security trade-offs.'
description: 'RustDesk vs Microsoft RDP compared point by point: cross-platform reach, internet access without a VPN, LAN performance, AD integration, and security trade-offs.'
keywords: 'RustDesk vs RDP, RustDesk vs Microsoft Remote Desktop, RDP over internet without VPN, cross-platform RDP alternative'
---
@@ -54,7 +54,7 @@ The safer way to publish RDP is through a properly configured VPN or RD Gateway
| | RustDesk | Microsoft RDP |
| ---------------------------- | -------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cost | Open-source client; free self-hosted community server | Free, built into Windows Pro/Enterprise/Education/Server |
| Cost | Open source; free self-hosted community server | Free, built into Windows Pro/Enterprise/Education/Server |
| Source code | Open source (AGPL), auditable | Proprietary |
| Host platforms | Windows, macOS, Linux, Android | Windows Pro/Enterprise/Education/Server ([not Home](https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/remote-desktop-allow-access)) |
| Controller platforms | Windows, macOS, Linux, Android, iOS | Windows, macOS, iOS, Android, and other Microsoft clients |
v3/src/content/post/en/rustdesk-vs-screenconnect.md
+12 -18
View File
@@ -4,7 +4,7 @@ lang: en
translationKey: rustdesk-vs-screenconnect
draft: false
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.'
excerpt: 'A full comparison of RustDesk vs ScreenConnect: features, OS support, security (including CVE-2024-1709), pricing models, and the self-hosting trade-off.'
image: ~/assets/images/blog/rustdesk-vs-screenconnect-og.png
category: Comparisons
tags:
@@ -14,7 +14,7 @@ tags:
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.'
answer: 'Yes. RustDesk Server Pro runs the ID/rendezvous and relay services on infrastructure you control, and RustDesk 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?'
@@ -22,11 +22,11 @@ faq:
- 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.'
description: 'RustDesk vs ScreenConnect compared in depth: features, OS support, security (incl. CVE-2024-1709), pricing models, and clear pros and cons for MSPs.'
keywords: 'RustDesk vs ScreenConnect, RustDesk vs ConnectWise Control, ScreenConnect self-hosted alternative, ScreenConnect comparison'
---
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.
RustDesk and ScreenConnect both target the MSP remote-support workflow; the split is ownership — ScreenConnect is proprietary software licensed per concurrent technician, while RustDesk is open source and built to be self-hosted. This article relies on public incident disclosures and product documentation rather than reproducing private customer emails, contract dates, or deployment details.
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.
@@ -64,7 +64,7 @@ The table below covers the everyday remote-support feature set. A note on method
| 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 |
| Remote printing | Yes — remote printer for incoming connections (Windows) | 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).
@@ -79,8 +79,8 @@ Both tools are cross-platform, with one structural difference worth understandin
| 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 | Browser-based web client for controlling (Server Pro, plan-gated); hosting uses the native client | Yes — host via Chrome, Firefox, Safari, Edge |
| iOS | Controller only | View-only guest screen sharing; iOS technician app |
| Control from a browser | Browser client for controlling (public web client, or self-hosted at a plan size); being controlled needs 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.
@@ -90,15 +90,13 @@ This section covers the security and compliance questions that usually drive the
**ScreenConnect's security model.** ConnectWise's current pricing page lists AES-256 encryption, two-factor authentication, brute-force prevention, granular access management, and integrations with LDAP, SAML, OAuth, and other SSO providers. Its on-premise product page lists multi-factor authentication and role-based access controls and describes configurations intended to support SOC 2, PCI, CJIS, and HIPAA requirements. These are vendor claims rather than a conclusion that any deployment is automatically compliant; the first-party pages are linked in [Sources](#sources).
**The 2024 incident.** One reason teams evaluating alternatives point to ScreenConnect's 2024 history is a specific, well-documented event. In February 2024, a critical authentication-bypass vulnerability in ScreenConnect, **CVE-2024-1709**, was disclosed. It carried a CVSS score of 10.0 — the maximum — and worked by appending a trailing slash to the `SetupWizard.aspx` URL to bypass a request filter, letting an unauthenticated attacker create a new administrator account and take full control of the server. It was paired with a path-traversal flaw, CVE-2024-1708. Affected versions were 23.9.7 and earlier; the fix shipped in 23.9.8. The bug was trivially exploitable, proof-of-concept exploits appeared almost immediately, and it was quickly tied to active exploitation, including ransomware activity.
[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.
**The 2024 incident.** One reason teams evaluating alternatives point to ScreenConnect's 2024 history is a specific, well-documented event. In February 2024, a critical authentication-bypass vulnerability in ScreenConnect, **CVE-2024-1709**, was disclosed. It carried a CVSS score of 10.0 — the maximum — and worked by appending a trailing slash to the `SetupWizard.aspx` URL to bypass a request filter, letting an unauthenticated attacker create a new administrator account and take full control of the server. It was paired with a path-traversal flaw, CVE-2024-1708. Affected versions were 23.9.7 and earlier; the fix shipped in 23.9.8. The bug was trivially exploitable, proof-of-concept exploits appeared almost immediately, and it was quickly tied to active exploitation, including ransomware activity. [CISA added CVE-2024-1709 to its Known Exploited Vulnerabilities catalog](https://www.cisa.gov/news-events/alerts/2024/02/22/cisa-adds-one-known-exploited-connectwise-vulnerability-cve-2024-1709-catalog) on February 22, 2024 — the formal signal that a flaw is being exploited in the wild and must be remediated on a deadline — and emergency patching and public scrutiny swept the MSP market.
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).
**RustDesk's security model.** RustDesk's approach is structurally different. RustDesk 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; plans below Basic do not include 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).
Being open source does not make software invulnerable. Review RustDesk's [latest releases](https://github.com/rustdesk/rustdesk/releases) and public vulnerability records. ScreenConnect cloud mode provides a vendor-operated service; RustDesk provides auditable code and self-hosted server-side services, along with operating responsibility. For the routing and residency boundaries, see [Remote Desktop and Data Sovereignty](/blog/remote-desktop-data-sovereignty-gdpr).
@@ -116,7 +114,7 @@ Pricing changes often, so rather than treat any number as permanent fact, we'll
_Pros_
- Open-source (AGPL) core client — auditable and buildable from source
- Open source (AGPL) — auditable and buildable from source
- Self-hosted Server Pro keeps brokering/relay on infrastructure you own (data sovereignty, GDPR)
- Unlimited concurrent connections on standard plans; limited on Customized V2
- Custom-branded client generator
@@ -152,9 +150,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 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).
**Open source you can actually verify.** The AGPL code 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.
**A client with your name on it.** RustDesk's custom-branded client generator lets you ship a tool that carries your brand to end users rather than a vendor's — meaningful for MSPs whose clients should see _their_ provider, not a third party.
@@ -168,9 +164,7 @@ You can run the entire coordination layer yourself and keep session data inside
## Try RustDesk yourself
The no-pressure way to evaluate RustDesk is a representative proof of concept:
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 no-pressure way to evaluate RustDesk is a representative proof of concept. Stand up the free community server and point a few endpoints at it — no cost, no sales call. For the Pro features, ask [sales@rustdesk.com](mailto:sales@rustdesk.com) about current evaluation terms or see [rustdesk.com/pricing](https://rustdesk.com/pricing), and there's a [video walkthrough](https://www.youtube.com/@rustdesk) if you'd rather watch first.
You can also just [See RustDesk in Action](/blog/see-rustdesk-in-action) first if you'd like a guided tour before you deploy anything.
v3/src/content/post/en/rustdesk-vs-splashtop.md
+9 -9
View File
@@ -18,7 +18,7 @@ faq:
- 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: '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.'
answer: 'Self-host when you want control of the server-side services, open-source software, 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:
@@ -26,7 +26,7 @@ metadata:
keywords: 'self-hosted Splashtop alternative, Splashtop replacement, migrate from Splashtop, RustDesk vs Splashtop, Splashtop alternative for IT teams'
---
A self-hosted Splashtop alternative is worth evaluating when your IT team needs control over server-side services, an open-source core client, or a licensing model that better matches its users, devices, and simultaneous sessions. It is not automatically the right move: switching also transfers infrastructure work to your team and can expose workflow gaps that a feature matrix misses.
A self-hosted Splashtop alternative is worth evaluating when your IT team needs control over server-side services, open-source software, or a licensing model that better matches its users, devices, and simultaneous sessions. It is not automatically the right move: switching also transfers infrastructure work to your team and can expose workflow gaps that a feature matrix misses.
Splashtop sells managed SaaS plans and a **separately licensed On-Prem** product. RustDesk makes self-hosting the core deployment model through its free community server and Server Pro. The useful comparison is therefore between three operating models, not simply "cloud versus self-hosted."
@@ -40,7 +40,7 @@ Splashtop sells managed SaaS plans and a **separately licensed On-Prem** product
| 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 |
| Best starting point | Free community server for basic evaluation; Server Pro evaluation via sales@rustdesk.com 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 the effort of running RustDesk yourself with Splashtop SaaS. If infrastructure control is mandatory, compare RustDesk Server Pro with Splashtop On-Prem.
@@ -50,7 +50,7 @@ The reasons usually fall into four decision areas. These are evaluation prompts,
### Licensing fit
Remote-support workloads can be measured by technicians, named users, managed endpoints, attended sessions, or concurrent connections. A plan that works for a small fixed team may become awkward for an MSP, a seasonal workforce, or an organization near a device threshold. Compare the current written terms against your actual workload rather than assuming any vendor is always cheaper.
Remote-support workloads can be measured by technicians, named users, managed endpoints, attended sessions, or concurrent connections. A plan that works for a small fixed team may become awkward for an MSP, a seasonal workforce, or an organization near a device threshold — no vendor is automatically the cheaper one.
### Infrastructure control
@@ -72,7 +72,7 @@ Splashtop On-Prem is therefore real, but it is not the default deployment behind
RustDesk starts from the opposite direction. The community server and Server Pro are self-hosted. With Server Pro, the ID/rendezvous server, relay, console, and stored deployment data run on infrastructure you control; direct sessions can still flow between endpoints. This provides architectural control, but it does not remove the need to secure and operate the server.
Do not describe Splashtop as cloud-only, and do not treat a standard Splashtop SaaS trial as an evaluation of Splashtop On-Prem. They have different deployment and procurement paths.
Splashtop is not cloud-only, and a SaaS trial tells you little about On-Prem — the two have different deployment and procurement paths.
## Source code and trust model
@@ -87,7 +87,7 @@ Splashtop On-Prem can answer the first requirement. RustDesk is designed to answ
## Licensing and cost: model the required system
RustDesk standard Server Pro plans are sized by login users and managed devices and include unlimited concurrent connections. Customized V2 instead includes a defined concurrency allowance and prices additional connections. For current figures, use [RustDesk pricing](https://rustdesk.com/pricing) and a dated quote for customized terms.
RustDesk standard Server Pro plans are sized by login users and managed devices and include unlimited concurrent connections. Customized V2 instead includes a defined concurrency allowance and prices additional connections. Current figures are at [RustDesk pricing](https://rustdesk.com/pricing).
Splashtop pricing depends on whether the requirement is Remote Access, Remote Support, Enterprise SaaS, or On-Prem. Its public pricing page provides figures for several SaaS plans, while Enterprise and On-Prem require sales engagement. Compare the same quantities on both sides:
@@ -104,7 +104,7 @@ A lower starting price, another customer's historical quote, or a first-year pro
A 2025 thread in the [Splashtop official community](https://www.reddit.com/r/Splashtop_Official/comments/1ltgest/constant_crashing_on_local_win10_computer/) documents Windows client crashes and follow-up troubleshooting. A separate 2026 [Atera community discussion](https://www.reddit.com/r/atera/comments/1qucbx3/is_splashtop_just_terrible_for_you_guys/) contains both negative reports and administrators describing stable deployments. It also shows why an **integration-specific** problem should not automatically be attributed to the standalone Splashtop product.
Use reports like these to build a test matrix, not to publish an unbounded claim that Splashtop is unreliable. Record results on your own endpoint mix, network paths, RMM packaging, security software, and operating-system versions.
These reports don't show Splashtop is broadly unreliable — use them to build the test matrix for your own pilot. Record results on your own endpoint mix, network paths, RMM packaging, security software, and operating-system versions.
## Operations: self-hosting is a responsibility
@@ -124,7 +124,7 @@ Infrastructure control is valuable when the team is prepared to operate it; if y
The free RustDesk community server does not include every Server Pro governance feature. If you need SSO, controlled-device 2FA, audit logs, synchronized address books, or scoped access through user assignments and device groups, compare the current Server Pro plan matrix and [LDAP/SSO documentation](/blog/rustdesk-active-directory-ldap-sso).
Do not infer Splashtop On-Prem capabilities from a Splashtop SaaS trial, and do not infer Server Pro capabilities from the free RustDesk server. Confirm the exact edition and license for identity integration, permissions, high availability, recording, IP restrictions, and other required controls.
Do not infer Server Pro capabilities from the free RustDesk server. Confirm the exact edition and license for identity integration, permissions, high availability, recording, IP restrictions, and other required controls.
## Migration checklist: test the workflow, not the logo
@@ -177,7 +177,7 @@ This approach costs more during the overlap, but it reduces the risk of discover
## 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.
RustDesk deserves evaluation when the organization wants self-hosting as the normal deployment model, open-source software, 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.
Those advantages do not remove the operational caveat: your team still needs to provision, secure, monitor, back up, and update the RustDesk server.
v3/src/content/post/en/rustdesk-vs-teamviewer.md
+12 -14
View File
@@ -4,7 +4,7 @@ lang: en
translationKey: rustdesk-vs-teamviewer
draft: false
title: 'RustDesk vs TeamViewer: The Self-Hosted Alternative'
excerpt: 'RustDesk vs TeamViewer compared: features, OS support, security, licensing models, and honest trade-offs — self-hosting, open source, no per-channel pricing.'
excerpt: 'RustDesk vs TeamViewer compared: features, OS support, security, licensing models, and the real trade-offs — self-hosting, open source, no per-channel pricing.'
image: ~/assets/images/blog/rustdesk-vs-teamviewer-og.png
category: Comparisons
tags:
@@ -13,7 +13,7 @@ tags:
- comparison
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.'
description: 'RustDesk vs TeamViewer compared: features, OS support, security, licensing models, and clear pros and 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?'
@@ -26,7 +26,7 @@ faq:
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.
RustDesk and TeamViewer solve the same remote-access problem on opposite models: an open-source stack you host yourself versus a managed cloud service you subscribe to.
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.
@@ -47,7 +47,7 @@ TeamViewer is a commercial remote-access platform with a deep integration catalo
**TeamViewer** is a commercial remote-access and remote-support platform from TeamViewer SE, in the market since 2005 and one of the most widely deployed tools of its kind. It is delivered as a managed, cloud-brokered SaaS: TeamViewer runs the connection infrastructure, you install a client, and sessions are brokered through TeamViewer's own routing network. It is closed-source, sold on annual subscriptions, and its higher tiers (branded **TeamViewer Tensor**) add enterprise features such as single sign-on, conditional access, mass deployment, and a broad catalog of integrations with tools like ServiceNow, Jira, and Microsoft Intune. ([TeamViewer Tensor / integrations](https://www.teamviewer.com/en/integrations/))
**RustDesk** is an open-source remote desktop tool built around a different premise: you can run the whole thing yourself. The core client is open source under the AGPL, so it can be audited, built from source, and used with a free community server that runs indefinitely. The commercial offering, **RustDesk Server Pro**, is self-hosted — the ID/rendezvous server and the relay server run on your own machine or VPS, which means session metadata and connection brokering stay on infrastructure you control. RustDesk is licensed by login-user and by managed-device rather than by concurrent session, and it is designed to scale from a single technician up to large fleets. If your objection to TeamViewer is fundamentally about _control_ — over data, over cost, over the software itself — that is the axis on which these two products differ most.
**RustDesk** is an open-source remote desktop tool built around a different premise: you can run the whole thing yourself. RustDesk is open source under the AGPL, so it can be audited, built from source, and used with a free community server that runs indefinitely. The commercial offering, **RustDesk Server Pro**, is self-hosted — the ID/rendezvous server and the relay server run on your own machine or VPS, which means session metadata and connection brokering stay on infrastructure you control. RustDesk is licensed by login-user and by managed-device rather than by concurrent session, and it is designed to scale from a single technician up to large fleets. If your objection to TeamViewer is fundamentally about _control_ — over data, over cost, over the software itself — that is the axis on which these two products differ most.
The rest of this article breaks the comparison down feature by feature.
@@ -63,7 +63,7 @@ The table below compares the day-to-day capabilities most teams ask about. The R
| 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/)) |
| Remote printing | Yes — remote printer for incoming connections (Windows) | 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)) |
@@ -85,11 +85,11 @@ Both tools cover the major desktop and mobile platforms; the details differ at t
| 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/)) |
| iOS / iPadOS | Controller only (no host, per Apple restrictions) | Controller app, iOS/iPadOS 15+ (cannot be fully controlled, per Apple restrictions) ([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/)) |
| Raspberry Pi OS | Yes — official ARM64/ARM32 Linux builds | 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/)) |
The headline is that both products run on Windows, macOS, Linux, Android, and iOS, so for the overwhelming majority of mixed-fleet support work either tool will reach the endpoints you need. TeamViewer casts a slightly wider net on the fringes (ChromeOS screen sharing, Raspberry Pi via its Classic build), with the caveat that some of that support is limited-functionality or restricted to the older Classic client. If exotic endpoints matter to you, verify the specific device against each vendor's current list before committing.
The headline is that both products run on Windows, macOS, Linux, Android, and iOS, so for the overwhelming majority of mixed-fleet support work either tool will reach the endpoints you need. TeamViewer covers a couple of extra fringes (ChromeOS screen sharing, and Raspberry Pi via its older Classic client), while RustDesk covers Pi with its standard ARM64/ARM32 Linux builds. If exotic endpoints matter to you, verify the specific device against each vendor's current list before committing.
## Security and identity
@@ -99,9 +99,9 @@ This is where the two products embody genuinely different philosophies, so it is
It is only fair to note the counter-example on the incident side. In June 2024, TeamViewer disclosed that its **corporate IT network** was breached; the intrusion was attributed to APT29 (also tracked as Midnight Blizzard), the group linked to Russia's foreign intelligence service, using compromised employee credentials. TeamViewer stated the incident was contained to its internal corporate environment, that employee directory data and encrypted passwords were exposed, and that there was no evidence the attacker reached the product environment or customer data. ([BleepingComputer](https://www.bleepingcomputer.com/news/security/teamviewers-corporate-network-was-breached-in-alleged-apt-hack/), [TeamViewer bulletin TV-2024-1005](https://www.teamviewer.com/en-us/resources/trust-center/security-bulletins/tv-2024-1005/)) No vendor is immune to this class of attack; we mention it because "the vendor's own network is a target" is precisely the risk profile that a self-hosted model changes.
**RustDesk's security model** starts from a different place. The core client is open source under the AGPL, so the code can be independently audited and built from source. RustDesk Server Pro is self-hosted: you operate the ID/rendezvous, relay, console, and stored deployment data. Direct sessions still flow between endpoints. Open source also makes defects public, so review the [latest releases](https://github.com/rustdesk/rustdesk/releases) and current vulnerability records rather than assuming self-hosting eliminates software risk.
**RustDesk's security model** starts from a different place. RustDesk is open source under the AGPL, so the code can be independently audited and built from source. RustDesk Server Pro is self-hosted: you operate the ID/rendezvous, relay, console, and stored deployment data. Direct sessions still flow between endpoints. Open source also makes defects public, so review the [latest releases](https://github.com/rustdesk/rustdesk/releases) and current vulnerability records rather than assuming self-hosting eliminates software risk.
On **identity**, one clarification that matters for planning. RustDesk supports LDAP/Active Directory and SSO via OIDC, and this is available **from the Basic plan and up** — it is not gated to only the top tiers, and it is not present on every paid arrangement below Basic either, so map it to the specific plan you intend to buy. Full setup details are in [RustDesk LDAP & Active Directory: Setup Guide](/blog/rustdesk-active-directory-ldap-sso). For per-user access control, RustDesk provides a self-hosted web console, device groups, and a shared address book, plus a custom-branded client generator so the app your users install carries your name rather than the vendor's.
On **identity**, one clarification that matters for planning. RustDesk supports LDAP/Active Directory and SSO via OIDC, and this is available **from the Basic plan and up**: it is not top-tier-only, but plans below Basic do not include it — map it to the specific plan you intend to buy. Full setup details are in [RustDesk LDAP & Active Directory: Setup Guide](/blog/rustdesk-active-directory-ldap-sso). For per-user access control, RustDesk provides a self-hosted web console, device groups, and a shared address book, plus a custom-branded client generator so the app your users install carries your name rather than the vendor's.
If keeping session data on infrastructure you control is the whole point of the exercise, the dedicated discussion is in [Remote Desktop & Data Sovereignty](/blog/remote-desktop-data-sovereignty-gdpr) and [Why Self-Host Your Remote Desktop Software](/blog/why-self-host-remote-desktop-software).
@@ -125,7 +125,7 @@ There is also a free-tier wrinkle. TeamViewer's free tier is for personal, non-c
_Pros_
- Open-source (AGPL) core client — auditable, buildable from source, free community server that runs indefinitely
- Open source (AGPL) — auditable, buildable from source, free community server that runs indefinitely
- Self-hosted Server Pro: ID/rendezvous and relay servers run on your own machine or VPS, keeping session brokering inside your perimeter
- Unlimited concurrent connections on standard plans; limited on Customized V2
- Licensed by login-user + managed-device, with prorated upgrades any time
@@ -158,14 +158,12 @@ _Cons_
Everything above is the neutral part. The following section explains which buyer requirements align with RustDesk's model.
**They want a different concurrency model.** RustDesk standard plans include unlimited concurrent connections, while Customized V2 licenses a defined allowance. All plans also require sufficient login-user and managed-device capacity. See the [concurrency FAQ](/blog/rustdesk-concurrent-connections-limit).
**They want a different licensing and scaling model.** RustDesk sizes commercial plans by login users and managed devices; standard plans include unlimited concurrent connections, while Customized V2 licenses a defined allowance. Rates and allowances can change, so model growth against the current pricing matrix — see the [concurrency FAQ](/blog/rustdesk-concurrent-connections-limit) and the [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices).
**They want control over the server-side data path.** Running the ID/rendezvous and relay services lets a team choose where those services and stored metadata reside. Direct session traffic still flows between endpoints, and self-hosting alone does not establish GDPR compliance. See [Why Self-Host](/blog/why-self-host-remote-desktop-software), [Self-Hosted vs Cloud](/blog/rustdesk-self-hosted-vs-cloud-saas-option), and [Remote Desktop & Data Sovereignty](/blog/remote-desktop-data-sovereignty-gdpr).
**They want to read the code.** Open source under the AGPL means the client can be audited and built from source rather than trusted blindly. For security-conscious buyers, "we can inspect it" is a different assurance level from "the vendor says it's fine."
**They need a different scaling model.** RustDesk sizes commercial plans by login users and managed devices, with plan-specific concurrency terms, and publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices). Rates and allowances can change, so model growth against the current pricing matrix.
**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).
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).
v3/src/content/post/en/rustdesk-vs-vnc.md
+5 -5
View File
@@ -4,7 +4,7 @@ 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 why teams move from VNC to RustDesk."
excerpt: "RustDesk vs VNC compared in practice: 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:
@@ -23,7 +23,7 @@ faq:
- question: 'Is RustDesk or VNC better for a home lab on a LAN?'
answer: 'On a trusted LAN, VNC is dead-simple, standardized, and widely available on almost every OS and even Raspberry Pi. RustDesk adds NAT traversal, modern codecs, and default encryption that matter more once you leave the LAN or need mixed-OS remote access.'
metadata:
description: "RustDesk vs VNC compared honestly: NAT traversal, modern codecs, built-in encryption, self-hosting, and where VNC's simplicity and ubiquity still win."
description: "RustDesk vs VNC compared point by point: NAT traversal, modern codecs, built-in encryption, self-hosting, and where VNC's simplicity and ubiquity still win."
keywords: 'RustDesk vs VNC, RustDesk vs RealVNC, VNC NAT traversal, VNC encryption comparison'
---
@@ -59,7 +59,7 @@ RustDesk applies **end-to-end encryption by default** on every connection, self-
| --------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
| What it is | One AGPL app + rendezvous/relay | RFB protocol, many implementations |
| Source code | Open source (AGPL) | Mixed: GPL/open (TigerVNC, TightVNC), proprietary (RealVNC) |
| Cross-platform | Windows, macOS, Linux, Android, iOS | Very broad, including Raspberry Pi |
| Cross-platform | Windows, macOS, Linux, Android; iOS (controller only) | Very broad, including Raspberry Pi |
| NAT traversal | Built in (rendezvous + relay) | None in base protocol — [needs port-forwarding/VPN/SSH](https://en.wikipedia.org/wiki/Virtual_Network_Computing) |
| Encryption | End-to-end (NaCl) by default ([docs](https://rustdesk.com/docs/en/)) | Varies: AES (RealVNC) to none (TightVNC) |
| Video transport | Modern codecs (VP8/VP9/AV1, H.264/H.265) | Pixel-based RFB encodings |
@@ -76,7 +76,7 @@ RustDesk's design advantages appear the moment you leave the LAN or need consist
- **Internet reach without plumbing.** NAT traversal and relay fallback mean no port-forwarding, VPN, or SSH tunnel per endpoint.
- **Encryption you don't have to configure.** End-to-end by default, not an implementation you have to vet.
- **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.
- **One auditable app and one self-hosted server.** Open-source (AGPL) software 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 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.
@@ -86,4 +86,4 @@ For a trusted LAN, an air-gapped segment, or a Raspberry Pi, VNC's simplicity an
## Try it
Self-host the free community server today, or email [sales@rustdesk.com](mailto:sales@rustdesk.com) about evaluation terms. Standard plan rates are at [rustdesk.com/pricing](https://rustdesk.com/pricing), and there's a full walkthrough on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
If this comparison is what finally retires your SSH tunnel, start with the free community server — open source, no expiry, NAT traversal included. Email [sales@rustdesk.com](mailto:sales@rustdesk.com) when you want Pro evaluation terms; current plan rates are at [rustdesk.com/pricing](https://rustdesk.com/pricing).
v3/src/content/post/en/rustdesk-web-console-custom-client-generator-port-21114.md
+9 -9
View File
@@ -13,13 +13,13 @@ tags:
author: RustDesk Team
faq:
- question: 'How do I reach the RustDesk Server Pro Web Console?'
answer: 'RustDesk Server Pro serves plain HTTP on port 21114, but you must not send credentials over that connection on a public or untrusted network. Configure HTTPS first. If TLS is not yet available, complete the first login only through localhost, an SSH tunnel, or a trusted private network, then rotate the initial credentials. The Custom Client Generator requires Basic or a higher plan.'
answer: 'RustDesk Server Pro serves plain HTTP on port 21114, but you must not send credentials over that connection on a public or untrusted network. Configure HTTPS first. If TLS is not yet available, complete the first login only through localhost, an SSH tunnel, or a trusted private network, then rotate the initial credentials.'
- question: 'How do I put the RustDesk Web Console behind HTTPS with a valid certificate?'
answer: 'Port 21114 serves plain HTTP and does not 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 update the client API address to the HTTPS endpoint.'
- question: "Why can't I reach the console on port 21114?"
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.'
answer: 'If none of the URLs respond, the Pro service 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.'
answer: 'Native clients need TCP 21115-21117 and UDP 21116 for NAT test, ID registration, hole punching, and relay; TCP 21118-21119 serve WebSocket and web clients; the console itself is on TCP 21114, or on 443 behind a reverse proxy. Open only what your deployment uses, and confirm against the current RustDesk docs 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?"
@@ -34,7 +34,7 @@ faq:
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.'
metadata:
description: "Can't reach the RustDesk Pro web console or Custom Client Generator on port 21114? Here are the URLs, TLS notes, and first-login checks."
description: "Fix RustDesk web console access on port 21114: check firewall and proxy, put HTTPS in front, log in safely, and find the Custom Client Generator."
keywords: 'RustDesk web console port 21114, RustDesk Custom Client Generator, RustDesk Pro web console login, RustDesk self-hosted admin console, access RustDesk console port 21114, RustDesk reverse proxy'
---
@@ -48,7 +48,7 @@ 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 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."
If the console does not respond, the service 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.
@@ -79,14 +79,14 @@ Self-hosting the web client (serving it from your own server at `https://your-se
## Who asks this
This comes up most often with IT admins and [MSPs](/blog/rustdesk-for-msps) standing up a self-hosted RustDesk Server Pro for the first time. Two separate checks are required: confirm that the console is reachable, then confirm that the selected plan includes the generator.
First-time Server Pro installers — IT admins and [MSPs](/blog/rustdesk-for-msps) standing up their own server — are the main audience, typically minutes after deployment when the console URL does not load. Two separate checks are required: confirm that the console is reachable, then confirm that the selected plan includes the generator.
## Related questions
- [How do I open or forward port 21114 on a cloud-hosted RustDesk server?](https://rustdesk.com/docs)
- [How do I put the RustDesk Web Console behind HTTPS with a valid certificate?](https://rustdesk.com/docs)
- [How do I run RustDesk Server Pro without Docker?](/blog/rustdesk-server-pro-without-docker)
- [How does the Custom Client Generator brand and pre-configure a client build?](/blog/rustdesk-for-msps)
- [I changed the admin password and locked myself out — how do I reset it?](https://rustdesk.com/docs)
- [Which ports does RustDesk Server Pro need open besides 21114?](https://rustdesk.com/docs)
- [Where do I manage licenses, invoices, and renewals?](/blog/upgrade-rustdesk-license-mid-subscription)
- [Why won't RustDesk connect, and which ports matter?](/blog/rustdesk-not-connecting-troubleshooting)
Still stuck? Confirm the server process is running and that either TCP 21114 is reachable through a protected bootstrap path or your configured TCP 443 reverse proxy is reachable over HTTPS. Never submit credentials to port 21114 across the public internet; rotate the initial admin credentials after the protected first login.
v3/src/content/post/en/self-host-rustdesk-server-hardware-at-scale.md
+6 -6
View File
@@ -14,17 +14,17 @@ tags:
author: RustDesk Team
faq:
- question: 'How much hardware do I need to self-host RustDesk for a large fleet?'
answer: 'RustDesk Server Pro requirements depend more on concurrent sessions, relay traffic, storage, and operating-system limits than on raw device inventory. Many deployments can start with an SSD-backed host and validate whether they actually need more RAM, CPU, bandwidth, or an external database.'
answer: 'RustDesk Server Pro requirements depend more on concurrent sessions, relay traffic, storage, and operating-system limits than on raw device inventory. Many deployments can start with an SSD-backed host and validate whether they actually need more RAM, CPU, or bandwidth.'
- question: 'Does RustDesk Server Pro need PostgreSQL or MySQL, or is SQLite enough?'
answer: 'SQLite is enough to start for many deployments, including fleets in the thousands, and keeps the setup simple. Move to an external database such as PostgreSQL or MySQL only when your workload, operating model, or observability needs justify it. SSD storage keeps the database and its logging responsive under load.'
answer: 'RustDesk Server Pro uses a built-in SQLite database (db.sqlite3) — there is no separate PostgreSQL or MySQL to run, and none is needed even for fleets in the thousands. Scale by giving the host enough CPU, RAM, SSD storage, and relay bandwidth for your session load rather than by swapping the database engine.'
- question: 'What OS socket and file-descriptor limits should I set for a large deployment?'
answer: 'Concurrent TCP/WebSocket connections and relayed streams stress operating-system socket and file-descriptor limits more than device count does. Raise your ulimit and file-descriptor ceilings and give the host adequate network throughput rather than piling on RAM you will not use.'
- question: 'How much RAM and CPU does a self-hosted RustDesk server use per session?'
answer: 'Load is driven by concurrent active sessions and relay traffic, not by the number of registered devices. Size CPU and bandwidth for your peak simultaneous sessions and any heavy relay reliance; RAM is rarely the bottleneck.'
metadata:
description: 'Planning to self-host RustDesk for thousands of devices? Size for concurrent sessions, relay traffic, storage, and OS limits rather than inventory alone.'
keywords: 'self-host RustDesk server hardware, RustDesk Server Pro requirements, RustDesk hardware requirements at scale, RustDesk SQLite vs database, RustDesk self-hosted performance, RustDesk server sizing'
description: 'RustDesk server sizing for large fleets: concurrent sessions, relay bandwidth, SSD storage, and OS socket limits matter more than device inventory.'
keywords: 'self-host RustDesk server hardware, RustDesk Server Pro requirements, RustDesk hardware requirements at scale, RustDesk Server Pro SQLite database, RustDesk self-hosted performance, RustDesk server sizing'
---
Self-hosting RustDesk at scale is often less hardware-hungry than IT teams expect. The important thing is sizing for the traffic and operating pattern you actually have, not guessing from inventory alone.
@@ -39,13 +39,13 @@ The key insight for capacity planning is that the number of _registered_ devices
The real load comes from concurrent activity. Each active remote session opens TCP/WebSocket connections, and any session that can't connect peer-to-peer falls back to the relay, which passes traffic through your server. The more simultaneous sessions and relayed streams you run, the more the CPU, network, and — critically — the OS socket and file-descriptor limits matter. When you tune your server, raise those `ulimit`/file-descriptor ceilings and give the box adequate network throughput rather than piling on RAM you won't use.
On the database question, teams often assume a fleet in the thousands automatically demands PostgreSQL or MySQL. Many deployments do not start there. SQLite can keep the deployment simple at first; move to an external database only when your workload, operating model, or observability needs justify it. SSD storage matters because it keeps the database and its logging responsive under load.
On the database question, teams often assume a fleet in the thousands automatically demands a separate PostgreSQL or MySQL server. RustDesk Server Pro does not work that way: it ships with a built-in SQLite database that stays simple and holds up well into the thousands of devices. SSD storage matters because it keeps that database and its logging responsive under load; scale the host's CPU, RAM, and relay bandwidth rather than the database engine.
The practical takeaway: size for concurrency and network, not headcount. If you expect an unusually high ratio of simultaneous active sessions, or heavy reliance on relay because peer-to-peer is blocked in your network, plan for more CPU and bandwidth and confirm your OS limits are raised. For larger fleets or unusual edge cases, validate your sizing assumptions with RustDesk at [rustdesk.com](https://rustdesk.com).
## Who asks this
This comes from IT admins, [MSPs](/blog/rustdesk-for-msps), and enterprises standing up self-hosted RustDesk Server Pro for large fleets — frequently teams migrating off TeamViewer or AnyDesk who have just become Pro customers and are sizing infrastructure before rollout. It's a recurring question from organizations managing thousands to tens of thousands of endpoints who need to right-size a server without guesswork.
Capacity planners speccing a Server Pro host before rollout are the usual askers — infrastructure teams at enterprises and [MSPs](/blog/rustdesk-for-msps) that have just licensed a large fleet. It's a recurring question from organizations managing thousands to tens of thousands of endpoints who need to right-size a server without guesswork.
## Related questions
v3/src/content/post/en/self-hosted-teamviewer-alternative.md
+11 -15
View File
@@ -15,11 +15,11 @@ tags:
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."
answer: "RustDesk Server Pro is self-hosted by design — the ID/rendezvous server, relay, console, and stored data run on infrastructure you control — and RustDesk 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.'
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 are prorated. 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?'
@@ -30,7 +30,7 @@ metadata:
keywords: 'self-hosted TeamViewer alternative, TeamViewer replacement, open source TeamViewer alternative'
---
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.
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.
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.
@@ -38,7 +38,7 @@ If you're one of them, this page is for you: why teams leave TeamViewer, how a s
Two decision factors show up repeatedly.
**Cost.** Compare the current renewal quote with alternatives using the same user, device, concurrency, feature, and support requirements.
**Cost.** Renewal totals can grow independent of usage — tier packaging, add-ons, and rate changes all move the number. Compare the current quote with alternatives against identical requirements.
**Control.** With a cloud-only tool, your session traffic and your device list live on a vendor's infrastructure. For a growing number of teams — especially in healthcare, the public sector, and anywhere [GDPR](/blog/remote-desktop-data-sovereignty-gdpr) applies — choosing where the server-side data and relay layer run is a hard requirement, not a preference.
@@ -48,7 +48,7 @@ A **self-hosted TeamViewer alternative** answers both: you own the infrastructur
RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-desktop-software). 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.
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.
Underneath, RustDesk 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.
@@ -61,19 +61,19 @@ It's also the reason security incidents in this category — such as [AnyDesk's
| 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](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 |
| Try before you buy | Vendor trial (see vendor page) | Free server today, or Pro evaluation via sales@rustdesk.com |
_Competitor details vary by plan — confirm current TeamViewer terms with the vendor. [See RustDesk pricing](https://rustdesk.com/pricing)._
## Predictable licensing, no per-channel tax
RustDesk licenses per login-user plus per managed-device. **Standard plans include unlimited concurrent connections; Customized V2 has a defined allowance.** Mid-term upgrades may be prorated under current terms. Model all three counts against the current pricing page.
RustDesk licenses per login-user plus per managed-device. **Standard plans include unlimited concurrent connections; Customized V2 has a defined allowance.** Mid-term upgrades are prorated. Model all three counts against the current pricing page.
That maps cleanly onto login-users and managed-devices whether you are a small support team or a larger IT operation. It also scales well beyond a starter deployment: [large-fleet planning](/blog/rustdesk-scale-50000-200000-devices) starts around 50,000 managed devices today, with larger estates requiring validation around caching, database tuning, and rollout design.
That maps cleanly onto how support teams actually grow. It also scales well beyond a starter deployment: [large-fleet planning](/blog/rustdesk-scale-50000-200000-devices) starts around 50,000 managed devices today, with larger estates requiring validation around caching, database tuning, and rollout design.
## Your data stays where you put it
Because you host the servers, you control the rendezvous, relay, console, and stored device data. Direct connections still flow between endpoints, so self-hosting alone does not guarantee in-country traffic or GDPR compliance.
Because you host the servers, the server-side services and everything they store are genuinely yours: rendezvous, relay, console, and the device list all run where you decide, under access rules you set. The caveat is endpoint routing — direct connections still flow between endpoints, so self-hosting alone does not guarantee in-country traffic or GDPR compliance.
## Built for MSPs and IT teams
@@ -100,10 +100,6 @@ This sequence prevents a licensing decision from turning into an untested infras
## Evaluate the switch on your own infrastructure
You don't need to talk to anyone to evaluate RustDesk:
You don't need to talk to anyone to get started: the free, open-source community server installs on your own hardware and runs indefinitely. To trial the Pro features against the migration plan above, ask [sales@rustdesk.com](mailto:sales@rustdesk.com) for the evaluation terms currently on offer; standard plan rates live at [rustdesk.com/pricing](https://rustdesk.com/pricing). And if you want to watch it work before installing anything, the [video demo](/blog/see-rustdesk-in-action) covers a full session end to end.
- **Self-host the free, open-source community server today** and see how it runs on your own hardware.
- **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 a proof of concept on your own hardware.
Leaving TeamViewer usually comes down to cost and control; the quickest way to know whether self-hosting delivers both is a short proof of concept on your own hardware.
v3/src/content/post/en/teamviewer-commercial-use-detected.md
+5 -5
View File
@@ -18,7 +18,7 @@ faq:
- 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.'
answer: 'No. A reset clears the flag only when it was raised in error; if your actual usage is commercial, TeamViewer will correctly identify it, and the lasting fix is software whose license covers that work.'
- 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?'
@@ -39,11 +39,11 @@ 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.
3. **Briefly describe your actual usage pattern** — e.g. "I only use this to help my elderly parent with their PC." Write it in your own words and keep it truthful.
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 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.
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. From there, the review ends one of two ways: TeamViewer resets your ID because personal use is confirmed, or it declines the reset and offers you a "declaration of private use" to sign instead. If your actual usage is commercial, neither outcome changes that — a reset request can only clear a flag that was raised in error.
### What actually counts as "commercial use" here
@@ -55,7 +55,7 @@ Per TeamViewer's own definitions, **personal use** means helping family and frie
- Server administration or monitoring
- Salaried work at a non-profit organization
If you're doing any of that, the appeal process will correctly identify you as commercial, and the real fix is choosing a tool licensed for how you actually use it — which is where the rest of this guide picks up.
If you're doing any of that, the appeal process will correctly identify you as commercial, and the lasting solution is software whose license actually covers your work — which is where the rest of this guide picks up.
## Why TeamViewer flags "commercial use" in the first place
@@ -81,7 +81,7 @@ RustDesk belongs in the third row. Its community server can be self-hosted witho
Do not uninstall TeamViewer as the first step. Stand up a test RustDesk server and validate the workflows behind your commercial usage: attended and unattended access, elevation, file transfer, multi-monitor, client deployment, access restrictions, and relay performance. Then compare the operating cost with the current TeamViewer quote.
The [self-hosted TeamViewer alternative guide](/blog/self-hosted-teamviewer-alternative) covers the full migration and feature comparison. If you only need personal access and TeamViewer approves the reset, keeping the free tier may be simpler than running a server.
The [self-hosted TeamViewer alternative guide](/blog/self-hosted-teamviewer-alternative) covers the full migration and feature comparison. If the reset is approved, your free personal-use access continues. If any of your use is commercial, licensing is the durable fix — either TeamViewer's paid tier or a tool licensed for how you work.
## What to do next
v3/src/content/post/en/teamviewer-too-expensive-alternatives.md
+11 -26
View File
@@ -30,21 +30,17 @@ metadata:
keywords: 'TeamViewer too expensive, TeamViewer renewal cost, TeamViewer three-year TCO, TeamViewer cost alternatives'
---
## "TeamViewer Too Expensive?" You're Not Alone
## 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 what running it involves.
If **TeamViewer feels too expensive**, it usually isn't because you're using more — tier-and-seat pricing can climb whether or not you grow. 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
Cloud-subscription remote-desktop tools are priced around tiers, seats, and add-on modules. A renewal may change when your requirements, plan packaging, discounts, or vendor rates change. You're renting access to a vendor's cloud, so compare the dated renewal quote with current alternatives rather than assuming a universal increase.
Cloud-subscription remote-desktop tools are priced around tiers, seats, and add-on modules, and each of those is a lever that can move at renewal. Tier boundaries do the most damage: outgrow a single allowance and the whole plan re-prices, not just the feature that pushed you over. Add-on modules and expiring introductory discounts move the total the rest of the way, one line item at a time.
Renewal changes can motivate a comparison, but the correct plan depends on your current workload. Model the decision from official pricing and feature matrices.
The frustration isn't the software. It's the model. So the real question isn't "what's a cheaper cloud tool" — it's "what pricing model stops surprising me."
None of that requires you to use the product more — which is why the frustration isn't the software, it's the model. The real question isn't "what's a cheaper cloud tool" — it's "what pricing model stops surprising me." (How to decompose your own renewal quote is covered below.)
## The core fix: own the infrastructure, pay per user + per device
@@ -65,9 +61,7 @@ You can also [upgrade any time](/blog/upgrade-rustdesk-license-mid-subscription)
| Concurrent sessions | Often capped by plan | Unlimited on standard plans; limited on Customized V2 |
| Server-side services and data | Vendor-operated | Operated on infrastructure you control |
| Source code | Closed | [Open source (AGPL)](/blog/case-for-open-source-remote-access) — auditable |
| Try before you buy | Often needs a sales call | Free community server, or Pro trial on request |
For exact competitor pricing and current plan details, check each vendor's own page — we don't quote numbers we can't stand behind.
| Try before you buy | Often needs a sales call | Free community server; ask sales about evaluation terms |
## What to extract from the renewal quote
@@ -92,11 +86,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 — hardware requirements are low, so this is a small, predictable line item
- A VPS or on-prem host to run the ID/rendezvous and relay servers
- 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
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.
Self-hosting has a cost too — the host and the setup time above — but 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
@@ -107,27 +101,18 @@ 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 running the server yourself — more on that below.
## You can prove the savings before you pay
One reason renewal sticker-shock stings is that switching feels risky. RustDesk removes the leap of faith: you can **self-host the free, open-source community server today**, or email [sales@rustdesk.com](mailto:sales@rustdesk.com) for current evaluation terms for the Pro features. Prefer to watch first? There's a full [video walkthrough](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
Use a trial or proof of concept to validate the cost model and operational fit on your own hardware before purchasing an annual license.
What you take on instead is running the server yourself — the ops line items in the TCO breakdown above are the whole list.
## It scales, and it consolidates
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 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.
Part of a TeamViewer bill is often a second tool doing overlapping work — a separate unattended-access product, a support add-on, an extra console. Consolidating onto one self-hosted deployment can retire those line items, provided you validate access-control and SSO requirements against the current plan matrix (custom client generation and identity features are available from the Basic plan and up). And the model does not top out early: RustDesk publishes [large-fleet planning guidance](/blog/rustdesk-scale-50000-200000-devices) for sizing well beyond a starter deployment.
## The cost lands where you control it
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
## Prove the savings before you pay
- Stand up the **free, open-source community server** and connect your first devices — no cost, no sales call.
- **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.
Renewal sticker-shock stings partly because switching feels risky, so remove the leap of faith: stand up the free, open-source community server, connect your first devices, and validate the cost model and the operational fit on your own hardware before any money moves. When you are ready to test the Pro features, [sales@rustdesk.com](mailto:sales@rustdesk.com) can quote the current evaluation terms — standard plan rates are at [rustdesk.com/pricing](https://rustdesk.com/pricing).
Prove the cost model on your own infrastructure, then decide.
v3/src/content/post/en/teamviewer-vs-anydesk-for-msps.md
+5 -7
View File
@@ -38,13 +38,11 @@ MSPs sometimes inherit a mix of TeamViewer, AnyDesk, and RDP across clients. Thi
| Best fit | Service desks needing policy controls, reporting, and integrations | Teams prioritizing a compact client, connection performance, and branding |
| Hosting | Managed cloud plans | Managed cloud on standard tiers; Ultimate advertises cloud or on-premises deployment |
Treat the pricing rows as dated, since both vendors reprice often.
## Licensing: the real difference is what you're metered on
TeamViewer packages named users and concurrent-session capacity into tiers. Buyers should compare the complete written quote, including add-ons, with their actual workload.
TeamViewer packages named users and concurrent-session capacity into tiers, with add-ons layered on top.
AnyDesk plan packaging and renewal terms can change. Its [official pricing page](https://anydesk.com/en/pricing), checked July 7, 2026, lists Solo with one user and one connection, Standard with up to 20 users and one included connection, and Advanced with up to 100 users and two included connections; managed-device and connection add-on limits vary by plan. Compare that page and a dated written quote against the exact users, concurrent sessions, managed endpoints, and features your MSP requires. Do not base a purchase on another customer's legacy contract. Security review should be separate from price review; the [2024 incident](https://anydesk.com/en/public-statement) belongs in the vendor-risk assessment, not as proof that one licensing model is better.
AnyDesk plan packaging and renewal terms can change. Its [official pricing page](https://anydesk.com/en/pricing), checked July 7, 2026, lists Solo with one user and one connection, Standard with up to 20 users and one included connection, and Advanced with up to 100 users and two included connections; managed-device and connection add-on limits vary by plan. Compare that page and a dated written quote against the exact users, concurrent sessions, managed endpoints, and features your MSP requires. Do not base a purchase on another customer's legacy contract. AnyDesk's [2024 incident](https://anydesk.com/en/public-statement) belongs in the vendor-risk assessment alongside this licensing review.
## Where each one actually fits
@@ -56,13 +54,13 @@ Neither vendor is going to solve the thing a lot of MSPs actually want, though:
## Why some MSPs look past both
This is the part where RustDesk makes its case, so read it as vendor-authored commentary.
From here down you are reading the maker's case — we build RustDesk — so weigh these points accordingly.
**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.
**Open source you can audit.** The client is AGPL-licensed — inspect it, build it yourself, run the free community server indefinitely. That's a structurally different trust model than a closed-source client whose licensing terms you don't control.
**Open source you can audit.** RustDesk is AGPL-licensed — inspect it, build it yourself, run the free community server indefinitely. That's a structurally different trust model than a closed-source client whose licensing terms you don't control.
**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.
@@ -72,4 +70,4 @@ Both of these live in someone else's cloud. Self-hosting RustDesk is the other m
## Try it
Self-host the free community server today. 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).
Testing the claim costs nothing: self-host the free community server against one real client site and see how it holds up. When you are ready to look at the Pro features, [sales@rustdesk.com](mailto:sales@rustdesk.com) can share current evaluation terms, and plan rates are published at [rustdesk.com/pricing](https://rustdesk.com/pricing).
v3/src/content/post/en/teamviewer-vs-splashtop.md
+5 -5
View File
@@ -33,7 +33,7 @@ TeamViewer and Splashtop both cover remote access and support, but the right com
| Published plans | Business, Premium, Corporate, and enterprise offerings; features and session capacity vary by plan | Remote Access Solo, Pro, Performance, and Enterprise; Remote Support uses separate packaging |
| Deployment model | Vendor-operated service | Vendor-operated SaaS plans; a separately licensed On-Prem product is available for enterprise deployments |
| Administration | Policy controls, reporting, mass deployment, and enterprise integrations vary by edition | Roles, access management, and session recording on relevant plans; SSO, granular controls, SIEM, and other controls are concentrated in Enterprise |
| Performance | Test relay routing, responsiveness, audio, and multi-monitor workflows on representative networks | Performance advertises 4:4:4 color, high-fidelity audio, and up to 240 FPS; validate those workflows on the endpoints and networks you will actually use |
| Performance | Managed relay network; no published fps/color-depth claims | Performance advertises 4:4:4 color, high-fidelity audio, and up to 240 FPS; validate those workflows on the endpoints and networks you will actually use |
| Buying fit | Teams that value a mature managed service, structured administration, and broad integrations | Individuals and teams comparing lower published entry tiers, multimedia features, or a separately quoted On-Prem deployment |
| Source model | Proprietary | Proprietary |
@@ -79,7 +79,7 @@ Record connection time, interaction latency, image quality, failure rate, and te
Security claims need dates and boundaries. Splashtop's [September 18, 2025 announcement](https://www.splashtop.com/press/splashtop-achieves-iso-iec-27001-2022-certification) reports ISO/IEC 27001:2022 certification, while its current [security page](https://www.splashtop.com/security) lists SOC 2, TLS 1.2, and 256-bit AES session protection. Certification does not prove an absence of incidents: on June 30, 2026, Splashtop [disclosed a third-party Klue incident](https://www.splashtop.com/blog/security-update-third-party-klue-incident) that it says did not affect Splashtop products or services.
TeamViewer's current [Trust Center](https://www.teamviewer.com/en/resources/trust-center/) lists SOC 2/SOC 3 and ISO/IEC 27001, and its [technical security overview](https://teamviewer.scene7.com/is/content/teamviewergmbh/teamviewer/central-image-hub/pdf/en/teamviewer-security-technical-overview-en.pdf) documents current architecture and encryption. TeamViewer's [TV-2024-1005 incident bulletin](https://www.teamviewer.com/en/resources/trust-center/security-bulletins/tv-2024-1005/) says the June 2024 attack was contained to its internal corporate IT environment and did not affect the product environment, connectivity platform, or customer data. These are dated vendor disclosures, not an unbounded claim that either company has never had a breach.
TeamViewer's current [Trust Center](https://www.teamviewer.com/en/resources/trust-center/) lists SOC 2/SOC 3 and ISO/IEC 27001, and its [technical security overview](https://teamviewer.scene7.com/is/content/teamviewergmbh/teamviewer/central-image-hub/pdf/en/teamviewer-security-technical-overview-en.pdf) documents current architecture and encryption. TeamViewer's [TV-2024-1005 incident bulletin](https://www.teamviewer.com/en/resources/trust-center/security-bulletins/tv-2024-1005/) says the June 2024 attack was contained to its internal corporate IT environment and did not affect the product environment, connectivity platform, or customer data. Both are vendor statements — verify against current disclosures.
## Where each product fits
@@ -91,13 +91,13 @@ The decision changes when infrastructure control, source visibility, or a differ
## Why some teams also evaluate RustDesk
This is where we make RustDesk's case plainly, so read it as that.
Cards on the table: RustDesk is our product, and this section explains why it belongs on this particular shortlist.
**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.
**Open-source client and community server.** RustDesk's core client and free server are AGPL-licensed, so teams can inspect the code and evaluate basic self-hosting before buying Server Pro. TeamViewer and Splashtop are proprietary products.
**Open source.** RustDesk's core client and free server are AGPL-licensed, so teams can inspect the code and evaluate basic self-hosting before buying Server Pro. TeamViewer and Splashtop are proprietary products.
**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).
@@ -107,4 +107,4 @@ Between two SaaS products sits the option neither sells: run the coordination yo
## Try it
Self-host the free community server today. 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).
The free community server runs for as long as you like at no cost. If the Pro features are the deciding factor, email [sales@rustdesk.com](mailto:sales@rustdesk.com) for current evaluation terms; plan details are at [rustdesk.com/pricing](https://rustdesk.com/pricing), and the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk) has a walkthrough if you want to see it running before installing anything.
v3/src/content/post/en/upgrade-rustdesk-license-mid-subscription.md
+5 -5
View File
@@ -27,7 +27,7 @@ faq:
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: '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.'
description: 'Upgrade your RustDesk license anytime to add users or devices, prorated. Refresh in the web console for instant effect, or it applies 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'
---
@@ -41,7 +41,7 @@ You do not have to wait for renewal to scale up. RustDesk lets you upgrade your
RustDesk licensing is structured around per-user and per-device seats, and a growing IT team or [MSP](/blog/rustdesk-for-msps) will naturally hit the point where more devices or users need coverage. Rather than forcing you to buy a whole new subscription or wait for the annual renewal date, RustDesk treats the upgrade as an in-place change to your existing license.
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.
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. The prorated charge is easy to verify against your remaining term.
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.
@@ -51,12 +51,12 @@ For teams migrating from TeamViewer or AnyDesk, this flexibility is a meaningful
## Who asks this
This question comes up most often from IT admins and MSPs who bought a license sized for their current fleet and are now onboarding new endpoints, staff, or client sites partway through the year. The concern behind it is usually twofold: whether scaling up is even possible mid-term, and whether they will be fairly charged for it.
Growth is the usual trigger: an admin who sized the license for the fleet as it stood is now onboarding new endpoints, staff, or client sites partway through the year. The concern behind it is usually twofold: whether scaling up is even possible mid-term, and whether they will be fairly charged for it.
## Related questions
- [How is the upgrade cost prorated for the remaining time on my subscription?](/blog/rustdesk-pro-license-cost-how-to-pay)
- [How does RustDesk count users and managed devices for a license?](/blog/what-counts-as-a-managed-device)
- [How do I manually refresh my license in the web console?](/blog/rustdesk-web-console-custom-client-generator-port-21114)
- [What is the difference between per-user and per-device licensing in RustDesk?](/blog/what-counts-as-a-managed-device)
Growing your deployment? Upgrade your license whenever you need more capacity, then refresh it in the web console—and double-check the prorated amount against your remaining term if you want to confirm the numbers.
Growing your deployment? Upgrade your license whenever you need more capacity, then refresh it in the web console to put the new limits to work right away.
v3/src/content/post/en/what-counts-as-a-managed-device.md
+7 -9
View File
@@ -23,8 +23,8 @@ faq:
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: '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'
description: 'How RustDesk counts managed devices: standard plans count every reachable device once; Customized V2 counts only devices assigned to a group or user.'
keywords: 'what counts as a managed device, rustdesk device counting, rustdesk vs teamviewer licensing, unattended vs attended device license, rustdesk ad-hoc support, msp remote support licensing'
---
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.
@@ -37,26 +37,24 @@ On standard plans, a "managed device" is any machine you want to be able to reac
- whether you'll connect **once** or **many times**,
- how frequently you access it.
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.
If your work is largely spontaneous, one-off support, the narrower **[Customized V2](https://rustdesk.com/pricing#custom2)** counting covered below is designed for exactly that case.
## In detail
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.
On standard plans, 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 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 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).
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. For endpoints that are truly one-time support calls, the Customized V2 rule above applies; current allowances are at [rustdesk.com/pricing](https://rustdesk.com/pricing).
## Who asks this
This comes up from **MSPs and internal IT teams migrating off TeamViewer or AnyDesk**, where different licensing units make comparisons confusing. RustDesk paid plans require capacity for both the people who log in and the devices kept under management.
Anyone translating a TeamViewer or AnyDesk seat count into RustDesk's units hits this definition first, because the licensing units do not map one-to-one. RustDesk paid plans require capacity for both the people who log in and the devices kept under management.
## Related questions
- [Does RustDesk license per user, per device, or both?](/blog/rustdesk-pro-license-cost-how-to-pay)
- Do [concurrent connections](/blog/rustdesk-concurrent-connections-limit) to the same device count more than once?
- [Do concurrent connections to the same device count more than once?](/blog/rustdesk-concurrent-connections-limit)
- [How do I count devices for a self-hosted RustDesk Server Pro deployment?](/blog/rustdesk-custom-quote-minimum-users-invoice-fees)
- [Coming from TeamViewer — how does RustDesk's pricing compare for MSPs?](/blog/rustdesk-vs-teamviewer)
v3/src/content/post/en/why-self-host-remote-desktop-software.md
+6 -6
View File
@@ -28,7 +28,7 @@ metadata:
keywords: 'why self-host remote desktop, self-hosted remote desktop benefits, on-premise remote access, remote desktop without vendor cloud'
---
Self-hosting is often evaluated when organizations want more control over price, features, and infrastructure. This article focuses on those structural trade-offs.
Most remote-desktop tools are sold one way: as a cloud subscription, with the vendor's servers brokering — and often relaying — every session.
There is another way to run remote access, and it is not new — it is just less marketed, because it doesn't come with a recurring cloud subscription attached. It's the decision to **self-host your remote desktop software**: run the server that coordinates connections and relays traffic when direct connectivity fails on infrastructure you control. This article makes the case for that model and uses RustDesk as the concrete example.
@@ -36,7 +36,7 @@ There is another way to run remote access, and it is not new — it is just less
Most mainstream remote-support tools are cloud-only. When your technician connects to a client's PC, the session is coordinated — and often relayed — through the vendor's servers. That's convenient. It also means your device list, your connection metadata, and sometimes your session traffic pass through a third party, on their uptime, under their pricing, subject to their security posture.
Self-hosting flips that. With RustDesk Server Pro, the ID/rendezvous server, relay, console, and stored deployment data run on **your infrastructure**. Direct sessions still flow between endpoints; relayed sessions use your configured relay. The core client is [open source (AGPL)](/blog/case-for-open-source-remote-access) and the free community server runs indefinitely—the auditability argument for that is [its own topic](/blog/case-for-open-source-remote-access); this piece stays on the self-hosting decision itself.
Self-hosting flips that. With RustDesk Server Pro, the ID/rendezvous server, relay, console, and stored deployment data run on **your infrastructure**. Direct sessions still flow between endpoints; relayed sessions use your configured relay. RustDesk is [open source (AGPL)](/blog/case-for-open-source-remote-access) and the free community server runs indefinitely — the auditability argument for that is its own topic; this piece stays on the self-hosting decision itself.
## Four reasons the self-hosted model wins
@@ -72,7 +72,7 @@ Self-hosting doesn't mean giving up scale or capability. RustDesk publishes [lar
## Own the server, own the outcome
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.
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
@@ -89,8 +89,8 @@ None of this is exotic, and most of it is one-time setup. If a question comes up
## How to evaluate self-hosting
- **Self-host the free open-source community server today.** The core is AGPL — deploy it, audit it, and run it indefinitely at no cost.
- **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.
- **Start with the community server.** The core is AGPL — deploy the free open-source server this afternoon, audit it, and run it for as long as you like at no cost.
- **Need the Pro feature set?** Current plan rates are at [rustdesk.com/pricing](https://rustdesk.com/pricing), and [sales@rustdesk.com](mailto:sales@rustdesk.com) can tell you which evaluation options exist right now.
- **Rather watch than install?** There's a full [video demo](/blog/see-rustdesk-in-action) on the [RustDesk YouTube channel](https://www.youtube.com/@rustdesk).
If price hikes, closed code, or a cloud you don't control are what pushed you to start shopping, self-hosting is the structural fix, not a discount. Own the server, own the data, own the cost.
v3/src/content/post/en/zoho-assist-alternative-self-hosted.md
+11 -17
View File
@@ -4,7 +4,7 @@ lang: en
translationKey: zoho-assist-alternative-self-hosted
draft: false
title: 'Zoho Assist Alternative: Self-Hosted and Open Source'
excerpt: 'Looking for a self-hosted Zoho Assist alternative? See how RustDesk compares on hosting, open source, and licensing — plus an honest look at the trade-offs.'
excerpt: 'Looking for a self-hosted Zoho Assist alternative? See how RustDesk compares on hosting, open source, and licensing — trade-offs included.'
image: ~/assets/images/blog/zoho-assist-alternative-self-hosted-og.png
category: Alternatives
tags:
@@ -15,15 +15,15 @@ tags:
author: RustDesk Team
faq:
- question: 'Is there a self-hosted alternative to Zoho Assist?'
answer: "Yes. Zoho Assist is a cloud-based SaaS, so sessions are brokered through Zoho's infrastructure. RustDesk is self-hosted by design: you run the ID/rendezvous and relay servers on your own machine or VPS, so session brokering and your device list stay on infrastructure you control. The RustDesk client is also open source under the AGPL, which Zoho Assist is not."
answer: "Yes. Zoho Assist is a cloud-based SaaS, so sessions are brokered through Zoho's infrastructure. RustDesk is self-hosted by design: you run the ID/rendezvous and relay servers on your own machine or VPS, so session brokering and your device list stay on infrastructure you control. RustDesk is also open source under the AGPL, which Zoho Assist is not."
- question: 'How is RustDesk licensed compared to Zoho Assist?'
answer: 'Zoho Assist generally meters remote support per technician and unattended access per computer through a cloud subscription. RustDesk Server Pro is licensed per login-user plus per managed-device, hosted on your own server. There is no per-technician cloud metering layered on top. For current per-unit rates, see rustdesk.com/pricing.'
- question: 'Does RustDesk let me rebrand the client like Zoho Assist?'
answer: "Yes. RustDesk Pro includes a custom-branded client generator, so you can ship a preconfigured installer with your own name and logo. Zoho Assist also offers rebranding on its cloud plans. The difference is where everything runs: RustDesk's branded client points at your self-hosted server, not a vendor cloud."
answer: "Yes. RustDesk Pro includes a custom-branded client generator on Basic and higher plans, so you can ship a preconfigured installer with your own name and logo. Zoho Assist also offers rebranding on its cloud plans. The difference is where everything runs: RustDesk's branded client points at your self-hosted server, not a vendor cloud."
- question: 'What is the catch with a self-hosted Zoho Assist alternative?'
answer: 'Someone on your side has to run the server. You provision a host, open ports, set up TLS, and keep it patched. Zoho Assist is a mature managed SaaS with a large ecosystem and zero server maintenance, and that convenience is real. Self-hosting trades that convenience for control and auditability.'
answer: 'Someone on your side has to run the server. You provision a host, open ports, set up TLS, and keep it patched. Zoho Assist is a managed SaaS with no server of your own to run; self-hosting trades that convenience for control and auditability.'
metadata:
description: 'A self-hosted Zoho Assist alternative: RustDesk is open-source, runs on your own server, and licenses per login-user and per managed-device. See the comparison.'
description: 'Zoho Assist alternative you can self-host: RustDesk pairs open-source software with your own server and per login-user, per managed-device licensing.'
keywords: 'Zoho Assist alternative, self-hosted Zoho Assist alternative, open source Zoho Assist alternative, RustDesk vs Zoho Assist, self-hosted remote support, on-premise remote support software'
---
@@ -37,13 +37,13 @@ Credit where it is due. Zoho Assist is [cloud-based](https://www.zoho.com/assist
For many teams that is exactly the right call. The reason people go looking for an alternative is usually one of two things: they want their session data and brokering on their _own_ servers, or they want to get out of a per-technician cloud subscription model.
## The core difference: you host it, you own it
## What changes when you self-host
Zoho Assist is a SaaS. Your sessions are brokered through Zoho's cloud, on Zoho's terms, and your device list lives there too. That is convenient, and for regulated teams or anyone with strict [data-sovereignty](/blog/remote-desktop-data-sovereignty-gdpr) requirements, it is also the sticking point.
RustDesk flips the model. **RustDesk Server Pro is [self-hosted by design](/blog/why-self-host-remote-desktop-software)** — 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.
And **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](/blog/open-source-remote-desktop-software) indefinitely. Zoho Assist is a proprietary, closed product. That is a different trust model: you do not have to take a vendor's word for what the software does, because you can look.
And **RustDesk 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](/blog/open-source-remote-desktop-software) indefinitely. Zoho Assist is a proprietary, closed product. That is a different trust model: you do not have to take a vendor's word for what the software does, because you can look.
## Zoho Assist vs. RustDesk at a glance
@@ -54,7 +54,7 @@ And **RustDesk's core client is [open source under the AGPL](/blog/case-for-open
| 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](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) |
| Custom branding | Yes, on cloud plans | Yes — [self-hosted client generator](/blog/rustdesk-web-console-custom-client-generator-port-21114) (Basic plan and up) |
| Server maintenance | None (Zoho runs it) | Yours to run |
_Zoho Assist plan details and pricing vary by tier and change over time — confirm current terms on [Zoho's pricing page](https://www.zoho.com/assist/pricing.html). For RustDesk rates, see [rustdesk.com/pricing](https://rustdesk.com/pricing)._
@@ -71,14 +71,8 @@ Self-hosting does not mean going without the tooling a support desk expects. Rus
## Off Zoho's cloud, onto your server
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.
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 open-source software you can inspect. That is the trade a SaaS cannot make.
## Evaluate it on your own infrastructure
## Pilot it before the next renewal
You don't need a sales call to find out whether this fits:
- **Self-host the free, open-source community server today** — no cost, no expiry — and see how it runs on your own hardware.
- **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 a short pilot before you renew.
Spin up the free, open-source community server on a spare VM and run a week of real support sessions through it — there is no cost and no time limit. If the self-hosted model fits your workflow, [sales@rustdesk.com](mailto:sales@rustdesk.com) can share the current Pro evaluation terms, and the per-user and per-device rates are at [rustdesk.com/pricing](https://rustdesk.com/pricing). That is a decision you can make from evidence, before the next Zoho Assist invoice arrives.