RustDesk Server Pro

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Purslane Tech Pte. Ltd. · rustdesk.com

Compare with Getscreen.me → Report an error on this page Is this your product? →

Link to this page

RustDesk Server Pro: AI-assisted analysis on whats-best.ai RustDesk Server Pro: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

RustDesk Server Pro at a glance

Vendor
Purslane Tech Pte. Ltd.
Headquarters
Incorporated in Singapore source, captured 6 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 6 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 6 Nov 2026
Panel verdict
The AI panel rates RustDesk Server Pro 3/5, the mean of 6 judges. RustDesk Server Pro, from Purslane Tech Pte. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

RustDesk Server Pro alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

RustDesk Server Pro, from Purslane Tech Pte. Ltd., is a self-hosted remote desktop and remote support product. Security and reliability and pricing transparency score highest, both at 7 to 7: NaCl-based end-to-end encryption with a self-hosted relay, per-user two-factor enforcement and exportable audit logs with configurable retention sit alongside published plans — an individual plan at $11.88 and a customized plan at $23.88 per month USD billed annually, the latter with $1.20 for each additional user and $0.12 for each additional device — on a one-year prepaid per-server licence with no auto-renewal. Unattended access scores 6 to 7 on scripted deployment and a custom client generator. Support workflow is the weakness at 4 to 5: branding and connection notes are documented, but the pages show no public information on session queues, helpdesk or ITSM integrations, or per-technician reporting. Sovereignty splits, 5 to 7: some judges credit self-hosting that keeps the session chain on the buyer's own infrastructure, while others weigh the Singapore contracting entity and governing law, subprocessor locations not stated, and no public information on a published data processing agreement.

Report an error

Speaks for it

  • Scripted fleet deployment by PowerShell, batch, MSI and bash, with a custom client generator that embeds server settings
  • NaCl-based end-to-end encryption with the relay running on your own infrastructure
  • CSV-exportable audit logs with configurable retention that can keep records indefinitely
  • Admin roles in Global, Group Scoped and Individual scopes, OpenID Connect single sign-on, and API tokens with permission scopes
  • Managed-service use expressly permitted where the licence covers the customers' devices and users

Report an error

Held against it

  • No public information on session queues, helpdesk or ITSM integrations, or per-technician and per-customer reports
  • No public information on session recording, ISO 27001 or SOC 2 certification, a status page or an SLA
  • Licence provides support and maintenance at the vendor's sole discretion under separate agreement
  • Web console ships with default administrator credentials (admin/test1234) that the documentation says to change immediately
  • No public information on VAT treatment or renewal pricing, and a trial licence is available only by contact

Report an error

Best for

  • You need the relay, web console and logs to run on your own infrastructure
  • You are an MSP or internal IT team rolling out unattended access to a device fleet by script
  • You want published per-user and per-device pricing on a one-year prepaid term with no auto-renewal
  • Your team signs in through Azure, Okta or Google and wants single sign-on for the remote tool

Report an error

Avoid if

  • You run a service desk that depends on session queues, routing and helpdesk or ITSM integrations
  • You must control iOS devices, for which screen sharing is stated as not yet supported
  • You need a contractual support commitment rather than support at the vendor's sole discretion
  • Your procurement requires a European contracting entity and governing law

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Remote control & attended support sessions

Show reasoning
How this is scored

What a technician can do in a session with a user who is present: starting a session from a code, link or small support client without admin rights, viewing and controlling the screen with good image quality at low bandwidth, multi-monitor switching, file transfer, clipboard, chat and voice, remote reboot with automatic reconnect, running as administrator and crossing UAC or elevation prompts, session handover to a colleague, whiteboard or annotation, screen sharing in the other direction, and which operating systems can be supported (Windows, macOS, Linux, iOS and Android, including control rather than only viewing of mobile devices).

0 — No remote control of another device; a meeting or chat tool with screen sharing only.

3 — Screen viewing and control of Windows or macOS with a session code; file transfer, reboot and reconnect, elevation and mobile support are basic or not described.

5 — Attended sessions by code or link with a support client that needs no installation, Windows, macOS and Linux supported, multi-monitor, file transfer, chat, clipboard sync, reboot and reconnect, running with admin rights, and viewing or controlling Android or iOS devices described.

