Moving over
What it takes
Keep your VNC client for servers that insist on TLS, VeNCrypt or a vendor sign-in; every other VNC screen opens in Vandle, on the same record as the machine's shell and files.
VNC's virtue is that it is simple and everywhere. Vandle speaks it too, and puts the protocols most of those boxes also run - SSH and files, and RDP where there is one - on the same record, each with a route of its own.
Credit where it is due
VNC is an open protocol with an implementation for everything, and for a headless box on a local network it is often the least complicated thing that works.
What changes
Side by side
| Aspect | RealVNC, TigerVNC and other VNC clients | Vandle |
|---|---|---|
| Protocols | VNC | VNC beside RDP, SSH, files and the web |
| Security types | TLS, VeNCrypt and vendor sign-ins, depending on the client | No authentication or a VNC password; no TLS or VeNCrypt |
| Routing | An SSH tunnel you set up separately | A proxy on the connection, used whenever it opens |
| Beyond the screen | Not covered | Terminal and file transfer for the same machine |
Moving over
Keep your VNC client for servers that insist on TLS, VeNCrypt or a vendor sign-in; every other VNC screen opens in Vandle, on the same record as the machine's shell and files.
And the rest of it
Replacing one tool gets you all of them: a browser with a profile per saved site, shells, files, desktops, databases, MQTT brokers, containers, APIs and dashboards - each a tab in the same window, each taking the route you gave it. And all of it free.
Also compared