Leneex - Hosting Provider
RustDesk

Deploy RustDesk on a VPS in One Click

Utilities

Open-source remote desktop tool with your own connection server for encrypted access to computers.

Deploy on a VPSAll apps
  • Ready in ~2 min
  • Free installation
  • We handle the setup
At a glance
Version
Latest (1.1)
Operating system
Ubuntu Server 24.04 LTS
Minimum RAM
1 GB
License
AGPL-3.0
Addressing
IPv4, IPv6
GitHub
11,000
Deployment~2 min
Open source & self-hosted
VPS plans

Choose a VPS plan for RustDesk

Blazing-fast NVMe drives and powerful processors. Take a ready-made plan or build the configuration yourself.
Minex
Perfect for personal projects and small websites.
€3.20/mo
Save €0.80 per month
  • 1 vCPU core
  • 1 GB DDR5 RAM
  • 20 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 1 TB traffic
Basex
A great balance of power and affordable price.
€4.80/mo
Save €1.20 per month
  • 2 vCPU cores
  • 2 GB DDR5 RAM
  • 40 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • 2 TB traffic
Most popular
Corex
For growing applications and businesses.
€7.20/mo
Save €1.80 per month
  • 4 vCPU cores
  • 4 GB DDR5 RAM
  • 50 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Midex
Resources for high-load projects.
€9.60/mo
Save €2.40 per month
  • 4 vCPU cores
  • 6 GB DDR5 RAM
  • 60 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Proex
Maximum power and scalability.
€12.00/mo
Save €3.00 per month
  • 6 vCPU cores
  • 8 GB DDR5 RAM
  • 70 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Scalex
Resources for scaling.
€16.00/mo
Save €4.00 per month
  • 6 vCPU cores
  • 10 GB DDR5 RAM
  • 150 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Maxex
A large reserve of power.
€44.00/mo
Save €11.00 per month
  • 8 vCPU cores
  • 16 GB DDR5 RAM
  • 200 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic
Apex
The top configuration.
€79.99/mo
Save €20.00 per month
  • 16 vCPU cores
  • 32 GB DDR5 RAM
  • 400 GB NVMe SSD
  • Full root access
  • 1 dedicated IPv4
  • Unlimited traffic

What you can do with RustDesk

RustDesk is an open-source remote desktop application built as a self-hosted alternative to TeamViewer and AnyDesk. The core server components are open source under AGPL, which lets IT teams, MSPs, and support staff verify exactly how connection data is handled instead of trusting a closed vendor binary. Clients exist for Windows, macOS, Linux, Android and iOS, all connecting through the same ID and relay service rather than a proprietary cloud.

Choosing RustDesk self hosted over the default public server changes who controls the connection path. By default, clients register through RustDesk's own shared infrastructure — running your own hbbs/hbbr pair on a VPS means every session ID, key exchange, and relayed byte passes through hardware you control, with no shared rate limits from other users of the public service. That's the practical reason RustDesk vps hosting appeals to teams handling client machines: predictable performance and a connection server nobody outside the company touches.

Get started
The applications screen of the control panel with one-click install

RustDesk features

A server surrounded by app icons — applications running on a VPS

Beyond acting as a drop-in remote desktop client, self-hosting gives you direct control over the two services that make every connection work.

01

hbbs + hbbr architecture

The ID/rendezvous server (hbbs) looks up devices while the relay server (hbbr) carries traffic when a direct connection isn't possible.

02

NAT traversal with hole punching

The server attempts a direct peer-to-peer link first and only falls back to relaying through hbbr when needed.

03

Key-pair encryption

hbbs generates an asymmetric key pair on RustDesk installation, so session traffic stays unreadable even to whoever operates the relay.

04

Custom client builds

Bundle your server address and key into a branded installer so end users never type connection settings by hand.

05

Cross-platform reach

Native apps for Windows, macOS, Linux, Android, and iOS all register with the same self-hosted server.

06

File transfer and unattended access

Move files between machines and set a permanent password for access without an on-screen confirmation.

07

Config via flags, env vars, or file

hbbs and hbbr can be configured with command-line flags, environment variables, or an .env / config file, no separate admin panel required at the open-source tier.

08

Docker-native deployment

Official RustDesk vps docker images ship for both hbbs and hbbr, so the whole stack starts as containers rather than manually compiled binaries.

Requirements

Which server to run it on

Minimum requirements for RustDesk and the configuration worth starting with.
Minimum
  • CPU1 vCPU
  • Minimum RAM1 GB
  • Disk10 GB
Recommended
VPS Minex
  • CPU1 vCPU
  • Minimum RAM1 GB
  • Disk20 GB

Installation is free — you only pay for the server

Getting started

How to deploy RustDesk

Three steps and the app is running on your server.
Step 1
Choose a server

Pick a VPS with enough network headroom for the number of simultaneous relay sessions your team expects before you install RustDesk on VPS resources.

Step 2
Pick the app

Select the RustDesk template to deploy RustDesk in one click — Leneex brings up the hbbs and hbbr containers together so both services start in sync.

