What can this machine build?

Lit cells are ready to build right now. Outlined cells need a toolchain. Hatched cells need a different host OS.

building capability map…

0 selected

Dry run (print commands only)

Baked-in config

These values are compiled into the client and written to custom_.txt. The password and permissions live in the base64 payload.

Server Server address Public key API server

Identity App name File name Company Slogan Android app id

Installed identity on the phone. Must not be com.carriez.flutter_hbb or this APK cannot sit beside official RustDesk. Blank is filled from app + company name on save/build.

Theme Appearance Apply as Accent

Light surface (rail, connection card, settings — title bar stays white)

Dark surface (rail, connection card, settings — title bar stays dark chrome)

ID / “me” color

Client preview

App

1 234 567

ready to connect

Accent, surfaces and ID color are compiled in. Appearance is written to custom_.txt (default or locked).

Links Custom URL for links (replaces https://rustdesk.com) Custom URL for downloading updates (replaces https://rustdesk.com/download)

Branding

App icon (JPG or PNG, 1024×1024 recommended)

App logo (JPG or PNG or SVG, shown in About)

Access Permanent password Approval mode

Permissions

Tweaks Connection direction In-app installer Settings page

Both land in custom_.txt at build time. Disabling Settings also hides the gear on desktop; disabling the installer removes the in-app install flow (the .msi / .deb you built still works).

Advanced keys

Official RustDesk key=value lines. Default = first-run, the user can still change it if Settings stay allowed. Override = locked. Search or click a key to insert a ready line. Keys already set above are tagged so you don’t have to retype them. Full docs

Click Default or Override on a row. Last box used: Default.

Default settings Override settings (locked)

Distribution signing

Optional. Leave empty to keep local/debug signing (this machine only). Certificates are stored under workspace/signing/ and are not compiled into the client. Linux packages have no Authenticode step.

Windows

Authenticode certificate (.pfx / .p12)

Creates a .pfx named after the app (e.g. SIGNING.pfx) in workspace/signing/. Trusted on this Windows user only — other PCs still see an unknown publisher.

PFX password Timestamp server

Android

Upload keystore (.jks / .keystore / .p12)

Creates a free .jks named after the app (e.g. SIGNING.jks) in workspace/signing/. Back it up — losing it means you cannot update already-installed APKs. Play Store still needs a Play Console account.

Key alias Keystore password Key password (blank = keystore password)

macOS

Signing identity (Developer ID wins if set) Self-signed certificate (.p12)

Creates a .p12 named after the app in workspace/signing/. Used only on a Mac build. If this is empty, DVForge keeps ad-hoc signing so the app still launches on this Mac. Self-signed does not pass Gatekeeper on other Macs. A Developer ID in the identity field always wins.

P12 password Notary API key (.p8 or json)

Notary key id Notary issuer UUID

custom_.txt preview

Written next to the binary as base64 — never raw JSON. Decoded for readability here.

—

Compiled-in values

—

Build

Runs the same steps as the GitHub Actions workflow, on this machine.

RustDesk version idle

Select targets, then Start build. Output streams here.