Features
NexaDesk is designed for authenticated, consent-gated remote access over self-hosted infrastructure. Current implementation provides the session foundation; graphical capture, input control, and file transfer are planned.
Available now
Reliable foundation
A focused foundation for dependable, authenticated sessions with a small and carefully controlled footprint.
Authenticated encrypted sessions
Every connection is protected and tied to an approved session. The current Linux command-line foundation supports authenticated remote access.
Consent-gated connections
Explicit authorization required for every connection. Sessions require approval from the remote device with visible requester identity.
Recognizable device trust
Devices establish trust on first connection and show a recognizable identity on future connections.
Linux command-line host and client
A lightweight Linux command-line foundation for authenticated remote sessions and explicit approval.
Planned
Self-hosted deployment Planned
Planned deployment on infrastructure you control. Public cloud, relay, and download services are not part of the current release.
Graphical screen capture Planned
A future desktop experience for viewing an authorized screen. Not yet available.
Remote input control Planned
Planned mouse and keyboard control, with separate permission for each session.
File transfer Planned
Secure file transfer with confirmation before each transfer. Not yet available.
Clipboard synchronization Planned
Optional clipboard sync between devices. Off by default; explicit per-session toggle. Planned feature.
Windows client Planned
A planned desktop experience for viewing and controlling an approved connection across supported platforms.
Device discovery and relay Planned
Planned connection support to help devices find each other and stay connected when a direct path is unavailable.
Releases and downloads Planned
Verified downloads for supported platforms will appear here when a release is ready.
How a consent-gated session works
Every connection requires explicit approval from the remote device user. No silent or automatic access.
Learn More
Review the security model and implementation documentation to understand current capabilities and planned features.