// the find
galaxy-s10/billd-desk
基于Vue3 + WebRTC + Nodejs + Flutter搭建的远程桌面控制、游戏串流
A self-hostable remote desktop client in the ToDesk and RustDesk category. It runs as an Electron app around a Vue 3 and TypeScript renderer, and uses WebRTC so a browser can view or control a machine without installing anything. It suits people who want to run their own relay, and Windows users who care about frame rate and hardware encoding more than typical remote-support use.
- Codec and encoder choices are exposed as settings: H264, H265, AV1, VP8 and VP9, with toggles for encode and decode hardware acceleration and zero-copy. NVIDIA and AMD paths are listed separately. This is the part that determines the frame-rate numbers the README claims.
- Self-hosting is a real path, not an afterthought. The README lists a custom relay server, custom wss and api endpoints, and private deployment, and coturn appears in the topics for TURN relaying. If the relay has to stay inside your own network, that matters more than the feature checklist.
- The adaptive frame-rate mode, which drops frames when the screen is static, and the separate default and low-latency network modes are useful bandwidth trade-offs. A user can reason about them without reading the code.
- The Electron layer is separated into electron-main/ with a preload script, which is where the privileged surface should live. The tree does not show how much input and screen-capture code ends up there, so that part still needs reading.
- The top-level README is a feature checklist for BilldDesk Pro, which its own text says is closed source and paid. The most attractive ticked items (privacy screen, virtual display, screen wall, batch control) are listed as paid features. Check README_OpenSource.md and the code before assuming they are in what you clone.
- The benchmark section is a few single-author test reports on four machines. It gives no latency, packet loss or session-length numbers and says nothing about the capture pipeline. The ToDesk comparison table is also self-authored and quotes competitor pricing that will drift. Read both as the author's view, not as measurements to plan around.
- The stack section names Node.js and Flutter, but the tree shown has no server directory and no Flutter project. iOS and Linux are unchecked. Standing up the relay or the mobile client means finding those components elsewhere, and the README does not say where.
- Nothing in the README covers the security exposure of a self-hosted remote-control server reachable from the internet. There is no threat model, no note on how connection passwords are stored or rate-limited, and no mention of an external review. For software that grants full control of a machine, that gap matters more than the feature list.