Open source · AGPL-3.0

RustDesk GitHub: Code, Releases and Contributing

The entire project lives in public repositories. Here you will find what each repository contains, how to pick a release asset and how to build the client yourself.

Clone the repository
git clone --recurse-submodules cd rustdesk

Main repositories

The organization hosts several projects. These are the ones most people need.

rustdesk

The client: Rust core, Flutter interface, platform code for capture and input. Releases for all systems are attached here.

View repository →

rustdesk-server

Open-source hbbs and hbbr. Contains Docker files and systemd examples for running your own infrastructure.

View repository →

doc.rustdesk.com

Source of the documentation site: installation guides, client configuration and server deployment.

View repository →

hbb_common

Shared library with protocol definitions, config handling and networking helpers used by client and server.

View repository →

Reading the Releases page

Each release on RustDesk GitHub carries dozens of assets. File names follow a simple pattern.

Asset suffixPlatformNotes
-x86_64.exe / .msiWindows 64-bitInstaller and MSI
-aarch64.dmgmacOS Apple SiliconM1–M4 chips
-x86_64.debDebian, UbuntuAlso .rpm and .AppImage
-universal-signed.apkAndroidAll architectures in one file
nightlyAllFresh commits, may be unstable

Building from source

  1. Install the toolchain

    You need Rust via rustup, the Flutter SDK, Python 3 and vcpkg with libvpx, libyuv, opus and aom.

  2. Prepare dependencies

    Set VCPKG_ROOT and install the libraries for your target triplet, for example x64-windows-static.

  3. Run the build script

    Execute python3 build.py --flutter. The output binary appears in the flutter build folder.

  4. Or use Docker

    A ready Dockerfile in the repository compiles the Linux client without touching your system packages.

How to contribute

Bug reports go to Issues with logs and OS version. Ideas and questions are discussed in Discussions before any code is written.

Pull requests should target the master branch, pass CI and include a short description of the change. Translations are welcome and live in the src/lang folder.

Before opening an issue

  • Search closed issues — many problems are already solved
  • Reproduce on the latest nightly build
  • Attach logs from the client's log folder
  • Describe network setup: direct, relay or self-hosted

RustDesk GitHub FAQ

They are built by public CI workflows from tagged commits, so you can trace every binary back to its source code.
The AGPL license allows forks, but you must publish your modified source code under the same license.
Stable versions come out every few months, while nightly builds are generated automatically almost every day.