8 — Elevation across UAC documented, session handover and invitation of a second technician, annotation and voice, control of Android devices from named makers and iOS screen sharing, performance at low bandwidth and high resolution documented, and browser-based technician and user sides.

10 — A session that handles everything a help desk meets: every major platform including headless Linux, mobile and rugged devices, every session feature documented per platform with its limits, accessibility of the technician console, and quality and latency figures published.

Report an error

The IT Support Lead

All our platforms are covered (Windows, macOS, Linux, Android and a web client), and the Windows client needs no installation and can elevate privileges locally or from remote on demand. Chat, file transfer and clipboard copy/paste during remote desktop sessions are documented, and Android control is described down to input permissions; the captured mobile page states iOS does not yet support screen sharing, and we found no public information on session handover to a colleague, annotation or voice. 1 3 11 17

Report an error

The MSP Technician

Attended control runs on Windows, macOS, Linux, Android and a web client, with no installation or admin rights needed on Windows, privilege elevation on demand, chat, file transfer with paste, and terminal, camera and port connections; codecs (VP8/VP9/AV1, H264/H265) and detailed Android input control are documented. The captured pages state that iOS does not yet support screen sharing, and we found no public information on session handover, annotation, voice, or low-bandwidth and high-resolution performance figures. 1 3 10 11

Report an error

The Software Support Lead

Control of Windows, macOS, Linux and Android is documented, including a Windows client that needs no installation or admin rights and can elevate privilege from remote on demand — exactly the profile I need for four thousand non-IT practice users. It sits above the middle because the self-hostable web client, the codec list, chat, file transfer and separate Terminal and Port Transfer connection types are all documented, but we found no public information on session handover, annotation or voice, and the Android pages state that iOS does not yet support screen sharing, with no published performance figures. 1 3 4 7 10 11

Report an error

The Small Office Owner

The client works on Windows, macOS, Linux, Android and the web, needs no installation or admin rights on Windows, and can raise privileges remotely on demand; chat, file transfer with multi-select and paste, and full control of Android devices are documented. The pages do state that iOS does not yet support screen sharing, and we found no public information on session handover to a colleague, annotation, voice, or multi-monitor switching outside a Wayland preview. 3 10 11 1

Report an error

The Information Security Officer

Control of Windows, macOS, Linux and Android is documented with elevation on demand, file transfer, chat, terminal and camera connections, codec choices and a browser-based web client, and the pages state plainly that iOS does not yet support screen sharing. We found no public information on session handover to a second technician, annotation, or in-session voice, which a help desk will ask for. 3 11 10 1 7

Report an error

The Skeptic

The Windows client runs without installation or admin rights with privilege elevation locally or from the remote side on demand, and the client covers Windows, macOS, Linux, Android and a web client, with chat, file transfer including paste transfer, and terminal and camera-view connection types documented. Android input control with touch and mouse modes is described in detail, though iOS screen sharing is stated as not yet supported. We found no public information on session handover, annotation, voice, or published latency and bandwidth figures. 1 3 4 10 11

Report an error

Unattended access & device deployment

Show reasoning
How this is scored

How machines are reached when nobody sits at them: unattended agents for workstations and servers, mass deployment through MSI packages, group policy, Intune or other management tools, device lists and groups with search, tagging and an address book, wake-on-LAN, access to the login screen and after reboot, access to headless or terminal-only machines, remote command line and file manager without taking over the screen, connecting through proxies and restrictive firewalls, and a desktop or browser client for the person connecting, including remote work access to one's own office PC.

0 — No unattended access; every session needs a person at the remote device to accept it.

3 — An agent can be installed for unattended access with a password; deployment, groups, wake-on-LAN and access to servers are basic or not described.

5 — Unattended agents for Windows, macOS and Linux, deployment by MSI or a custom installer, device groups and an address book shared within the team, wake-on-LAN, access at the login screen and after reboot, and connection through proxies described.

8 — Mass deployment through group policy or an MDM documented with assignment to groups, background tools (command line, file manager, processes, services) without disturbing the user, access to headless servers, tagging and search over large device lists, and access for remote workers to their own office PC with its own policy.

10 — A fleet of thousands reachable and organised: zero-touch enrolment with naming and grouping rules, every background tool documented per platform, connection quality and device status visible across the fleet, and agent updates managed centrally with their rollout documented.

Report an error

The IT Support Lead

