Application hosting

Hosting RustDesk Server OSS

RustDesk Server OSS lets you run the connection infrastructure used by RustDesk remote-desktop clients. The ID server helps clients find one another, while the relay carries sessions that cannot connect directly. It suits teams that want control over those endpoints. It is the server component, rather than a browser-based desktop or a replacement for the clients installed on participating computers.

Requirements last checked 20 Oct 2026 against the project's documentation.

Compare server plans Size a server

Understand the setup

Find the software and services needed to run the application.

See requirements

Budget your resources

Plan memory, storage and CPU for the way you will use it.

Open resource planner

Build your shortlist

Compare plans for the starting size, then review the provider and billing terms.

See plans

Must have

Installation requirements

Docker or Podman for the documented container deployment.
Network access to the required ID and relay service ports.
RustDesk clients configured for your server and its public key.

Recommended

Planning guidance

Use the resource planner to size a server for your workload.

Choosing a server for RustDesk Server OSS

Relay traffic is a major sizing consideration when clients cannot connect directly. Choose network capacity for the sessions you expect to relay; the container guide does not establish a universal RAM or concurrent-session target.

Deploy with

Supported paths

Docker Compose
Docker
Podman Quadlet

The host must provide

Runtime

ID server: hbbs from the selected RustDesk Server OSS release.
Relay: hbbr with persistent server data.

Storage

Persistent data

Preserve the server data and keys across container replacement. Client configuration depends on the server identity, so losing that data can require changes on participating devices.

Step by step

Plan your RustDesk Server OSS deployment

Prepare the host

Create persistent storage and choose Docker Compose or the supported container method for your system.
Official instructions
Start the server pair

Run hbbs and hbbr and permit their required network traffic. Keep optional web-client ports closed unless they are needed.
Official instructions
Configure the clients

Set the server address and public key on clients. Confirm both direct and relayed connections before depending on remote access.
Official instructions

Security

Before you go public

If web-client support is enabled, restrict its WebSocket ports to a trusted reverse proxy.
Protect private keys and the remote computers independently.

Cost

Beyond the server price

Include relay bandwidth and server backups in the hosting budget.
Server Pro features are separate from the OSS server.

Want the full monthly bill? Use the hosting cost calculator. Add storage, backups and other costs to your estimate.