Documentation

Secure Desk Documentation

Install, configure and operate self-hosted remote support and web VDI.

Get started with Secure Desk

Everything you need to install, configure and start providing secure remote support. New here? Follow the four-step quick start below.

Three parts. One secure connection.

Secure Desk brings your support team and Windows devices together through a connection you control. The naming below is used consistently across the product and these docs.

Agent
The technician giving support. They work in the browser console — view the screen and send mouse and keyboard when Control is on.
Client
The Windows machine receiving support. It captures and shares its desktop and receives input.
Relay
Your Linux server. It serves the portal, join page and console, pairs an Agent and a Client, and forwards bytes between them.
outbound · encrypted outbound · encrypted Your browser Technician console Your relay Forwards ciphertext Windows PC Client or service outbound · encrypted outbound · encrypted Your browser Technician console Your relay Forwards ciphertext Windows PC Client or service

Quick start: up and running in 4 steps

  1. Install your Secure Desk server

    Prepare a Linux server, assign a public DNS name, and run the installer: sudo bash install.sh. Installation instructions

  2. Complete your initial setup

    Open the setup page with the one-time token printed during installation. Create your administrator account and configure TLS. Portal setup

  3. Activate your license

    Request your free license, then sign in to your portal and go to Settings → License to activate it. Licensing instructions

  4. Connect your first Windows device

    Create a support session and share the link with the user. For ongoing access, install the Windows client as a service. Device setup

Before you begin

  • A Linux server — Debian or Ubuntu with Node.js 18 or newer. Developed and tested on Debian with Node.js 22.
  • A database — PostgreSQL for production. The Debian installer can configure this for you.
  • A domain and secure connection — a public DNS name with ports 80 and 443 accessible for HTTPS and certificate setup.
  • Windows devices — supported Windows computers for remote support, and a modern browser for technicians.

Take a look inside your portal

Your dashboard gives you an overview of devices, sessions and support activity as soon as your portal is running.

your-domain.com/portal
Secure Desk portal dashboard

Something unclear or missing? Tell us and we'll improve this page.