Step 3
Get your credentials

Copy the server address and the generated public key from your instance and enter them in each client's ID/Relay Server settings, since the open-source server tier has no separate web login step.

Official websiterustdesk.com
GitHub repositorygithub.com
Documentationrustdesk.com
Why us

Why Host RustDesk on Leneex

Speed, protection and support you can rely on — on every plan, with no hidden limits.
Deployment speed
RustDesk needs hbbs and hbbr running together with matching ports open from the first minute — a one-click template avoids the manual docker-compose and firewall work that trips up a first-time vps for RustDesk setup.
Free installation
RustDesk's server components are already free and open source, so paying for the install step would undercut the whole point of self-hosting it — Leneex sets up the containers at no cost.
DDoS protection
hbbs and hbbr listen on ports reachable from wherever your remote clients connect from, often outside your office network — keeping that entry point online under attack is what keeps every technician's remote session working.
Control and support
Diagnosing a failed connection means reading hbbs/hbbr logs and adjusting firewall rules for the hole-punching ports — root access and engineers who understand container networking cut that troubleshooting time down.
99.9% uptime with SLA compensation
If the RustDesk server goes down, every technician loses remote access to every managed machine at once — unlike a single web app going offline, this stops an entire support operation, which is why uptime SLA weighs more here.
Flexible payment
MSPs and IT departments running RustDesk instead of a per-seat SaaS tool want that cost advantage reflected in billing too — a fixed VPS invoice fits corporate procurement better than recurring per-technician charges.
What to choose

RustDesk: Self-Hosted vs Cloud — Which to Choose

We compare cost, control over your data and limits, so the choice is an informed one.
Ready-made SaaS
Self-hosted on LeneexRecommended
Resources and limitsBandwidth and the number of concurrent sessions are shared among all customers on the planAll server bandwidth and computing resources are dedicated exclusively to your relay traffic
Control and accessClosed-source agent with no access to the server-side infrastructure; keys and metadata are managed by the vendorFull root access to hbbs/hbbr, open-source code, and your own encryption keys
Feature limitsSome features (such as session recording and the number of simultaneous connections) are restricted to higher-tier plansFull feature set: file transfer, unattended access, and custom clients, with no per-seat limits
ScalingGrowing the number of technicians requires purchasing additional seats or channels under the applicable planUpgrade VPS resources with a single click; technical users are not licensed separately
CostTypically billed monthly per seat or channel, with costs increasing as the team growsFixed server pricing regardless of the number of support technicians connecting
Who it fitsTeams that prioritize a ready-to-use web interface without the need to administer a serverTeams that need to keep traffic and session metadata within their own infrastructure

RustDesk does not sell a separate cloud SaaS subscription for end users. It offers only an open-source server and a paid self-hosted Pro tier with a web console. Therefore, the table compares self-hosting with a typical commercial SaaS remote access solution. Self-hosting is a practical way to run RustDesk with full control over the communication channel and encryption keys, without relying on third-party infrastructure or paying per workstation.

Frequently Asked Questions about RustDesk on VPS

What people ask most about RustDesk and our servers.

  • Device IDs and client connections are determined by the key pair files (id_ed25519.pub / id_ed25519), generated by hbbs. Copy these files and the data directory from the old server to the new one to keep the same IDs working without reinstalling the clients.

  • Upgrading resources does not affect the volume containing the keys and data, so device IDs remain unchanged. Clients briefly lose their connections while the containers restart and reconnect automatically.

  • Yes. hbbs generates a key pair on the first startup, and the entire session is encrypted at the RustDesk protocol level, regardless of the hosting settings.

  • According to RustDesk's own estimates, 1 CPU core and 1 GB of RAM are sufficient to support 1,000 concurrent relay connections. This means even an entry-level VPS plan can comfortably meet the needs of a small or medium-sized support team.

  • Leneex maintains the underlying operating system and Docker environment, but updating the rustdesk-server image (switching to a newer tag) is the client's responsibility. RustDesk releases new server versions more frequently than the underlying infrastructure changes.

What's Already Configured

After the one-click deployment, the Docker containers running hbbs (ID/rendezvous server) and hbbr (relay server) are already up and configured with an automatic restart policy. You need to open port 21116 for TCP and UDP (used for ID registration, heartbeats, and hole punching), as well as port 21117 for the hbbr relay service. On the first startup, hbbs generates a key pair and stores it in a data volume. These keys are what clients need to connect to your server instead of the public RustDesk server.

First Access and Client Configuration

The open-source server does not include a separate web console with a login. Instead, copy the server address and public key (id_ed25519.pub) and enter them in each RustDesk client under the ID/Relay Server settings. Once the address and key are entered, the client receives a new local ID associated with your server, and all subsequent connections are routed through it.

Maintenance

Since there is no administration panel at this level, updating the server involves replacing the rustdesk-server image with a newer tag and recreating the containers.

Deploy RustDesk in about 2 minutes

Choose a server — we do the rest: install, configure and send you the credentials.

Choose a serverAll apps