Rollout to my 400 machines is well documented: MSI or scripted deployment with PowerShell and bash, a custom client generator that bakes the server settings into the build, and device groups with tags and wildcard search. Terminal and file-transfer connection types let a technician work without taking over the screen, and unattended login-screen access after reboot is documented for Wayland in a preview; we found no public information on deployment through Intune or another MDM, wake-on-LAN, or connecting through restrictive proxies. 1 4 5 12 13 15

Report an error

The MSP Technician

This is the strong side for a fleet: scripted deployment with PowerShell, batch, bash and MSI, a custom client generator that bakes my server settings into the build, command-line bulk assignment of users, strategies, address books and device groups, plus tags, wildcard search and an offline-days filter over the device list. Terminal and file-transfer connections work without taking over the screen, and the Wayland preview adds login-screen access after reboot. We found no public information on wake-on-LAN, group-policy or MDM-based deployment, or headless server access. 1 5 12 13 15

Report an error

The Software Support Lead

Unattended access with a permanent password, deployment by MSI and by PowerShell, batch, bash and custom-client scripts, a custom client generator that packages server settings with preset address-book assignment, device groups with tags, wildcard search and bulk assignment, and Wayland access at the login screen after reboot are all documented. It stops short of the top because we found no public information on wake-on-LAN, connection through proxies, headless servers or rollout by group policy or an MDM. 1 5 11 12 13 15

Report an error

The Small Office Owner

Deployment is documented in real depth for my eleven-seat office: MSI or scripted install with PowerShell, batch, macOS bash and Linux, an API-token deploy command, and a custom client generator that packages the server settings into the build; devices sit in groups with tags, wildcard search, filters by days offline, and shared address books with saved passwords, plus a Terminal connection type that works without taking the screen. Access to the login screen after reboot is shown only for a Wayland preview, and we found no public information on wake-on-LAN, group policy or Intune rollout, headless machines, or proxy traversal. 12 13 15 4 1 5

Report an error

The Information Security Officer

Fleet-scale deployment is documented through MSI installers, PowerShell and bash scripts, a custom client generator embedding server settings, command-line assignment of users, strategies and device groups, and background terminal and file-transfer connections that need no screen takeover, with tagging and wildcard search. We found no public information on wake-on-LAN, process and service management, or enrolment through group policy or an MDM. 12 4 5 13 15 1

Report an error

The Skeptic

Large-scale deployment is documented through PowerShell, batch, MSI and bash scripts, a custom client generator that embeds server settings, command-line deployment and assignment of users, strategies, address books and device groups, and clients auto-register on first connection; terminal and file transfer run as separate connection types without taking the screen, and device tags with wildcard search and offline-day filtering are documented. We found no public information on wake-on-LAN, connection through proxies, headless server access, or group-policy and MDM rollout, and login-screen access after reboot is documented only for a Wayland preview. 1 4 5 12 13 15

Report an error

Support desk workflow, branding & reporting

Show reasoning
How this is scored

How a support team runs remote sessions as a service: session queues and routing to technicians or groups, a support request button or chat on the vendor's website, a support client and portal in the customer's own branding with its own domain, post-session surveys, session notes and summaries, integrations with helpdesk and ITSM tools (ServiceNow, Jira Service Management, Zendesk, Freshservice, HubSpot) that start sessions from a ticket and write the session back, reports per technician and customer, session duration for billing, and any AI assistance in sessions with its provider named.

0 — No way to organise sessions across technicians; each session is a one-off between two people.

3 — A session history and one or two integrations; queues, branding, surveys and reports are basic or not described.

5 — A custom-branded support client or portal, session history and reports per technician, session notes, one-click sessions from common helpdesk tools, and a way to queue or assign incoming support requests.

8 — Queues with routing to technician groups, a support button or chat for the vendor's own website, the support client under the customer's domain, post-session surveys, session data written back to the ticket, exportable reports for billing, and AI assistance with its model provider named.

10 — A support operation that needs no separate session tool: routing by skill and language, full white-label of every client and email, service-level reporting per customer, every integration documented with the data it writes, and AI features documented with data handling and an opt-out.

Report an error

The IT Support Lead

