What is self-hosted remote support?
Self-hosted remote support is a technician connecting to a real Windows machine the user already has. Both ends dial out to a relay you run, share a 6-digit SAS, then run ECDH. The relay forwards ciphertext. It is not VDI. It is not TeamViewer-cloud-in-the-middle.
Is this VDI? No.
A technician connects to a real Windows machine the user already has. Nothing is streamed from a datacenter desktop. If you want Citrix or Horizon, this is the wrong product.
Both ends dial out, 6-digit SAS, ECDH, ciphertext
The user runs the portable client; the console opens in a browser. Each side connects outbound over WSS to the relay you run and presents the session id plus its token. Neither needs a public IP or an inbound firewall rule. The relay pairs them and nothing else.
Both ends derive the same 6-digit short authentication string from the agreed key material. Read it aloud to the user. The two endpoints then run an ECDH exchange through the relay and derive their own AES-256-GCM keys. The relay never gets a key. Compromise the relay and you get pairing metadata and ciphertext, not screens or keystrokes.
Not TeamViewer-cloud-in-the-middle
You host the portal and the relay. There is no vendor cloud in the path. A vendor-hosted relay puts the operator of that host inside the confidentiality boundary. The comparison that matters is on the TeamViewer page.
AI only as agent-desktop access
Secure Desk does not run the agents, and it does not watch sessions with AI. The named use case is reaching Windows desktops they already run on: enrol once, backstage SYSTEM, no inbound RDP. That page is AI-agent desktops.
The session walk-through is on how it works. Start free or read the security model.