An end-to-end encrypted peer-to-peer link between two devices — screen, mouse, keyboard, files and calls go straight across; the server only introduces the two sides, then steps out.
Free · No install needed to try · No account required
One connection handles control, meetings and file exchange.
View and control a remote machine in real time. Multiple monitors supported, switch between them without dropping the session.
Talk to the person on the other end while you work. HD video over WebRTC, low latency.
Drag files across, chunked and sent straight over P2P. Falls back to relay when the network blocks it.
Encrypted chat alongside the control session. Send links, commands and notes.
Keys are exchanged directly between the two machines. The server never holds a key, so it cannot read anything.
Finds a path via STUN, falls back to TURN relay when a corporate network blocks it. No port forwarding.
Same protocol, same account. You decide which machine controls which.
| Operating system | Can be controlled | Can control others | Technology |
|---|---|---|---|
🪟 Windows 10 / 11 |
FullIncluding lock screen and UAC | Yes | Rust + Tauri |
🍎 macOS 13 or later |
FullRequires system permissions | Yes | Rust + Tauri |
🤖 Android 8.0 or later |
YesVia Accessibility Service | Yes | Kotlin + Rust |
📱 iOS / iPadOS 15 or later |
NoiOS does not permit it — an Apple restriction | Yes | Swift + Rust |
🌐 Browser |
NoScreen sharing only, cannot be controlled | Yes | WebRTC |
Designed so the server only introduces the two sides to each other.
Each machine generates its own identity key at install time. The server only receives the public key, so it can decrypt nothing.
Every message uses its own key. Mouse and keyboard commands use a key that exists only for the session, then disappears.
WebRTC's mandatory encryption standard, applied to the screen and audio streams.
Both ends show the same fingerprint string so you can confirm nobody is sitting in the middle.
A fresh 6-digit password on every start. Five wrong attempts lock it out for 15 minutes.
Standard TOTP, works with Google Authenticator. Comes with 10 backup codes in case you lose your phone.
Who connected, when, and for how long. No API can delete it — not even the machine's owner.
Exactly two ways to control a machine — there is no third.
The person wanting in sends a request. You see exactly who is asking, then choose how long to allow. When time runs out the permission disappears and any running session is cut immediately.
Machines signed into the same account recognise each other and work permanently, with no approval prompt. Office machine, home machine — reachable any time, even with nobody sitting there.
Nothing to add by hand — a machine appears in the list the moment it signs in
The web version works right now. Windows and Android are ready to download; macOS and iOS are in progress.
Sign in with the same account, or use the device code shown on the main screen.
The device list shows online status in real time. Click to call.
The other side approves or enters a password. The P2P connection comes up and you get to work.
Completely free, including for business use. No time limit per session, no cap on the number of devices, and no paid tier that unlocks extra features.
Not if you only need to control another machine — open your browser and it works, no account required. Only the machine BEING controlled needs the app installed, because a browser is not allowed to inject mouse and keyboard input into the operating system.
Nobody gets into your machine unless you approve it, or unless they have a password you set yourself. While a session is running, a red bar you cannot dismiss stays on screen with a stop button. Data travels directly between the two devices and is end-to-end encrypted, so the server cannot read it.
No — and that is an Apple restriction that applies to every remote desktop app, not just Chat Remote. iOS does not let third-party apps capture the screen in the background or receive input events. Using an iPhone or iPad TO control another machine works fully.
Your data does not pass through our server: the two devices connect directly, and the content is encrypted with keys only the two endpoints hold. The server just introduces the two sides and then stays out of the way. On top of that, the web version works immediately without installing or signing up.
Yes. The customer only has to read you the device code and the 6-digit password shown on their screen. To reach a machine when nobody is sitting at it — an office server, for instance — set a permanent password for that machine; the owner is notified every time someone connects that way.
Report a bug, ask for a feature, or just say something — we read all of it.
Open the web app in two different browsers to watch the P2P connection work.
Open web app