In development — join the early-access list and be first to run it.
RemoteMyDesktop

Secure remote desktop · for every platform

Reach any machine you own — safely, and on your say-so.

RemoteMyDesktop links Windows, macOS, Linux, Android and iOS over an end-to-end encrypted connection that does nothing until the person at the keyboard grants it. No account to create. No screen a middle server can read.

Free while in beta · no spam, one email when it's ready to run.

  • Windows
  • macOS
  • Linux
  • Android
  • iOS
End-to-end encrypted No account required Open protocol — Noise XX Memory-safe Rust core Self-hostable relay

Most remote-desktop tools ask you to trust a company with the keys to your machine. We took the opposite bet: the connection is encrypted end to end, the relay in the middle only forwards sealed bytes, and nothing happens on your computer until you grant it — in plain sight, one capability at a time.

01 Every platform

One app, every screen you own.

The same consent model and the same encryption, whether you're at a desk or on a phone. We're building all five in the open — here's where each one stands.

Windows

10 & 11, 64-bit. The desktop host and controller, with DXGI capture and hardware H.264 video.

In development

macOS

Apple silicon & Intel. ScreenCaptureKit capture and VideoToolbox encoding on the roadmap.

In development

Linux

Debian, Ubuntu, CentOS, Fedora and friends. X11 capture is landing; Wayland next.

In development deb · ubuntu · centos · fedora

Android

Phones & tablets. Control a machine from your pocket, or let a helper see your screen.

Planned

iOS & iPadOS

iPhone & iPad. The same encrypted connection, pocket-sized.

Planned

Want it on your platform first?

Tell us where you need it and we'll let you know the moment that build is ready.

Join early access

02 What you get

Built for people who read the permission dialog.

Encrypted end to end, by construction

Keys are agreed directly between the two machines with the Noise XX handshake (X25519, ChaCha20-Poly1305). The relay forwards ciphertext and never holds a key — there is no server that could watch your screen even if asked.

Consent is the default, not a setting

A new session is view-only until you decide otherwise. Control, clipboard and file transfer are each a separate grant — revocable, and announced by a session indicator the software will not let the other side hide.

Connect by Desk ID

Every machine gets a permanent nine-digit ID. Read it out, type it in, and the two computers meet over port 443 — through NAT and office firewalls — or go straight across the LAN with no relay at all.

Host-key pinning catches imposters

The first time you connect, the machine's key is pinned to its address. If a different key shows up later — a man in the middle, or a quietly reinstalled host — the session stops before a single keystroke is sent.

A log you can actually trust

Every connection, grant and file lands in a hash-chained audit record. Tamper with one line and the chain no longer verifies — so the history of who did what stays honest.

Files, moved carefully

Transfers are capped, checked against a SHA-256 the sender computes as it streams, and the name is sanitised so a file can never land outside the folder you chose. No path tricks, no overwrites.

03 Use cases

Made for the way you actually work.

IT support & helpdesk

Jump onto a colleague's machine the moment they read you their Desk ID and tap Allow. Take control or move a file only when they grant it, and hand them an audit trail of exactly what happened.

Your office desktop, from home

Reach the machine on your desk over port 443 — through the office firewall, no VPN to configure. Low-latency H.264 video makes it feel like you never left.

All your own devices

Hop between your laptop, home PC, phone and tablet without a cloud account holding the keys. Your devices, your connection, nobody in the middle.

Servers & headless Linux

Reach a box by Desk ID through a firewall on 443, or drop onto its terminal over the same encrypted channel. Pin its key once and trust it for good.

04 How a session starts

Three decisions, and you're in.

  1. 1

    Open it on the machine you want to reach

    Install and launch. The app shows that machine's nine-digit Desk ID and a note that it is now reachable — nothing is shared yet.

  2. 2

    Type the ID on the other end

    The two computers find each other through the relay on 443 (or directly on the LAN) and perform a mutual handshake, agreeing on keys no one else — not even the relay — can read.

  3. 3

    Grant exactly what you mean to

    View only? Control too? Files? Each is a separate yes at the host, shown on screen for the whole session and revocable at any moment.

05 Under the hood

We'd rather show you how it works than ask you to trust us.

The hard parts — the key exchange, the permission checks, the framing that reads untrusted bytes — are small, deliberate, and written in memory-safe Rust. Here is what that buys you.

Forward secrecy

Each session negotiates fresh ephemeral keys. A key captured today cannot unlock a recording of yesterday.

No plaintext in the middle

Screen, input and files are sealed on your machine and opened only on the other. The relay routes bytes it cannot read.

Least privilege, always

A single authorization checkpoint gates every capability. View-only is the floor; nothing exceeds what you granted.

Mutual authentication

Both ends prove their identity in the handshake. Device identities are derived from their keys, not a name anyone can claim.

Bounded by design

Every frame and message is length-checked before a byte is allocated, so a hostile peer cannot exhaust your memory.

Open about the model

The protocol is standard Noise XX, documented and inspectable — not a proprietary box you have to take on faith.

Noise XX · X25519 · ChaCha20-Poly1305 · BLAKE2s · SHA-256 device IDs · TOFU host-key pinning

06 Pricing

Free for your own machines. Fair when it's your business.

Planned pricing for launch. Early-access members keep the beta free and get founder rates when paid plans arrive.

Personal

Free

For your own devices and helping family or friends.

  • End-to-end encryption
  • Consent model & session indicator
  • Connect by Desk ID or LAN
  • File transfer
Join early access
Most will want this

Pro

$7/ month

For professionals who support a handful of machines.

  • Everything in Personal
  • Unattended access to machines you own
  • More concurrent sessions
  • Priority support
Join early access

Business

$20/ seat / month

For teams that need an audit trail and control.

  • Everything in Pro
  • Exportable audit log
  • Team & device management
  • Self-hosted relay option
Talk to us

Prices shown in USD, indicative and subject to change before launch. Volume and non-profit rates on request.

07 Early access

Be first to run it.

We're building RemoteMyDesktop in the open, platform by platform. Leave your email and we'll send you the first build for your system — Windows first, the rest close behind — plus the occasional note on what we shipped. No noise.

No spam, no selling your address. Unsubscribe in one click.

08 Questions

The ones people actually ask.

When can I download it?

RemoteMyDesktop is in active development. We're finishing the Windows build first, with macOS, Linux, Android and iOS close behind. Join the early-access list and we'll email you the moment there's a build to run on your platform — no public download until it's ready.

Can the relay see my screen?

No. The two machines agree on encryption keys directly; the relay only forwards the sealed bytes between them and holds no key. It cannot read your screen, your keystrokes or your files. On a LAN you can skip the relay entirely.

Do I need to create an account?

Not to connect. A Desk ID is derived from the machine itself, and a LAN or Desk-ID session needs no sign-up. Accounts come in only with the paid team features.

What stops someone impersonating my machine?

The first connection pins the host's key to its address. If the key ever changes — a man in the middle, or a reinstalled host — you're warned and the session is refused before any data is sent. You can also verify the device ID out of band.

Is the security something I can inspect?

Yes. The handshake is the well-studied Noise XX pattern, the transport is ChaCha20-Poly1305, and the sensitive core is written in memory-safe Rust. The design is documented rather than hidden.

09 Get in touch

A real inbox, read by real people.

Questions about Business, a partnership, a security report, or just curious where we're at — send it over. We answer in plain language.

Or email us directly at hello@remotemydesktop.com.