End-to-end encryption
Sessions are encrypted peer-to-peer. Our self-hosted ID and relay servers only coordinate connectivity — they never hold your session content in the clear.
Self-hosted · End-to-end encrypted · Branded
Private remote desktop under your control
Desk is a production-ready remote access platform built on hardened open-source foundations. Authenticated users download a branded client, connect through our self-hosted rendezvous and relay servers, and work without third-party telemetry.
TLS on the web edge
E2E session encryption
No public rendezvous servers
<15m
First session
E2E
Session crypto
OSS
Proven stack
Built for controlled remote access
Desk focuses on reliability and security for support teams, operators, and private infrastructure — not consumer screen-sharing gimmicks.
Full desktop control
Multi-monitor, clipboard sync, file transfer, audio, and unattended access with permanent passwords or keys for host machines under your custody.
Desk-branded client
Downloadable packages ship pre-pointed at Desk infrastructure with branded install helpers — no public server defaults, no surprise telemetry endpoints.
Secure downloads
Short-lived signed download tokens, optional single-use links, SHA-256 checksums, rate limiting, and audit logging of every issue and fetch event.
Self-hosted stack
Rendezvous (hbbs) and relay (hbbr) run on infrastructure you operate. Docker Compose deploy scripts make greenfield installs reproducible.
Ready for growth
Architecture leaves room for MFA/SSO (OIDC), multi-tenant admin, and managed fleets without rewriting the connection plane.
Secure client download
Enter your access code to unlock platform packages. Links expire quickly and are logged. Verify the SHA-256 checksum after download.
Authenticate
Access codes are issued by your Desk administrator. Demo environments may use a shared invite code.
What you receive
- Desk-packaged remote desktop client for your OS
- Preconfigured ID server and public key for our infrastructure
- Install helper scripts and a short First Session guide
- SHA-256 checksum displayed before and after token issue
Prefer not to install? Ask your admin for a supervised session or browser-based guest path when enabled for your tenant.
First session in four steps
Non-technical friendly path from landing page to working remote desktop.
Unlock download
Use the access code from your invite email or administrator.
Install Desk client
Run the Windows installer or Linux package. Keep the default Desk server settings.
Note your Desk ID
On the host machine, open Desk and copy the ID (and set a strong permanent password if unattended).
Connect
From your client PC, enter the host ID and password. You should reach the desktop within seconds.
Full guide: docs/FIRST-SESSION.md (shipped with the package and in the repository).
Security & privacy
Desk is designed around least privilege, short-lived credentials, and data residency under operator control.
Non-negotiables
- End-to-end encryption for remote sessions
- No plaintext credentials stored for downloads (HMAC-signed tokens only)
- Expiring download links; single-use where practical
- TLS at the web edge; strong defaults on the connection plane
- No third-party telemetry enabled by default
- Prepared for future MFA / OIDC SSO integration
Privacy statement
Connection metadata (IDs, timestamps, download events) may be logged on infrastructure we operate for security and support. Session content is not inspected. Data residency remains under our operational control — we do not route traffic through public third-party rendezvous networks.
Contact: security@webservice.digital