How it works
Three Steps to Better Remote Support.
From a fresh Linux server to fixing someone's computer — here's the whole journey.
The three steps
Set up. Connect. Support.
Step 1: Set Up
Configure the Secure Desk relay and portal on a Linux server you control.
Step 2: Connect
Enroll a device or start an attended support session.
Step 3: Support
Access the session and resolve the issue.
Walkthrough
Watch it come together.
Click a step or let it play.



Connection flow
What happens when you click Connect.
1 · Create or enroll
Sign in to the portal. Send a join link, or open an enrolled device.
2 · Both dial out
The console and the Windows client connect outbound to your relay over WSS.
3 · Pair and key
The relay matches the session; the two ends agree on AES-256-GCM keys.
4 · Work the session
Screen to the console, input back when Control is on. Same encrypted channel.
Setup details
What you'll need.
- A Linux server — Debian or Ubuntu recommended (Node.js 18+)
- PostgreSQL (the Debian installer sets it up for you)
- A public DNS name with ports 80 and 443 reachable
- Windows computers to support, and a modern browser
# download and extract the release, then:
tar -xf secure-desk-*.zip
cd rubix-remote
sudo bash install.sh
# the one-time setup token is printed to the service log:
sudo journalctl -u rubix-relay -e | grep -i 'setup token'
Confirm the archive and folder names against the release you download.
Under the hood
The full session diagram

Free Starter plan · no credit card
Ready to set up your relay?
It takes one command on a Debian or Ubuntu server.