Signed release
Verify what you install
Release manifests, SHA-256 checksums and code-signing identity make the production package traceable.
DOWNLOAD
Windows first.
Make the first connection dependable.
The current production client prioritizes Windows connection stability, session quality and a trustworthy upgrade chain. Web pages manage accounts and authorization; remote sessions stay in the native client.
Trusted native remote sessionsWeb manages identity and authorization; native clients carry control and media.
First connection
Install, bind, connect
After device binding JDesk automatically attempts LAN, P2P and then Relay.
Platform roadmap
Expand without weakening the Windows baseline
Additional native platforms follow real demand and capability readiness rather than being advertised before they are production-ready.
Start with secure remote access, then add what you need.
Core remote access remains simple; advanced performance and governance are enabled by published entitlements.