Moving over
What it takes
Your bookmarks translate directly: host, user, path and a route, kept once per machine.
You already connect to more than one kind of storage
Cyberduck understood early that the far side is not always a server. Vandle takes the opposite starting point and meets it in the middle: the connection is the object, and a file surface is one of the things it can open.
Credit where it is due
Cyberduck is open source, covers a remarkable spread of backends, and its bookmark model made remote storage feel like a place rather than a protocol.
What changes
Four things you get that you did not have.
- A terminal on the same record as the file surface, so a permission problem is fixed where you found it.
- A route per bookmark instead of a proxy that belongs to the whole machine.
- A default download target per connection, and multi-select transfers straight into it.
- Inline editing that writes back over the same session, with no download-edit-upload round trip.
Side by side
Cyberduck and Vandle
| Aspect | Cyberduck | Vandle |
|---|---|---|
| Focus | Storage backends | Connections, with files as one surface among six |
| Shell access | Not covered | A terminal on the same connection |
| Routing | System or per-bookmark proxy | A route object per connection or per folder |
| Look | Native per platform | One deliberate dark theme on all three |
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