Web VDI on a relay you run. Not a support dongle.

A Windows desktop, in a browser, on your relay

Open the console in any modern browser. Land on a real Windows machine you already run — a laptop, a lab VM, a locked-down host that never gets a public IP. Both ends dial out over WSS to the relay you host. Neither side needs an inbound firewall rule.

That is web VDI, self-hosted VDI, browser VDI: the desktop is persistent, the path is yours, and the session is not a ticket that expires when the helpdesk hangs up.

Not Azure Virtual Desktop, Citrix or Omnissa

Those stacks still sit in a vendor control plane. They publish app stacks, pool GPUs, and broker desktops the vendor designed the farm around. Desk does not claim that feature set. No published applications. No GPU pools. Windows endpoints only.

What you get instead is the machine you already have, in the browser, through infrastructure you operate. If you need Citrix published apps or an AVD host pool, this is the wrong product.

The relay cannot watch

After pairing, the browser console and the Windows endpoint run an ephemeral ECDH P-256 exchange and derive AES-256-GCM keys — one per direction. Both ends show the same 6-digit SAS. Read it aloud and a relay that tampered with the exchange is exposed. Compromise the relay and you get pairing metadata and ciphertext, not screens or keystrokes.

Support is one use case, not the product

A technician can still send a join link and take the keyboard. That is how self-hosted remote support works, and it is still here. It is not the whole product. The same pipe carries a standing desktop you open from the browser whenever you need it.

The same relay for a fleet of AI-agent desktops

Many agents, each with its own Windows desktop, on one relay you run. Sessions are isolated. The relay still cannot watch. Desk does not run or orchestrate the agents — it is how those desktops stay reachable. That page is AI-agent desktops.

Read how a session works, the security model, or start free.