Ask Secure Desk a question. Answers come from this site's docs only. I will cite a page. I will not invent a product claim.
About Secure Desk
Self-hosted remote support and web VDI on a relay you run
We built the path as if the relay were already compromised — and then made it something you run yourself, rather than something you have to trust a vendor cloud with.
Most desktop-access products terminate the session on the vendor's servers. That is a reasonable engineering choice and an uncomfortable security one: a console that can view any screen, type anything, and — if it offers privilege escalation — run commands as SYSTEM has a blast radius of every machine in the fleet if the middle is compromised.
Secure Desk takes the other route. The browser console and the Windows machine run their own key exchange through the relay and encrypt everything above it, so the relay pairs two sockets and forwards opaque bytes. Both ends dial out, so nobody opens an inbound firewall rule. And because the relay is software you install on your own host, we never hold the keys — the vendor cannot watch the session.
What it actually does
Persistent Windows desktops in the browser — web VDI through a relay you operate. Isolated sessions for a fleet of AI-agent desktops; Desk does not run the agents. Attended support from a one-time join link is one use case on the same pipe. Unattended access to enrolled devices through a Windows service that works before anyone logs in. A SYSTEM shell that needs no desktop. Verified file transfer, multi-monitor, two-way clipboard, and a voice call inside the session. Portal identity with TOTP or SSO, three roles, and an audit log.
What it does not do
It does not capture the Windows secure desktop — UAC prompts and Ctrl-Alt-Del stay out of reach, though the sign-in and lock screens are handled. It runs Windows endpoints only. It is not a compliance certificate: it gives you encrypted transport, a scope-reducing relay design and the identity and logging hooks a PCI assessment needs, but validating that assessment is your work and your assessor's. We would rather tell you that here than have you discover it during a rollout. It is not Azure Virtual Desktop, Citrix or Omnissa — no published app stacks, no GPU pools.
What we stand for
The relay is not a trusted party
Screen frames, keystrokes, shell bytes and file chunks are encrypted by the endpoints before they leave. Even the relay you run yourself is treated as infrastructure that could be compromised.
You host it, so you can audit it
One Linux host, a PostgreSQL database and a DNS name. No vendor tenancy to trust, no session data leaving your perimeter, and licence checks that verify offline so a network outage is not a lockout.
Portal identity is separate from OS identity
Your portal decides who may open a desktop. The Windows machine keeps its own security entirely — we never join, trust, or authenticate against a customer domain to do our job.
Evaluate on a host you control
Starter is 1 operator and 3 enrolled desktops. The relay is yours either way.