I can brand the client with my name, icon and logo, host the web client on my own domain, and have technicians add a note to a connection during or at the end of a session, with logs exportable as CSV. But for a service desk of six we found no public information on queues or routing of incoming requests, integrations that start a session from a ServiceNow, Jira or Zendesk ticket, or post-session surveys and per-technician reports. 1 4 17

Report an error

The MSP Technician

Branding is covered — a custom client with my name, icon and logo, plus a web client hosted on my own server and domain — and sessions can carry notes the controlling side writes during or at the end of a connection. We found no public information on session queues or routing, integrations with helpdesk and ITSM tools, post-session surveys, or per-technician and per-customer reports, which is the ticket-to-invoice link my service desk needs. 1 4 17

Report an error

The Software Support Lead

The branding piece is real for me: a custom client with our own name, icon and logo, a web client on our own domain, connection notes that can be prompted at the end of a session, and connection logs exportable as CSV are all documented. For a fourteen-agent desk like mine, though, we found no public information on session queues, a support button for our website, helpdesk or ITSM integrations that write the session back to the ticket, post-session surveys or per-technician reports, so the service layer around the sessions is thin on the captured pages. 1 4 15 17

Report an error

The Small Office Owner

I can brand the client with my firm's name, icon and logo, host the web client on my own domain, and keep connection notes plus CSV-exportable logs across connection, file, console and alarm sections. We found no public information on session queues or routing, helpdesk and ticketing integrations, post-session surveys, or per-technician reports for billing. 1 4 17

Report an error

The Information Security Officer

A custom-branded client carrying our own name, icon and logo can be generated from the web console, the web client can sit on our own domain, and connection notes plus CSV-exportable session history exist. We found no public information on queues or routing to technician groups, helpdesk integrations that start sessions from tickets, post-session surveys, or per-customer reporting for billing. 1 4 17

Report an error

The Skeptic

A custom client under the customer's own name, icon and logo, connection notes added during or at the end of a session, and connection, file, console and alarm logs with CSV export are documented. We found no public information on session queues or routing to technicians, a support button for the website, post-session surveys, helpdesk and ITSM integrations, or per-technician and per-customer reports, so a team running sessions as a service is left to organise itself. 1 11 17

Report an error

Administration, identity & API

Show reasoning
How this is scored

How the tool fits the company or the MSP: user and technician management with roles and granular permissions per device group, single sign-on (SAML or OpenID Connect) with Entra ID or Google, SCIM or directory sync, enforced two-factor authentication, central policies for agents (who may connect, when, with which features), multi-tenant customer separation for MSPs, a documented REST API and webhooks for users, devices and sessions, integrations with RMM, PSA and endpoint management tools, and licence management across seats, endpoints and concurrent sessions.

0 — No administration beyond a single login per technician.

3 — A web console to add technicians and see devices; roles, SSO, policies and the API are basic or not described.

5 — Technician roles and permissions per device group, two-factor authentication that can be enforced, single sign-on, central policies for agent settings, a documented API, and an integration with at least one RMM, PSA or endpoint management tool.

8 — SAML or OIDC single sign-on with SCIM or directory sync, conditional permissions by group and time, policies pushed to agents with lock-down of local settings, separate customer tenants for MSPs, an API covering users, devices, sessions and reports with webhooks, and integrations with named RMM, PSA and MDM products.

10 — Administration that scales across many companies: every setting reachable by API with parity stated, delegated administration per tenant, SSO and SCIM enforced across tenants, and the audit trail of every administrative change exportable to a SIEM.

Report an error

The IT Support Lead

Technicians can sign in with our Entra ID — Azure is among the named OpenID Connect providers — and admin roles come in global, group-scoped and individual flavours with granular permissions over users, devices, groups, logs and strategies, plus per-user two-factor enforcement. A scoped API token and Python command-line tools cover users, devices, groups, strategies, address books and audit logs; we found no public information on SCIM or directory sync, webhooks, separate customer tenants for MSPs, or named RMM, PSA or endpoint management integrations. 4 6 14 15

Report an error

The MSP Technician

Admin roles come in global, group-scoped and individual variants with permissions across users, devices, groups, logs, strategies and custom clients, which maps neatly onto keeping each client's machines and technicians apart; OpenID Connect sign-on with Google, Okta and Azure is documented, as are API tokens with permission scopes, Python command-line tools for users, devices, groups, address books, strategies and audits, and strategies for pushing client settings. The licence explicitly permits managed-service use covering my customers' devices and users. We found no public information on SCIM or directory sync, webhooks, time-based permission conditions, or integrations with named RMM, PSA or MDM products. 5 6 8 14 15

