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 Software Support Lead

Weighted verdict

Runs first- and second-level support for a vendor of practice software for physiotherapists, with fourteen agents in Kassel and four thousand customer practices that are not IT people. Wants a small support client in the company's own branding that runs without admin rights, a support button on the website that puts the caller in a queue, the session written back to the helpdesk ticket, and reports per agent that show how long a fix takes.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Software Support Lead

Panel median The Software Support Lead This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Software Support Lead
Remote control & attended support sessions 3 of 5 3 of 5
Unattended access & device deployment 3.5 of 5 3.5 of 5
Support desk workflow, branding & reporting 2 of 5 2 of 5
Administration, identity & API 3.5 of 5 3.5 of 5
Session security, audit & reliability 3.5 of 5 3.5 of 5
European sovereignty 3 of 5 3.5 of 5
Pricing transparency 3.5 of 5 3.5 of 5

Remote control & attended support sessions

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 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

Unattended access & device deployment

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 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

Support desk workflow, branding & reporting

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 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

Administration, identity & API

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 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

Session security, audit & reliability

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 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

European sovereignty

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 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

Pricing transparency

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 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

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 →