Rustdesk Server

Open source alternative to TeamViewer, AnyDesk, Splashtop and ConnectWise ScreenConnect

10.7K stars
AGPL-3.0
Active this week
Last commit 1 day ago

Last verified Nov 10, 2026

Host your own remote desktop relay server instead of routing sessions through TeamViewer, AnyDesk, or Splashtop infrastructure.

Visit website GitHub10.7K Deploy on Hostinger

Read the full breakdownWho it is for, how it works, trade-offs, the quick start and the FAQ

who it's for

Who Rustdesk Server is for#

IT administrators migrating away from TeamViewer

RustDesk Server removes the per-device licensing cost that makes TeamViewer expensive at scale. An administrator sets up hbbs and hbbr on a single VPS, points the RustDesk client at those servers, and gains unlimited concurrent connections with no per-seat fees. Device management, 2FA, and audit logging are available on RustDesk Server Pro if the team needs them.

Skip if:

If your organization requires a vendor-backed SLA with guaranteed uptime and 24/7 support, RustDesk Server's self-managed model means you own the uptime problem. TeamViewer or Splashtop Business are better fits in that case.

Managed service providers building private support infrastructure

MSPs can run their own relay server to keep all client session traffic on infrastructure they control. RustDesk Server Pro's custom client generator lets them brand the client, and the web console manages access control across technicians and devices without exposing any connection data to a third-party vendor.

Skip if:

If your MSP supports fewer than a dozen clients or needs rapid onboarding with no infrastructure overhead, a hosted tool like ConnectWise ScreenConnect's cloud edition is faster to start with.

Privacy-focused teams in regulated industries

Organizations in healthcare, finance, or government where remote desktop traffic must stay within defined network boundaries can run RustDesk Server on internal infrastructure. Because the relay is self-hosted, no session data crosses a third-party network. The AGPL-3.0 license makes the entire software stack auditable.

Skip if:

If your compliance requirements demand a commercially supported product with formal security certifications (SOC 2, FedRAMP), RustDesk Server's open source licensing may not satisfy your procurement checklist without additional review.

the problem

The problem it solves#

Remote desktop tools like TeamViewer, AnyDesk, and Splashtop route every connection through the vendor's own relay infrastructure. That means your sessions, your device inventory, and your access credentials live on servers you do not control. For IT teams managing dozens or hundreds of endpoints, the per-device or per-connection pricing scales quickly: TeamViewer's business licensing and AnyDesk's per-seat model add up to hundreds of dollars per year for mid-sized deployments.

The deeper issue is data sovereignty. Organizations in regulated industries, or those with strict security policies, cannot allow employee or client sessions to traverse third-party servers. Building a private relay has historically required custom infrastructure or accepting an on-premise enterprise contract from a vendor who controls the software stack.

how Rustdesk Server solves it

How it solves it#

hbbs ID and rendezvous server

hbbs assigns persistent IDs to RustDesk clients and brokers the initial connection handshake. It listens on port 21116 by default and generates a keypair on first run; the public key is what you distribute to clients to authenticate your server. Command-line flags control the bind address, relay server list, and whether to force relay-only mode via the ALWAYS_USE_RELAY environment variable.

hbbr relay server

hbbr proxies remote desktop traffic between two clients when a direct peer-to-peer connection cannot be established, which is the common case across NAT boundaries and firewalls. It listens on port 21117 by default. You can register multiple hbbr instances with hbbs for load distribution. The relay only proxies; it does not store or log session content.

Configuration via CLI flags and environment variables

Every hbbs and hbbr option is available as a command-line flag, an environment variable, or an .env file, with explicit precedence rules documented in docs/environment-variables.md. Options cover bind address, relay server registration, log level, database path, and relay bandwidth tuning. This makes containerized deployments and infrastructure-as-code workflows straightforward to manage.

Pre-built binaries on GitHub Releases

RustDesk Server ships ready-to-run binaries for Linux, macOS, and Windows on every GitHub release. No build toolchain is needed for a standard deployment: download hbbs and hbbr, configure environment variables, and run. For teams building from source, the codebase is Rust and compiles with a single cargo build --release.

Upgrade path to RustDesk Server Pro

The free OSS version installs alongside the paid Pro version, and the official documentation covers converting from OSS to Pro without rebuilding the server. Pro adds a web console, 2FA, SSO via OIDC, LDAP integration, audit logs, access control policies, distributed relay servers, and a custom client generator. The Individual Pro plan starts at $11.88 per month billed annually for 1 login user and 20 managed devices.

strengths · trade-offs

Strengths and trade-offs#

Strengths