Report an error

The Software Support Lead

OpenID Connect single sign-on with named providers, delegated admin roles in Global, Group Scoped and Individual scopes, two-factor authentication that can be enforced per user and re-checked on settings changes, settings strategies assigned to devices, users and groups, and API tokens with scoped permissions plus Python tools for users, devices, groups, address books and audit logs are documented. We found no public information on SCIM or directory sync, webhooks, time-based permissions or integrations with named RMM, PSA or endpoint management products, which keeps it one step below the top anchors. 4 5 6 14 15 16

Report an error

The Small Office Owner

OpenID Connect single sign-on with Google, Okta or Azure, per-user two-factor enforcement, and delegation through Global, Group Scoped and Individual admin roles with permissions over users, devices, groups, strategies and logs are documented, along with API tokens and Python command-line tools covering all of those areas. We found no public information on SCIM or directory sync, webhooks, time-based conditions, or integrations with RMM, PSA or endpoint management products. 6 14 16 4 15

Report an error

The Information Security Officer

OpenID Connect single sign-on against Azure, Okta or Google, per-user enforceable TOTP two-factor that also gates settings changes, and admin roles scoped globally, per group or per device are what I require before a remote tool touches our networks, backed by API tokens with named permission scopes and command-line management of users, devices and groups. We found no public information on directory sync, webhooks, time-limited access rules, or multi-tenant separation for service providers. 6 16 14 4 5 15 8

Report an error

The Skeptic

Admin roles come in global, group-scoped and individual variants with granular permissions across users, devices, groups, logs and custom clients, in-session permissions are governed by control roles, OIDC single sign-on with Google, Okta, Azure and others is documented, and two-factor can be enforced per user. API tokens carry scoped permissions and Python command-line tools cover users, devices, groups, strategies, address books and audit logs, but we found no public information on SCIM or directory sync, webhooks, time-based conditions, MSP tenant separation, or RMM, PSA and MDM integrations. 4 6 14 15 16

Report an error

Session security, audit & reliability

Show reasoning
How this is scored

Whether remote access is a door only the right people can open: end-to-end or transport encryption with the protocol and key length named, two-factor authentication, the user's consent prompt and the option to block input or blank the screen, device and IP allow-lists, trusted-device approval, brute-force protection, session recording and an audit log of who connected to what and when, protection against support scams and misuse of free accounts, a published vulnerability disclosure process and security advisories, independent certifications (ISO 27001, SOC 2), the location and redundancy of relay servers, a public status page, an SLA, and an on-premise or self-hosted server for organisations that keep the relay in their own network.

0 — Nothing on encryption, authentication or how sessions are logged.

3 — A claim of encryption and a password per session; two-factor authentication, audit logs, certifications and the status page are basic or not described.

5 — Encryption with the protocol named, two-factor authentication, a consent prompt for attended sessions, session logs with technician, device and time, session recording offered, a public status page, and a security page describing how access is protected.

8 — End-to-end encryption documented, device or IP allow-lists and trusted-device approval, audit logs exportable, recording rules per group, measures against support scams described, ISO 27001 or SOC 2 with its scope, a vulnerability disclosure policy with published advisories, an SLA, and an on-premise or self-hosted relay option.

10 — Security evidenced, not claimed: independent penetration tests or audit reports available, security advisories with fixed versions and timelines, a self-hosted deployment with no dependency on the vendor's cloud, and failover of the relay infrastructure documented.

Report an error

The IT Support Lead

The encryption is named (NaCl-based end-to-end), two-factor is TOTP or email with enforcement and re-verification on settings changes, consent is by click confirmation, and alarms watch for brute force and attempts outside the IP whitelist. Connection, file, console and alarm logs are exportable with configurable retention, and because we self-host, the relay stands in our own network; we found no public information on session recording, ISO 27001 or SOC 2, a vulnerability disclosure policy, a status page or an SLA. 1 3 16 17

Report an error

The MSP Technician

