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.
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 suffix | Platform | Notes |
|---|---|---|
| -x86_64.exe / .msi | Windows 64-bit | Installer and MSI |
| -aarch64.dmg | macOS Apple Silicon | M1–M4 chips |
| -x86_64.deb | Debian, Ubuntu | Also .rpm and .AppImage |
| -universal-signed.apk | Android | All architectures in one file |
| nightly | All | Fresh commits, may be unstable |
Building from source
Install the toolchain
You need Rust via rustup, the Flutter SDK, Python 3 and vcpkg with libvpx, libyuv, opus and aom.
Prepare dependencies
Set VCPKG_ROOT and install the libraries for your target triplet, for example x64-windows-static.
Run the build script
Execute
python3 build.py --flutter. The output binary appears in the flutter build folder.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