I come from a connection manager
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 its own proxy, 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 proxy on any connection, not only a gateway in front of it.
- Linux as a first-class target, from the same codebase as Windows and macOS.
- Secrets encrypted with a key derived from your passphrase; names and hosts readable so the sidebar loads.
- Folders that hand a route down to every connection inside them.
Side by side
Royal TS and Royal TSX and Vandle
| Aspect |
Royal TS and Royal TSX |
Vandle |
| Platforms |
Windows, macOS |
Windows and Linux now; macOS next |
| Routing |
Secure gateway per connection |
Any SOCKS5 or HTTP(S) proxy per connection or folder |
| Credentials |
Shared credential objects |
Stored on each machine record |
| Pricing |
Per user, per version |
Free |
Moving over
What it takes
Vandle has no shared credential objects yet - credentials live on each machine record. Folders carry over one level deep, there is no importer, and where you used a gateway you will use a proxy route, which can differ per connection.
And the rest of it
The rest came along
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.
Web
A browser with a profile per saved site
SSH
A terminal that keeps up
SFTP
Two servers, no detour
WebDAV
Cloud storage, same view
RDP
Remote desktops, natively
VNC
Any screen that speaks VNC
Database
SQL, Redis and SproutDB in one editor
MQTT
A broker, live
Docker
Containers over the SSH you have
API
HTTP calls with a memory
Dashboards
Your APIs as a control panel
Console
Your own machine, in the same list
Local Docker
The engine on this computer
Files
Your disk, beside your servers