NaCl end-to-end encryption, TOTP and email two-factor with per-user enforcement, an IP whitelist, trusted devices, alarm rules for repeated login and access attempts, and exportable audit logs with configurable retention give me a chain I can defend, and the relay runs self-hosted inside my own network. We found no public information on session recording, ISO 27001 or SOC 2 certifications, a vulnerability disclosure process or an SLA — the licence states support and maintenance are provided at the company's sole discretion — and the console ships with default admin credentials, with documentation advising an immediate password change. 3 4 7 8 16 17

Report an error

The Software Support Lead

End-to-end encryption based on NaCl, an IP whitelist with brute-force and anomaly alarms, trusted-device and 2FA-code values in the connection log, consent by click confirmation, exportable audit logs with configurable retention, a published scam warning and the whole relay self-hosted on our own servers give a strong documented picture. We found no public information on session recording, ISO 27001 or SOC 2 certifications, a vulnerability disclosure process, a status page or an SLA — the terms state support and maintenance are provided at the company's sole discretion. 1 2 3 7 8 11 16 17

Report an error

The Small Office Owner

NaCl-based end-to-end encryption, two-factor by email or authenticator app with backup codes, authentication by click confirmation, one-time or permanent password, and audit logs with CSV export, configurable retention and alarms for IP-whitelist violations and repeated access attempts are documented — and the whole relay runs on my own server. We found no public information on session recording, ISO or SOC certifications, a vulnerability disclosure policy, a status page or a service-level agreement, and the terms state support is provided at the company's sole discretion. 3 16 17 7 8 1

Report an error

The Information Security Officer

End-to-end encryption based on NaCl, an IP whitelist, trusted-device state, brute-force alarms on login and terminal access, and connection, file, console and alarm logs with export and configurable retention are documented, and the relay itself runs on our own servers via Docker, the architecture I insist on. We found no public information on session recording, a vulnerability disclosure process with published advisories, ISO 27001 or SOC 2 certification, or a status page, and the terms state that support and maintenance are provided at the company's sole discretion. 3 16 17 4 7 8 2

Report an error

The Skeptic

End-to-end encryption based on NaCl, TOTP and email two-factor with backup codes, IP-whitelist and brute-force alarms, trusted-device entries, CSV-exportable audit logs with configurable retention down to indefinite, a published scam warning, and a relay the customer hosts itself are all documented. We found no public information on session recording, ISO 27001 or SOC 2 certification, a vulnerability disclosure process with advisories, a status page, or an SLA, and the licence states support and maintenance are provided at the vendor's sole discretion under separate agreement; the web console also ships with default administrator credentials that the documentation itself says to change immediately. 2 3 7 8 15 16 17

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Who the contracting entity and the parent company are, where account data, device lists, session logs, recordings, chat transcripts and file transfers are stored and processed, where the relay and brokering servers that carry session traffic stand, and who the subprocessors are (hosting, relay networks, email delivery, support and payment tools, AI models). Independently sourced by the sovereignty pipeline. A self-hosted or on-premise server the customer runs on its own European infrastructure counts as the customer's chain, whatever the vendor's seat, as long as it does not call home for more than licensing.

0 — Non-EU vendor and contracting entity, hosting and relay locations unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting and relay locations are unstated or non-EU and the subprocessors are not listed.

5 — EU hosting or EU relay servers available and an EU contracting entity or EU representative, but parts of the chain (session brokering, support, payment, AI) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications stated — or a self-hosted server documented that keeps sessions, logs and recordings on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting, relays and every subprocessor including any AI model, or a self-hosted edition with no call home beyond licensing, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The IT Support Lead

The contracting entity and governing law are Singapore, and the privacy policy names Google Analytics and Stripe as subprocessors for the website and payments, with GDPR and standard contractual clauses referenced. What matters to me is documented: the deployment is self-hosted on our own infrastructure, with relays, console and logs including their retention on our own servers, which I can keep in North Rhine-Westphalia. We found no public information on a data processing agreement, an EU contracting entity or representative, or what the self-hosted server transmits to the vendor beyond the licence key. 1 8 9 15 17

Report an error

The MSP Technician

The server self-hosts on my own infrastructure via docker compose with my own relay and web console, so session traffic and audit logs stay on my servers — that chain is European because it is mine. The vendor chain is less clear: Purslane Tech Pte. Ltd. sits in Singapore with Singapore governing law, Google Analytics and Stripe are named for website analytics and payment, and transfers out of the EEA rely on standard contractual clauses or the EU-US Data Privacy Framework. We found no public information on a published data processing agreement or on where account and licence data are hosted. 1 3 7 8 9

