Moving over
What it takes
Keep Firefox as your browser. Let Vandle hold the interfaces that only exist inside your own networks.
Containers separate cookies. They do not separate networks.
Multi-account containers were the right instinct applied to identity. Vandle applies the same instinct one layer down: every connection gets its own network path, chosen per connection rather than per browser.
Credit where it is due
Firefox is independent, container tabs are a genuinely good idea, and it is one of the few browsers that lets you set a proxy without touching the operating system.
What changes
Four things you get that you did not have.
- A network path per connection, not one setting for the whole browser.
- Device web interfaces on the same record as the shell for that device.
- The active route and its exit address visible while the session runs.
- An inventory of internal hosts instead of a bookmark folder of addresses.
Side by side
Firefox and Vandle
| Aspect | Firefox | Vandle |
|---|---|---|
| Isolation | Per-container cookies and storage | Per-connection network route |
| Proxy scope | Browser-wide | Per connection, switchable at runtime |
| Internal hosts | Bookmarks | Records with host, port, route and credentials |
| Beside the page | Another tab | A terminal and a file surface 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