No per-device fees on the OSS tierThe free open source tier imposes no limits on managed devices or concurrent connections. TeamViewer's business licensing and AnyDesk's per-seat model charge per device or per concurrent session. RustDesk Server's OSS tier gives you the relay infrastructure itself with no ongoing licensing cost beyond your own server expenses.
Session traffic stays on your own serversBecause you run both hbbs and hbbr, remote desktop sessions never traverse a third-party network. This is the key architectural difference from TeamViewer, AnyDesk, and Splashtop: those vendors' relay servers sit between your machines. With RustDesk Server, the relay is on hardware you control, and the AGPL-3.0 source code is fully auditable.
Actively maintained Rust-based serverWritten in Rust for memory safety and performance, with 10,720 GitHub stars and a last push in November 2026. The project is under active development with releases available for Linux, macOS, and Windows. The companion RustDesk client is also open source, so the full connection stack from client to relay is inspectable and modifiable.

Trade-offs

-You own the uptime and updatesRunning RustDesk Server means you manage availability, security patches, and key rotation. If hbbr goes down, your remote sessions stop working until you restore it. Organizations without in-house infrastructure experience should factor in the operational overhead of running two persistent server processes, monitoring their availability, and keeping the software updated.
-No web console or admin UI on the free OSS tierThe free open source version has no graphical interface for managing users, devices, or permissions. All configuration goes through command-line flags and environment variables. Organizations that need centralized device management, audit logs, or 2FA must upgrade to RustDesk Server Pro, which starts at $11.88 per month billed annually.
-170 open GitHub issuesThe repository carried 170 open issues at last check. For server infrastructure your team will depend on for remote access, review the open issues that affect your deployment scenario before committing. The project is actively maintained with a November 2026 last push, but the issue count is worth monitoring for bugs relevant to your operating system or network configuration.

versus alternatives

Rustdesk Server vs alternatives#

RustDesk Server vs TeamViewer

Both tools enable remote desktop access to Windows, macOS, and Linux machines. TeamViewer is a closed, vendor-hosted service with per-license pricing; RustDesk Server is AGPL-3.0 open source infrastructure you deploy yourself.

Feature	RustDesk Server	TeamViewer
License	AGPL-3.0	Proprietary
Session routing	Your own servers	TeamViewer cloud
Self-hosting	Yes	No
Per-device pricing	None on OSS tier	Yes
Web console	Server Pro only	Yes

RustDesk Server is the better choice for regulated industries, security-sensitive organizations, and teams unwilling to pay TeamViewer's per-license fees. Because you control the relay, session traffic never leaves your infrastructure.

TeamViewer is still the better fit when you need a managed cloud option with enterprise support SLAs and no infrastructure overhead. TeamViewer's global relay network handles uptime, updates, and geographic distribution without any operator involvement.

RustDesk Server vs AnyDesk

AnyDesk offers a lightweight client and competitive pricing, but all sessions route through AnyDesk's relay network. RustDesk Server removes that dependency.

Feature	RustDesk Server	AnyDesk
License	AGPL-3.0	Proprietary
Session routing	Your own servers	AnyDesk cloud
Self-hosting	Yes	No
Client open source	Yes (RustDesk client)	No

RustDesk Server is the stronger choice for organizations that need an auditable, fully open stack. The RustDesk client is also open source, so the entire connection path from client to relay to destination can be inspected and modified.

AnyDesk remains easier for ad-hoc support cases where the recipient cannot install software permanently. If your use case is occasional one-time support rather than persistent unattended access, AnyDesk's simpler onboarding can outweigh RustDesk's self-hosting requirements.

install · quick start

Quick start#

bash

Download the RustDesk Server binaries (hbbs and hbbr) from GitHub Releases: https://github.com/rustdesk/rustdesk-server/releases/latest

tech stack · detected from GitHub

What it's built on#

Languages: JavaScriptRust

frequently asked

FAQ#

What is the difference between hbbs and hbbr in RustDesk Server?

hbbs is the ID and rendezvous server, assigning IDs to RustDesk clients and helping them discover each other. hbbr is the relay server, proxying traffic between two clients when a direct peer-to-peer connection cannot be established. Both must be running for a complete self-hosted setup. hbbs listens on port 21116 by default; hbbr listens on port 21117.

Is RustDesk Server free for commercial use?

The open source tier is AGPL-3.0 licensed. You can run it for free for internal commercial use, including supporting your own team and client devices, without paying any license fees. The free tier has no limits on managed devices or concurrent connections. If you modify the source code and run a modified version as a hosted service for third parties, AGPL requires publishing those changes.

How do I connect the RustDesk client to my own server?

In the RustDesk client settings, enter your hbbs server address in the ID/Relay Server field and your hbbr address in the Relay Server field. The client uses the public key generated by hbbs on first run to verify the server. Full setup instructions are in the official self-hosting documentation at rustdesk.com/docs/en/self-host/rustdesk-server-oss/.

What does RustDesk Server Pro add over the free version?

