Moving over
What it takes
Bring your proxies, give each saved site the profile and the exit it should have, and add the blocker you trust from the Chrome Web Store.
A private window with Tor is the right idea at the wrong granularity: one route for one window. In Vandle the route belongs to the tab, so two tabs can leave through two different exits, and a saved site can keep its own cookies.
Credit where it is due
Brave blocks by default, ships a Tor window nobody else does, and takes the position that the network path is the user's business. That is the same position Vandle starts from.
What changes
Side by side
| Aspect | Brave | Vandle |
|---|---|---|
| Routing | Per window, Tor or direct | Per tab, any SOCKS5 or HTTP proxy |
| Identity | Profiles and private windows | Optional profile per saved site; private links in memory |
| Visibility | You know which window it is | Route on the tab, exit address on demand |
| Blocking | Built in, excellent | Through extensions from the Chrome Web Store |
Moving over
Bring your proxies, give each saved site the profile and the exit it should have, and add the blocker you trust from the Chrome Web Store.
And the rest of it
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.
Also compared