COMPONENTS
What is open source
MIT licensed infrastructure
- tucdesk-api: Go REST + WebSocket control plane
- tucdesk-rendezvous: Go agent registration and signaling
- tucdesk-turn: Go UDP/TCP relay fallback
Proprietary, freely distributed clients
- Dashboard Docker image: ghcr.io/tucdesk/dashboard:latest
- iOS and Android apps from store channels
- Signed agent binaries and TUI client from releases
WHY THIS MODEL
Auditability without forcing cloud
The protocol, cryptography, API, rendezvous registry, and relay are reviewable and forkable. TucDesk Cloud funds ongoing development, while self-hosters can run the critical infrastructure themselves with no runtime visibility for TucDesk.
RUNNING THE STACK
Start with Docker Compose
git clone https://github.com/TucDesk/TucDesk
cd TucDesk
cp .env.server.example .env.server
docker compose -f docker-compose.server.yml --env-file .env.server up -d█ARCHITECTURE
Same clients, two infrastructure targets
SELF-HOSTED
Your infrastructure
- Dashboard image
- tucdesk-api
- tucdesk-rendezvous
- tucdesk-turn relay
- Postgres, Redis, and S3-compatible storage
MANAGED CLOUD
TucDesk infrastructure
- api.tucdesk.app
- rendezvous.tucdesk.app
- Managed relay fallback
- Managed dashboard and storage
- Hosted updates and security releases
SHARED CLIENT LAYER
DashboardAgentsiOSAndroidTUI