Report an error

The Software Support Lead

The entire product is a server we run ourselves — the pricing page stresses this is self-hosting, not a SaaS subscription — and the captured pages describe it as keeping our data fully under our control, so the session chain would sit on our European infrastructure in Kassel. The contracting party is Purslane Tech Pte. Ltd. in Singapore under Singapore governing law, the website names Google Analytics and Stripe as its analytics and payment providers with standard contractual clauses for transfers out of the EEA, and we found no public information on a published data processing agreement or the hosting of account and licence data. 1 2 3 7 8 9

Report an error

The Small Office Owner

Self-hosting on my own infrastructure is the documented deployment model, keeping sessions, logs and relays on my servers, and the privacy policy references the GDPR, transfers out of the EEA under standard contractual clauses, and names Google Analytics and Stripe as subprocessors. But the contracting entity is Purslane Tech in Singapore with Singapore courts and exclusive jurisdiction, subprocessor locations are not stated, and we found no public information on a data processing agreement, security certifications, or what the Pro server transmits to the vendor beyond the licence check. 2 3 9 7 8 4

Report an error

The Information Security Officer

The product is documented as self-hosting on our own infrastructure, with the pricing page stating it is not a SaaS subscription, so session brokering and audit logs stay on machines we control, while the vendor's own chain names Google Analytics and Stripe and cites standard contractual clauses for transfers out of the EEA. The contracting entity and exclusive jurisdiction are Singapore, and we found no public information on a data processing agreement, subprocessor locations, or certifications. 2 3 1 9 8 7

Report an error

The Skeptic

The contracting party is Purslane Tech Pte. Ltd. at a Singapore address under Singapore law with exclusive Singapore jurisdiction, the privacy policy names Google Analytics and Stripe as subprocessors without stating their locations, and transfers out of the EEA rely on standard contractual clauses or the EU-US Data Privacy Framework. The server is self-hosted on the customer's own infrastructure with logs and address books retained there, which can place the session chain in Europe, but we found no public information on where the vendor's own account and licence systems are hosted, on a data processing agreement, or on whether the self-hosted server calls home beyond licence checks. 1 2 3 7 8 9

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per plan and what the licence counts (technicians or seats, concurrent sessions, managed or unattended endpoints), what extra technicians, endpoints and sessions cost, which features (mobile device support, branding, SSO, session recording, integrations, on-premise server) cost extra, monthly versus annual billing, renewal prices, the terms for commercial use of a free version, minimum term, and VAT.

0 — No public prices at all; every customer is a sales call or a partner quote.

3 — A starting price exists, but what it counts and what extra technicians, endpoints and add-ons cost is unclear.

5 — Plans are public with their price and what the licence counts, but at least one commonly needed piece (extra technicians, more endpoints, mobile support, SSO, on-premise) is unpriced or "on request".

8 — Every plan priced publicly with its scaling rule for technicians, sessions and endpoints, add-ons priced, monthly and annual prices shown, renewal terms, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of technicians, concurrent sessions and endpoints, with every add-on, the on-premise licence and support fees, renewal increases and cancellation terms published.

Report an error

The IT Support Lead

The scaling rule is public — $1.20 for each additional user and $0.12 for each additional device — with plan prices and what they count, annual-only billing stated outright, no auto-renewal with a reminder 14 days before expiry, a one-year licence per server, and no refund if we terminate early. Features are not sold as add-ons and the pricing page states there are no hidden fees; we found no public information on VAT treatment or support fees, and a trial licence is only available on request. 2 8

Report an error

The MSP Technician

Plans and what they count are public: a free self-hosting plan at $ 0, an individual plan at $ 11.88 /month USD billed annually for one login user and twenty managed devices, and a customized plan at $ 23.88 /month USD billed annually with '$1.20 for each additional user' and '$0.12 for each additional device', licensed per server for a one-year prepaid term with no auto-renewal. Managed-service use is explicitly allowed as long as the licence covers the customers' devices and users, which keeps cost linear as my client list grows. We found no public information on VAT treatment or renewal price changes. 2 8

Report an error

The Software Support Lead

