Self-hosted remote desktop

Remote control for your whole fleet

Screen and input travel straight between the two machines over WebRTC — encrypted end to end, on a relay you run yourself.

How it works

Three steps to a remote session

No port forwarding, no VPN, no per-seat licence.

Install the agent

Run the agent installer on the PC you want to reach. It shows a nine-digit ID and a password.

Share the ID

Hand the ID and password to whoever is connecting, or enrol the machine into your organisation so it appears in the dashboard.

Connect and control

Open Remotler, enter the ID and password. The remote screen appears and your mouse and keyboard drive it. Ctrl+Alt+End ends the session.

Why Remotler

Built so the server stays out of the way

The relay brokers the introduction and then steps aside.

Direct peer-to-peer

Video and input flow straight between the two machines over WebRTC. The server only exchanges the initial handshake.

Encrypted end to end

DTLS-SRTP secures the media and data channels. The relay never sees pixels or keystrokes.

Works through NAT

STUN finds a direct path where one exists, with a TURN relay as fallback for networks that refuse to hole-punch.

Fleet management

Groups, users, enrolment tokens, session history and an activity log — all in one dashboard.

Self-hosted

Runs on your own server. Your devices, your data, your relay, your rules.

Native Windows apps

Single-file installers that bundle the .NET runtime. Nothing to install first.

Pricing

Free while we're in beta

One plan, everything included. We'll give plenty of notice before that changes.

Beta
Free

No card required

  • No device or user limits during the beta
  • Direct peer-to-peer sessions, with relay fallback
  • Groups, roles and enrolment tokens
  • Session history and activity log
Get started