RustDesk Open-Source Remote Desktop and Self-Hosted Access

RustDesk is open-source remote desktop software for remote access and remote support. You can use RustDesk infrastructure or connect clients to your own RustDesk Server. When a session starts, RustDesk first attempts a direct connection through NAT traversal; if a direct path cannot be established, the session can fall back to a Relay Server. This makes RustDesk suitable for remote support, unattended access, device maintenance, and self-hosted remote access.

Connections and self-hosting

How RustDesk Establishes a Remote Connection

RustDesk Server provides device ID, rendezvous, signaling, and relay services. When remote access begins, the server helps the two endpoints discover each other and attempts NAT traversal. If a P2P connection can be established, the devices communicate directly; otherwise the session falls back to the Relay Server.

RustDesk self-hosted server and remote access infrastructure

Device ID and Signaling

RustDesk uses hbbs as its ID, rendezvous, and signaling server to register devices, locate remote endpoints, and coordinate connection establishment.

P2P and NAT Traversal

RustDesk first attempts NAT hole punching so the two endpoints can communicate directly without sending the remote session through a relay.

Relay Fallback

If network conditions prevent a direct connection, RustDesk uses hbbr as the Relay Server to carry communication between the two endpoints.

Self-Hosted Infrastructure

Running your own RustDesk Server gives you control over the ID and relay infrastructure and lets you deploy it around your own network, operations, and compliance requirements.

Server OSS and Server Pro

From Open-Source Self-Hosting to Centralized Administration

RustDesk offers two self-hosted server options. Server OSS provides the core ID, rendezvous, signaling, and relay services. Server Pro builds on the same remote-access foundation with centralized administration, identity integrations, access controls, and management features for organizations.

  • ✓
    RustDesk Server OSSA free, open-source self-hosted backend built around hbbs and hbbr for device discovery, connection coordination, and relay services.
  • ✓
    Web ConsoleServer Pro provides a centralized administrative interface for managing users, devices, permissions, policies, logs, and server settings.
  • ✓
    OIDC, LDAP and 2FAIntegrate Server Pro with existing identity systems and add additional authentication controls for user accounts.
  • ✓
    Access Control and Device PoliciesControl which users can access devices and which remote actions are allowed through roles, groups, strategies, and access rules.
  • ✓
    Address Books and Audit LogsServer Pro adds shared address books and logs for remote connections, file transfers, security events, and administrative activity.
RustDesk remote device administration

Self-hosting

Start RustDesk Server with Docker Compose

RustDesk provides Docker Compose configurations for both Server OSS and Server Pro. The steps below show the basic Server OSS flow; production deployments should also account for firewall rules, server addressing, DNS, client configuration, and your own security requirements.

Step 1

Install Docker

bash <(wget -qO- https://get.docker.com)
Step 2

Download the OSS Compose File

wget rustdesk.com/oss.yml -O compose.yml
Step 3

Start RustDesk Server

docker compose up -d

Self-hosting scenarios

Who Uses RustDesk Self-Hosting?

RustDesk's published survey of more than 1,000 self-hosting users shows that the most common use cases include IT support, IT administration, remote work, and industrial or other device-access environments.

0%IT Support
0%IT Administration
0%Remote Work
0%Industrial and Other

Remote access scenarios

Common Ways to Use RustDesk

IT support teams can establish an authorized remote session, view the remote desktop, and help troubleshoot software, system, or configuration issues.

Remote IT support scenario
IT SupportRemote assistance

Remote workers can connect to an available work device from another location and continue using applications, files, and the remote desktop environment.

Remote work scenario
Remote WorkRemote desktop access

Always-on systems and fixed endpoints can be configured for unattended access so administrators can inspect, maintain, and operate them remotely.

Unattended remote access scenario
System OperationsUnattended access

Organizations using Server Pro can centrally manage users, devices, permissions, policies, identity integrations, and remote-access rules through the Web Console.

RustDesk Server Pro administration scenario
IT AdministrationCentralized access control

Organizations that want control over their remote-access infrastructure can operate their own ID and Relay Servers inside infrastructure they manage.

RustDesk self-hosted infrastructure scenario
Infrastructure ManagementSelf-hosted services

Support teams using Server Pro can combine centralized policies and client configuration with their own deployment workflow for managed remote support.

Managed RustDesk deployment scenario
Support TeamsManaged deployment

RustDesk FAQ

Remote Connections and Self-Hosting

How does RustDesk establish a remote connection?

RustDesk uses the ID Server to locate the target device and coordinate the two endpoints. It first attempts NAT traversal to establish a direct P2P connection. If a direct path cannot be created, the session can fall back to the configured Relay Server.

Does every RustDesk session pass through a Relay Server?

No. RustDesk attempts a direct connection first. The Relay Server is used when the two endpoints cannot establish a direct connection because of NAT, firewall, routing, or other network conditions.

What is the difference between RustDesk Server OSS and Server Pro?

Server OSS is the free, open-source self-hosted backend built around hbbs and hbbr. Server Pro adds centralized administration such as the Web Console, API, OIDC, LDAP, 2FA, device management, access control, address books, audit logs, and multiple relay management.

What do hbbs and hbbr do?

hbbs is the RustDesk ID, rendezvous, and signaling server used for device registration, discovery, and connection coordination. hbbr is the Relay Server used when the endpoints cannot communicate directly.

What does self-hosting RustDesk give me control over?

Self-hosting lets you operate your own ID and relay infrastructure and keep deployment-related data on systems you manage. Additional device, user, address book, policy, and audit capabilities depend on the server edition and configuration you use.

Open source

RustDesk Is Built in the Open

RustDesk continues to develop around an open-source remote desktop client and self-hosted server infrastructure, with users, developers, and organizations participating across the project and community.

0M
+
Client Downloads
0M+Docker Downloads
0M+Devices Online
0K+GitHub Stars
0K+GitHub Forks
0K+Community Members
0+Languages

Start Using RustDesk for Remote Access

RustDesk - Open-Source Remote Desktop Self-Hosting