Plans are public with what the licence counts — login users and managed devices per server — at "$ 11.88 /month USD billed annually" and "$ 23.88 /month USD billed annually", with "$1.20 for each additional user" and "$0.12 for each additional device", annual-only billing, no auto-renewal with a reminder fourteen days before expiry, one-year terms, and the refund and termination rules stated. The gaps are VAT treatment and renewal price changes, for which we found no public information, and the trial and bank-transfer routes both go through "contact us". 2 8

Report an error

The Small Office Owner

Plans are published with annual prices ($11.88 and $23.88 per month, billed annually) and what each counts in login users and managed devices, additional users at $1.20 and additional devices at $0.12 are priced, the term is one year per server prepaid with no automatic renewal and a 14-day reminder, and the paid licence expressly covers internal business and MSP use. VAT treatment is not stated, a trial is only on request, and no renewal-increase terms are published — with no auto-renewal I would simply re-buy, but the pages do not say the price of the second year equals the first. 2 8

Report an error

The Information Security Officer

Every plan is priced publicly with what the licence counts — login users and managed devices, per server, one-year prepaid term, annual billing only with no auto-renewal — and the pages state $1.20 for each additional user and $0.12 for each additional device, alongside a stated no-hidden-fees position. VAT treatment and the renewal price were not stated on the pages we read, and a trial is available only on contact. 2 8

Report an error

The Skeptic

Individual and customized plans are published at $11.88 and $23.88 per month USD billed annually with $1.20 for each additional user and $0.12 for each additional device, one-year prepaid per-server licences with no auto-renewal and a renewal reminder 14 days before expiry, and a stated free tier. What the second year costs is not stated, and we found no public information on VAT treatment, monthly billing, or the price of the basic plan, while a trial licence is by contact and no refund is given when the customer terminates. 2 8

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Self-hostable 1/1 pts 1 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about RustDesk Server Pro

Is RustDesk Server Pro European?

No. whats-best.ai classifies RustDesk Server Pro as Rest of world. Its vendor, Purslane Tech Pte. Ltd., is incorporated in Singapore, per the vendor’s page captured 6 Nov 2026.

Where does RustDesk Server Pro store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

Does RustDesk Server Pro have a free plan?

Yes. RustDesk Server Pro has a free plan, per the vendor’s page captured 6 Nov 2026.

What are the best alternatives to RustDesk Server Pro?

As of 18 Nov 2026, the panel rates Splashtop (3.5/5), TeamViewer Remote (3/5) and ConnectWise ScreenConnect (3/5) highest among the other 16 Remote Desktop & Remote Support products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is TeamViewer Remote (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: RustDesk Server Pro alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (17)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage rustdesk.com Checked 6 Nov 2026 Details →
  2. 2 Pricing page rustdesk.com Checked 6 Nov 2026 Details →
  3. 3 Documentation rustdesk.com Checked 6 Nov 2026 Details →
  4. 4 Documentation (web console) rustdesk.com Checked 6 Nov 2026 Details →
  5. 5 Documentation (permissions) rustdesk.com Checked 6 Nov 2026 Details →
  6. 6 Documentation (single sign-on) rustdesk.com Checked 6 Nov 2026 Details →
  7. 7 About page rustdesk.com Checked 6 Nov 2026 Details →
  8. 8 Terms of service (licence agreement) rustdesk.com Checked 6 Nov 2026 Details →
  9. 9 Privacy policy rustdesk.com Checked 6 Nov 2026 Details →
  10. 10 Remote control & attended support sessions — found from sitemap rustdesk.com Checked 6 Nov 2026 Details →
  11. 11 Remote control & attended support sessions — found from sitemap rustdesk.com Checked 6 Nov 2026 Details →
  12. 12 Unattended access & device deployment — found from sitemap rustdesk.com Checked 6 Nov 2026 Details →
  13. 13 Unattended access & device deployment — found from sitemap rustdesk.com Checked 6 Nov 2026 Details →
  14. 14 Administration, identity & API — found from sitemap rustdesk.com Checked 6 Nov 2026 Details →
  15. 15 Administration, identity & API — found from sitemap rustdesk.com Checked 6 Nov 2026 Details →
  16. 16 Session security, audit & reliability — found from sitemap rustdesk.com Checked 6 Nov 2026 Details →
  17. 17 Session security, audit & reliability — found from sitemap rustdesk.com Checked 6 Nov 2026 Details →