Moving over
What it takes
Keep Opera for browsing; hand Vandle the connections where the route matters more than the page.
A built-in tunnel for the browser. Now do it per connection.
Opera put routing in the product instead of an add-on, which was ahead of its time. Vandle takes the same position and applies it per connection, across every protocol rather than only the page.
Credit where it is due
Opera shipped a usable built-in tunnel long before it was fashionable, and its workspaces and sidebar apps keep a lot of daily tools one click away.
What changes
Four things you get that you did not have.
- A route per connection rather than one switch for the whole browser.
- The same routing on a shell, a transfer and a desktop, not only on web pages.
- The active path and exit address visible on the running session.
- An inventory of internal machines with credentials stored encrypted.
Side by side
Opera and Vandle
| Aspect | Opera | Vandle |
|---|---|---|
| Routing | Browser-wide, on or off | Per connection, any configured route |
| Scope | Web pages | Every protocol Vandle speaks |
| Visibility | An indicator in the address bar | Route, latency and exit on the session |
| Internal hosts | Bookmarks and speed dial | Connection records in folders |
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