RustDesk Server Pro adds a web console for managing users and devices, two-factor authentication (2FA), SSO via OIDC, LDAP integration, audit logs, access control, distributed relay servers, and a custom client generator. The Individual Pro plan starts at $11.88 per month billed annually (1 login user, 20 managed devices). The free OSS tier covers unlimited connections but has no web console or administrative UI.

Does RustDesk Server support distributed relay servers?

Distributed relay servers are a RustDesk Server Pro feature. The free OSS tier runs a single relay instance. Pro lets you register multiple hbbr instances in different geographic regions through the web console, reducing latency for globally distributed teams. The relay server list is configured via the RELAY-SERVERS flag or environment variable on the hbbs process.

also worth a look

Similar open-source tools#

RustDesk

Alternative toTeamViewer

Self-hosted remote desktop with end-to-end encryption

128,542 GitHub stars
Licence AGPL-3.0

Oxynote

Alternative toNotion

Technical wiki with live metrics, draft reviews, and real-time editing

537 GitHub stars
Licence Apache-2.0

Vela

Alternative toGoogle Maps

OpenStreetMap and Google data, no account, no Play Services

2,531 GitHub stars
Licence GPL-3.0

OpenBot

Alternative toGrok Bot

AI coworkers you can trust with real work

10,552 GitHub stars
Licence MIT

FckSignups

InCustomer Support

Open-source tools that work instantly, no signup required

4,570 GitHub stars
Licence GPL-3.0

Bitwarden

Alternative to1Password

Open source password manager with end-to-end encryption and self-hosting.

20,595 GitHub stars
Licence AGPL-3.0

by category

Open source tools in these categories#

151

Self-host Rustdesk Server on a Hostinger VPS

Keep it running 24/7, even when your laptop is off. A Hostinger VPS gives it a server of its own.

01
Choose a plan
Starts from $6.49/mo
02
Apply
Extra 10% off yearly plans
03
Install Rustdesk Server
On a server that stays on
04
Start building
Focus on the app, not the server

Deploy on Hostinger

Inbox Zero

Alternative toSuperhuman

AI email assistant that drafts replies and clears your inbox

12,942 GitHub stars
Licence AGPL-3.0
#Email

rakazo

Alternative toGrok Bot

AI teammates you own: your keys, your model, your machine.

7,478 GitHub stars
Licence Apache-2.0
#AI Agents

SnitchFeed

Live monitoring on LinkedIn, X, Reddit & more. Agentic social listening for startups.

Marketing & Growth

Advertise your product

The projects we add and every new guide. Free, unsubscribe any time.

Find open source alternatives to paid software

RustDesk Server vs TeamViewer

Feature	RustDesk Server	TeamViewer
License	AGPL-3.0	Proprietary
Session routing	Your own servers	TeamViewer cloud
Self-hosting	Yes	No
Per-device pricing	None on OSS tier	Yes
Web console	Server Pro only	Yes

RustDesk Server vs AnyDesk

AnyDesk offers a lightweight client and competitive pricing, but all sessions route through AnyDesk's relay network. RustDesk Server removes that dependency.

Feature	RustDesk Server	AnyDesk
License	AGPL-3.0	Proprietary
Session routing	Your own servers	AnyDesk cloud
Self-hosting	Yes	No
Client open source	Yes (RustDesk client)	No

Who Rustdesk Server is for#

IT administrators migrating away from TeamViewer

Skip if:

Managed service providers building private support infrastructure

Skip if:

Privacy-focused teams in regulated industries

Skip if:

The problem it solves#

How it solves it#

hbbs ID and rendezvous server

hbbr relay server

Configuration via CLI flags and environment variables

Pre-built binaries on GitHub Releases

Upgrade path to RustDesk Server Pro

Strengths and trade-offs#

Strengths

Trade-offs

Rustdesk Server vs alternatives#

RustDesk Server vs TeamViewer

RustDesk Server vs AnyDesk

Quick start#

What it's built on#

FAQ#

Similar open-source tools#

Open source tools in these categories#

IT Management

Security & Monitoring

Business & Productivity

Communication & Collaboration

Find open source alternatives to paid software

Who Rustdesk Server is for#

IT administrators migrating away from TeamViewer

Skip if:

Managed service providers building private support infrastructure

Skip if:

Privacy-focused teams in regulated industries

Skip if:

The problem it solves#

How it solves it#

hbbs ID and rendezvous server

hbbr relay server

Configuration via CLI flags and environment variables

Pre-built binaries on GitHub Releases

Upgrade path to RustDesk Server Pro

Strengths and trade-offs#

Strengths

Trade-offs

Rustdesk Server vs alternatives#

RustDesk Server vs TeamViewer

RustDesk Server vs AnyDesk

Quick start#

What it's built on#

FAQ#

Similar open-source tools#

Open source tools in these categories#

IT Management

Security & Monitoring

Business & Productivity

Communication & Collaboration

Find open source alternatives to paid software