Moving over
What it takes
Keep Safari for browsing. Give the devices a record, and the certificate prompt stops being a daily decision.
Your admin interfaces deserve better than a tab group
Safari is the right browser for a Mac and the wrong place for a self-signed certificate on a device with no DNS name. Vandle handles exactly that class of address.
Credit where it is due
Safari is fast, easy on the battery, and tab groups plus iCloud sync make it the most comfortable browser on Apple hardware.
What changes
Four things you get that you did not have.
- Internal hosts as connection records, with port, credentials and route stored once.
- The shell for the same device one row away from its web interface.
- A route per connection, so a device behind a jump path needs no tunnel you start by hand.
- The same inventory when you are on Windows or Linux that day.
Side by side
Safari and Vandle
| Aspect | Safari | Vandle |
|---|---|---|
| Sync | iCloud, Apple devices | A store you point at, on any platform |
| Internal devices | Certificate warnings and bookmarks | Records with a route and stored credentials |
| Proxy | System settings | Per connection |
| Beside the page | A tab group | Terminal, files and desktop on one 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