DeskRallyThe roadbook / Self-hosting
Self-hosting
Here is what you will be running.
DeskRally has a browser console, server services, and Windows agents. Running your own setup means maintaining those components and the infrastructure that connects them.
This guide covers the architecture and planning. I will add versioned build and installation instructions with the source release.
How the components fit together
WebRTC carries session media. Relay infrastructure helps when the computers cannot make a direct connection.
- Web console
- The browser interface uses React and TypeScript.
- Control plane and connection services
- Go services handle the API, signaling, and relay work.
- Windows agent
- Rust components handle the remote computer side of the session.
- Database
- PostgreSQL stores the application records. It should stay private to your setup.
- STUN/TURN
- These services help computers connect across different networks. Include relay capacity in your planning rather than assuming every connection will be direct.
What to plan for
- A server environment for the application services and database.
- A domain and HTTPS certificates for browser access.
- A reachable STUN/TURN setup and the necessary network rules.
- Windows computers for the agents, with permission to install the software.
- Backups, monitoring, updates, and a way to recover administrative access.
Keep public and private services separate
The public project website and your authenticated console do different jobs. Database ports and internal service listeners should not be exposed as public websites. Use credentials specific to your setup, and keep private signing material out of source control.
What you will need to maintain
You will be responsible for accounts, access policies, agents, network configuration, backups, and updates. Start with a small test setup and check both connectivity and permissions before relying on it for other people’s computers.