| Tool | From any browser | A terminal | Your files | Behind any network | Survives a network change | Nothing between reads it | Share exactly | No account elsewhere | Open source |
|---|---|---|---|---|---|---|---|---|---|
| Tailscale | partly | yes | partly | yes | yes | yes | yes | no | partly |
| ssh and mosh | no | yes | partly | no | partly | yes | partly | yes | yes |
| Syncthing | no | no | yes | yes | yes | yes | partly | yes | yes |
| VS Code Remote Tunnels and Codespaces | yes | yes | yes | yes | partly | partly | partly | no | partly |
| Chrome Remote Desktop | yes | partly | partly | yes | partly | partly | partly | no | no |
| youros today | yes | yes | yes | yes | yes | yes | partly | yes |
yes partly no planned here, not built · hover a column for what it means
youros
Your machines and files, from any browser
- From any browser
- A terminalLinux machines today
- Your files
- Behind any network
- Survives a network change
- Nothing between reads it
- Share exactlyyour own devices today; people and agents later
- No account elsewhere
- Open sourcethe repository is not public yet
Tailscale
A private network between your devices, on WireGuard
The best way to put your machines on one network; you still bring the tools.
Better at Mature, on every platform, and any program works over it, not only the ones in a browser tab.
Use it instead? If you want a network, and you'll use ssh, your editor and the rest over it, use Tailscale. They also work side by side.
- From any browseran SSH console in beta, for admins
- A terminalover ssh
- Your filesTaildrop sends files
- Behind any network
- Survives a network change
- Nothing between reads it
- Share exactlyaccess rules per machine and port
- No account elsewheresigns in with an identity provider
- Open sourceclients open; the coordination server closed, Headscale is a rewrite
Searched, 2026-10-24 · source
ssh and mosh
The standard remote shell, and a shell that roams
What everything else is measured against, and it needs a reachable address.
Better at Everywhere already, scriptable, and nothing new to trust.
Use it instead? If your machine has an address you can reach and you have a terminal on the device you hold, use ssh, or mosh on a shaky network.
- From any browser
- A terminal
- Your filesscp and sftp
- Behind any networka port and an address, or a jump host
- Survives a network changemosh yes, ssh no
- Nothing between reads it
- Share exactlya key per user, not per folder
- No account elsewhere
- Open source
From memory, not yet re-checked, 2026-10-24 · source
Syncthing
Folders kept in sync between your devices
The best open way to keep the same folders on several devices.
Better at Mature, fully open, and every device keeps a full copy that works offline.
Use it instead? If you want the same files on each device, rather than reaching one machine, use Syncthing.
- From any browserits web page is for the device it runs on
- A terminal
- Your filesa copy on each device
- Behind any network
- Survives a network change
- Nothing between reads it
- Share exactlya folder to a device, not to a person
- No account elsewhere
- Open source
From memory, not yet re-checked, 2026-10-24 · source
VS Code Remote Tunnels and Codespaces
Your editor on a machine elsewhere, in a browser
The richest editor on a remote machine, through Microsoft's relay and account.
Better at A full IDE, with extensions, debugging and its terminal, already familiar to most developers.
Use it instead? If you want an IDE and a GitHub or Microsoft account is fine, use it.
- From any browser
- A terminal
- Your files
- Behind any network
- Survives a network changereconnects
- Nothing between reads itthrough Microsoft's Dev Tunnels relay
- Share exactlyLive Share, per session
- No account elsewhereGitHub or Microsoft
- Open sourcethe editor is open; the server and the tunnels are not
Searched, 2026-10-24 · source
Chrome Remote Desktop
A machine's screen, in a browser
The easiest way to see and use another machine's whole desktop.
Better at The whole desktop, any program on it, set up in minutes on Windows and macOS.
Use it instead? If you need the screen, not a terminal or files, use it.
- From any browser
- A terminala terminal on the desktop
- Your filesfile transfer
- Behind any network
- Survives a network change
- Nothing between reads itGoogle says every session is encrypted; end to end is not documented
- Share exactlya one-time code for help
- No account elsewherea Google account
- Open source
Searched, 2026-10-24 · source
By need
From any browser
reach it from a browser, with nothing to install on the device you hold
Fully VS Code Remote Tunnels and Codespaces, Chrome Remote Desktop
Partly Tailscale (an SSH console in beta, for admins)
A terminal
a shell on your own machine
Fully Tailscale (over ssh), ssh and mosh, VS Code Remote Tunnels and Codespaces
Partly Chrome Remote Desktop (a terminal on the desktop)
Your files
open and edit a machine's files from elsewhere
Fully Syncthing (a copy on each device), VS Code Remote Tunnels and Codespaces
Partly Tailscale (Taildrop sends files), ssh and mosh (scp and sftp), Chrome Remote Desktop (file transfer)
Behind any network
no port to open, no public address
Fully Tailscale, Syncthing, VS Code Remote Tunnels and Codespaces, Chrome Remote Desktop
Survives a network change
wifi to 5G, and the session carries on
Partly ssh and mosh (mosh yes, ssh no), VS Code Remote Tunnels and Codespaces (reconnects), Chrome Remote Desktop
Nothing between reads it
end to end, even through a relay
Fully Tailscale, ssh and mosh, Syncthing
Partly VS Code Remote Tunnels and Codespaces (through Microsoft's Dev Tunnels relay), Chrome Remote Desktop (Google says every session is encrypted; end to end is not documented)
Open source
and you can run it yourself
Fully ssh and mosh, Syncthing
Partly Tailscale (clients open; the coordination server closed, Headscale is a rewrite), VS Code Remote Tunnels and Codespaces (the editor is open; the server and the tunnels are not)