Moving over
What it takes
Keep Edge for the appliances that need its rendering mode, and for the web. Everything with an SSH port belongs on a Vandle record.
You already organise work into workspaces
Workspaces group tabs by task, which is most of the way there. Vandle groups by machine instead, and each group brings its protocols with it: the web interface, the shell, the files, the desktop.
Credit where it is due
Edge's workspaces and profile handling are well judged, it is the path of least resistance on a managed Windows fleet, and legacy-mode rendering still rescues appliances nobody will ever update.
What changes
Four things you get that you did not have.
- Grouping by machine, with one row per protocol, so a server's web interface sits next to its shell.
- A route per connection rather than the system proxy your fleet policy set.
- Credentials stored encrypted on the connection, decrypted only in memory.
- The same client and inventory on Linux and macOS.
Side by side
Edge and Vandle
| Aspect | Edge | Vandle |
|---|---|---|
| Grouping | Workspaces of tabs | Folders of machines, one row per protocol |
| Proxy | System policy | A route on the connection |
| Legacy appliances | Legacy rendering mode | Keep Edge for the handful that need it |
| Beside the page | Another tab | Terminal and file surfaces on the same record |
And the rest of it
Four more protocols came along
Replacing one tool gets you five. Whatever else that machine speaks is already a row on the same record - and every one of them takes the route you assigned.
Web
Real browsing, properly routed
SSH
A terminal that keeps up
SFTP
Two remote panes, no detour
WebDAV
The other half of file transfer
RDP
Desktops on a native surface
Local
Your own machine, in the same list
Also compared