Assign
Per connection, or per folder
Give one machine a route and its neighbour a different one. Or hang the route on the folder and let a whole site inherit it - set once, applied every time you open any of its protocols.
Proxy-native connectivity hub
Not a browser.
A connectivity hub.
Every protocol you connect with, in one window: SSH, SFTP, WebDAV, RDP, real web browsing and a shell on your own machine. And a proxy on every single connection - assigned per machine, inherited per folder, switchable while the session runs.
- Web
- SSH
- SFTP
- WebDAV
- RDP
- Local
The part nobody else does
A proxy on every connection. Not on your machine.
Every other client treats the network path as an environment: one setting, one machine, everything inherits it. In Vandle the route belongs to the connection. Two sessions side by side can leave through two different exits, and you can move a running session onto a different path without reconnecting.
Switch
While the session runs
The route is a property you can change, not a tunnel you have to start first. Nothing to launch on the side, nothing to remember, nothing left running after you are done.
See
Where you are coming from
The active path, the latency, the throughput and the exit address sit on the session itself - so "which way did that go out" is something you read, not something you infer from a log.
B2B service
ProxyPass · proxy infrastructure, managed
Proxy infrastructure for companies - wired into the interface, not into a config file.
Any proxy you already run works in Vandle. ProxyPass is our business service for the organisations that would rather not run that part at all: tunnelled routes that need no open inbound port on the far side and reach a machine from wherever your people happen to be.
And Vandle supports it first class. Sign in once and your routes appear in the connection editor as a list. Pick one, and the connection is routed. There is no proxy string to paste, no tunnel to start beside the client, no environment variable to set, no credentials in a config file on a colleague's laptop.
proxypass.cloud- Your routes appear as a picklist in the connection editor - nothing typed by hand.
- Assign one to a folder and every machine inside it is routed. One change, a whole site.
- Switch the route of a running session from its header, without reconnecting.
- Credentials live encrypted with the rest of your state, never in a file somebody can copy.
- No inbound port on the target, and nothing exposed to the internet.
- Exit address and latency visible on the session while it runs.
Six protocols, one window
Each one better off here than in the tool it replaces.
Not a list of checkboxes. Every protocol gains something from sitting next to the others on the same connection record - and that is the whole argument.
Web
Real browsing, properly routed
A complete browser inside Vandle. The appliance at 192.168.1.1, the NAS, the IPMI card, the dashboard behind a jump host - they open on the record that also holds that machine's shell.
Each page inherits the route of its connection. No browser gives you a different network path per tab, and no extension does it without sitting in front of your credentials.
SSH
A terminal that keeps up
A full VT terminal with OpenSSH key formats and host-key verification on first connect. Paste ssh user@host anywhere and the session opens.
The same machine's files and desktop are one row away in the sidebar, not in two other applications with two other inventories.
SFTP
Two remote panes, no detour
Dual pane where each side carries its own connection picker. Multi-select, a queue you can watch, a default download folder per connection.
A file moves from server A to server B directly. Every other transfer client routes it through your laptop first.
WebDAV
The other half of file transfer
The same surface as SFTP, so every habit carries over exactly - including the split view and editing a remote file in place.
No drive letter and no cache to reason about: when a write fails you get the protocol error, on the file, not a generic I/O message.
RDP
Desktops on a native surface
Full remote desktops, rendered natively rather than inside a web runtime, on the same connection list as everything else.
Nothing to install on the far side, and the shell for that machine is one click away - so you can pick the faster tool instead of the only one you have open.
Local
Your own machine, in the same list
Your own shell in a folder you pick - PowerShell, a WSL distribution, bash, zsh, whatever you already use. Pinned right next to the servers that folder deploys to.
It is the real shell, not a cut-down one: every alias, every script and every full-screen tool behaves exactly as it does today - and it sits in the same window as the machines that folder is about.
Against the alternatives
What the market ships, and what Vandle ships instead.
| Aspect | Terminal, transfer and desktop tools | Vandle |
|---|---|---|
| Protocol coverage | Terminal tools do shells. Transfer tools do files. RDP clients do desktops. Three inventories of the same machines. | All six on one connection record, one row per protocol in the sidebar. |
| Routing | A proxy setting that belongs to the whole machine, or a gateway that sits in front of exactly one protocol. | A route object per connection or per folder, on every protocol, switchable mid-session. |
| Device web interfaces | A browser tab with no relationship to the machine it administers, and a bookmark folder full of private addresses. | Real browsing inside Vandle, on the record that also opens that machine's shell. |
| Remote to remote transfer | Down to your laptop, then back up again. | Directly between the two hosts, with a connection picker in each pane header. |
| Where your setup lives | A local file - a registry branch, an XML, a config directory - that you copy between machines by hand. | A store you point at, live-synced, with hosts and secrets encrypted before they are written. |
| What it costs to add a protocol | Another tool, another licence, another window. | Nothing. It is already in the client you installed. |
Why it is a category of its own
Three decisions a connection manager does not make.
Proxy-native
A route on every connection
Routing is not a setting you apply to a machine. It is a property of the connection: assign one, inherit it from the folder, switch it while the session runs - and see the active path, the latency and the exit address on the session itself.
One shell
Six protocols, one window
A terminal, a file surface, a browser, a remote desktop and a shell on your own machine are surface types on the same host shell. The base is abstracted once; every protocol clips into it. That is why the list stops growing.
Your state
The environment follows you
Connections, folders, routes and layouts live in a store you point at. Start Vandle on a machine that is not yours, aim it at your state, and your whole environment is there - with secrets encrypted until you unlock them.
In practice
What that looks like when you are actually working.
One record per machine, one row per protocol
A connection definition holds the machine once: host, key, route, default download folder. What you pin is a definition plus a protocol - so a single server appears as its own row for the shell and its own row for files, each in its module colour.
- Folders group machines and hand a shared default route to everything inside them.
- Pinned connections sit at the top of the sidebar, ad-hoc sessions below.
- Drag an ad-hoc session upwards and it becomes a saved definition.
- Paste ssh user@host, an rdp:// address or a URL and the right protocol opens.
File transfer that does not detour through your laptop
The file surface opens two panes, and each pane header is a connection picker. Pick a different host in each and a file moves from one server to the other directly. Text files open on an editor surface and save straight back over the same session.
- A default download folder per connection, for one-click transfers.
- Multi-select, and a queue you can watch.
- Inline editing instead of download, edit, upload.
- The same surface carries SFTP and WebDAV, so nothing has to be relearned.
Your own machine belongs in the same list
A local session is a shell rooted in a folder you choose, and it pins into the sidebar like any other connection. The repository sits next to the staging box it deploys to and the production host it eventually reaches - three rows, one folder, one window.
- Your shell, not ours: PowerShell, a WSL distribution, bash, zsh, sh. Vandle finds what is installed and offers it; you pick.
- Pick the folder once; the session always opens there.
- A real pseudo-terminal, so a build with live output, a full-screen tool like htop and a long agent session all behave the way they do in your terminal.
- Pinned or ad-hoc, exactly like a remote session - and promotable by drag.
Secrets that never leave in the clear
State is split into three sensitivity levels. Names and folders stay readable so the sidebar loads without a prompt. Hosts, users and routes are encrypted. Keys and passwords are encrypted with a nonce per value and decrypted only in memory, behind a master key derived from your passphrase.
- AES-256-GCM at rest; the database only ever sees ciphertext.
- The key is derived locally and never written back.
- Full export and import of definitions and folders, without secrets.
- Zero-knowledge means no password reset - so recovery is a deliberate choice.
Coming from something else
Whatever you use today, it got something right.
So every comparison here starts with that. Pick the tool you are coming from and see exactly what changes - and what does not.
I come from SSH
Terminals, key handling and jump hosts.
I come from SFTP
File transfer, mounts and sync.
I come from RDP
Remote desktops and screen sharing.
I come from a connection manager
One list for every machine you own.
Straight answers
The five questions everybody asks.
Is Vandle a browser?
No. Vandle is a connectivity hub, and browsing is one of the six protocols it speaks - a full, usable browser rather than a viewer, meant for the device interfaces that are really connections: a router, a NAS, an IPMI card, a dashboard behind a jump host. It is one part of the client, not the point of it.
Which protocols does Vandle speak?
SSH on a terminal surface, SFTP and WebDAV on a file surface, RDP and the web on pixel surfaces, and your own shell rooted in a folder you pick. All six sit on the same host shell and the same connection records, so one machine is one entry with one row per protocol - and the local session pins right next to the servers that folder deploys to.
What does proxy-native mean?
That the route is part of the connection record rather than a setting on your machine. One connection can take a route its neighbour does not, a folder can hand its route down to everything inside it, and a running session can be switched to a different path. Any proxy you already have works. ProxyPass is our B2B service for companies that would rather not run that part themselves - and Vandle supports it first class, so assigning a route is picking an entry from a list, not editing a config.
Where is my data stored?
In a store you choose. It can be local to one machine, or a central database every device you own reads from, with live updates when a definition changes. Metadata stays readable so the interface loads instantly; everything sensitive is encrypted before it is written and decrypted only in memory.
Which platforms are supported?
Windows, Linux and macOS, from one codebase, with the same connection list on each. Point a fresh install at your state and your environment is there.
The last client you will set up.
The base is abstracted once. Everything after that clips in - which is the whole reason the list stops growing.
Early access
Be there when it opens.
Leave an address and you get one mail - the one that says the build is ready for you. No newsletter, no sequence, no second list.
Stored on this server and used for exactly that one mail - never passed on, and gone the moment you ask. What this site stores.