Initial planning workspace for a self-hosted RustDesk OSS control plane.
Currently V.1 ALPHA -- working with caveats.
Goal: keep the official RustDesk clients and OSS hbbs/hbbr remote access stack, then build a full RustDesk Server Pro replacement control plane. OpenDesk provides the management value currently expected from Pro through our own web app, API, deployment tooling, inventory, policy, monitoring, backups, and validation discipline.
Production target:
- RustDesk domain:
rd.example.com - Current host context: Proxmox LXC on
root@LAN_HOST - Remote access engine: RustDesk OSS server and official RustDesk clients
- Management layer: custom app developed in this repository
- Initial Tape-Out
- Requirements
- Architecture
- Software Stack
- Feature Checklist
- Validation Matrix
- Validation Lab
- Client Delivery Plan
- Upstream Findings
- Pro Feature Parity Map
- Threat Model
- Architecture Decisions
- Cutover Readiness
- CI Plan
- Traceability
- Engineering Standards
- Research Roadmap
- Research Findings
- Research Status
- Owner Decision Worksheet
- Client Validation Procedures
- Dev Validation Environment
Use the official signed RustDesk apps wherever possible. Do not fork the RustDesk client unless an important workflow cannot be solved through external management, install automation, or endpoint self-registration.
Forking or vendoring RustDesk OSS server/client code is deferred until a specific full-replacement requirement cannot be met through the external control plane, deployment automation, endpoint registration service, or compatible APIs.
Local upstream reference clones may exist in upstream/, which is intentionally ignored by Git.
The first build slice is a Rust control plane service (Axum, Askama, sqlx/SQLite).
cargo test
OPENDESK_LISTEN_ADDR=127.0.0.1:8080 cargo runDefault bootstrap admin credentials come from OPENDESK_BOOTSTRAP_ADMIN_USERNAME and OPENDESK_BOOTSTRAP_ADMIN_PASSWORD (change before any real deployment).
Compose deployment:
docker compose up --build