✦The replacement checklist
What to look for in a replacement
Six tests, written against the specific trade-offs of a self-hosted, cross-platform tool like RustDesk. If a candidate fails one, you'll feel it within the first session.
- Native apps, not a shared UI skin
- Look for a per-platform native app that drives each OS's hardware encoder, decoder, and input pipeline directly — not one Flutter or web-view interface stretched across every platform. That's where both the feel and the latency come from.
- A zero-setup relay
- The relay should just exist — a managed service with credentials that rotate automatically — not a VPS you provision, patch, and monitor, and not a public server you have to hope is not overloaded today.
- Simple pairing, no ID to write down
- A short one-time PIN with an expiry window beats a 9-digit device ID plus a password you have to store somewhere safe. Both skip a central account — only one of them is actually simple to use.
- End-to-end encryption stated plainly
- Session keys should be negotiated directly between your devices so a relay in the middle only ever forwards ciphertext. Look for that claim stated outright, not one whose strength quietly depends on how you configured your own server.
- Full platform coverage without server ops
- You should be able to reach a machine on any supported platform without first deciding whether to trust a shared public relay or run your own. If the answer to "can I connect" depends on infrastructure you own, that's a cost the tool is quietly passing to you.
- Free is fine — convenience matters too
- Being free is good, and RustDesk already is. The bar for a genuine upgrade is that free doesn't also mean becoming your own sysadmin to get a fast, reliable session.