Moving over
What it takes
Credential objects and folders carry over conceptually; where you used a gateway, you will use a route, and it can differ per connection.
You already keep a tidy estate
Royal TS is the polished end of this category, and its credential objects and documents are the right abstractions. Vandle's difference is the routing model: any connection can carry any route, not only the gateway it was designed around.
Credit where it is due
Royal TS is well built, covers a wide protocol range on Windows and macOS, and its separation of credentials from connections is a pattern more tools should copy.
What changes
Four things you get that you did not have.
- A route object on any connection, not only a gateway in front of it, and switchable while the session runs.
- Linux as a first-class target, from the same codebase as the other two.
- Zero-knowledge state layout: metadata readable so the sidebar loads, hosts and secrets encrypted until you unlock.
- Live sync through change notifications: change a connection on one machine and the other updates without a file merge.
Side by side
Royal TS and Royal TSX and Vandle
| Aspect | Royal TS and Royal TSX | Vandle |
|---|---|---|
| Platforms | Windows, macOS | Windows, Linux, macOS |
| Routing | Secure gateway per connection | Any route per connection or folder, including a tunnelled path |
| Sharing | Documents on a share or a server | One central store with live change notifications |
| Pricing | Per user, per version | One client |
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