galaxy-s10/billd-desk

BilldDesk targets people who want ToDesk-style remote control without per-minute limits or a vendor account: run the hosted service, or start from the open-source edition and deploy your own relay and signaling. It is less a finished drop-in replacement than a stack to evaluate and operate.

The problem

Remote support usually starts with installing a client on both ends, signing into a commercial account, and accepting session and bandwidth caps. BilldDesk changes that workflow: a controlled machine runs a client, and the controlling side can be another desktop client, an Android device, or just a browser tab. For teams managing several machines, the screen wall and batch control let one operator view or drive many devices instead of opening sessions one by one. The result is a remote-control setup whose relay, API and device codes you configure yourself.

What's different

The stack is built around WebRTC with H.264/H.265, AV1 and VP8/VP9 codecs, and it exposes hardware encode/decode acceleration and zero-copy toggles for NVIDIA and AMD GPUs. That matters most for game streaming or high-frame-rate desktop work: the README reports tested combinations up to 2K at 120 fps on a Windows 11 host with an RTX 5070, and 1080p at 60 fps on older GTX cards. Hardware acceleration is optional, but the documented NVIDIA path expects driver version 570.0 or newer. Driver-level keyboard and mouse simulation and multiple mouse modes are aimed at avoiding game anti-cheat friction, a claim only the project makes, not an independently verified result. The trade-off is breadth: this is a multi-component system spanning a Flutter/Vue client, Koa2 backend and native capture code, so getting it running is closer to deploying an application than installing a utility. Privacy screen, virtual screen, screen wall and high bitrate/frame rate tiers are positioned as paid features in the hosted Pro product, while the open-source edition lists a narrower feature set.

Who should try it

It fits a developer or small IT team that already runs servers and wants browser-based access to Windows or Android machines, or wants to experiment with WebRTC game streaming on a LAN or self-hosted relay. It also suits someone who needs unattended access after reboot on Windows, which the Pro client documents via startup and process keep-alive. It is a poor fit if you need iOS or Linux control today, or if you want a turnkey installer with no backend to operate. If you only need occasional remote support, the hosted demo is the lower-commitment path; the open-source repository is the right entry point if you intend to self-host.

Requirements and limitations

Platform coverage is uneven and stated explicitly: Windows 10/11 and Server 2019/2022, macOS 15, Android 8-16 and major browsers are supported or tested; Windows 7, iOS and Linux are not. Android 7 can watch but not be operated remotely. That rules out mixed fleets with iOS or Linux machines and means older Windows hardware is out of scope.

Self-hosting is the bigger commitment. The README lists custom relay servers, custom WSS/API endpoints and private deployment as features, and Docker one-click deployment is still an unchecked item, so expect to wire up components such as coturn and the Node backend yourself. Ongoing work includes keeping the relay reachable, updating clients, and checking GPU driver compatibility for hardware acceleration. The open-source edition also does not include the full Pro feature list, which is documented separately.

HotRepo's take

HotRepo recorded 8,942 stars and +81 in a single daily-board observation on 2026-10-27; the sample spans only that date, so persistence and momentum cannot be judged. The project's own comparison table and the hosted demo are the most useful next checks: confirm whether the open-source edition covers the specific host/controller pair you need before planning a deployment around it.

Project source and documentation