Moving over
What it takes
Nothing replaces anything: rclone keeps the schedules, Vandle holds the connections you open with your hands.
You already scripted the transfer once and never touched it again
rclone is the right answer for anything a cron job should do. Vandle is the right answer for the other half: the interactive session where you are looking for something and do not yet know its name.
Credit where it is due
rclone speaks more backends than any GUI will ever ship, its sync semantics are careful, and a well-written remote in rclone.conf is genuinely durable infrastructure.
What changes
Four things you get that you did not have.
- A browsable surface for the sessions where you are exploring rather than executing.
- A terminal on the same connection, so you can check the far side without switching tools.
- A visible inventory grouped in folders, with one row per protocol per machine.
- A route per connection, assigned once and applied every time.
Side by side
rclone and Vandle
| Aspect | rclone | Vandle |
|---|---|---|
| Strength | Unattended sync and mounting | Interactive sessions on six protocols |
| Inventory | rclone.conf | A visible list, grouped and colour-coded |
| Shell | Not covered | A terminal on the same connection |
| Scripting | Excellent | Unchanged. Keep rclone for the cron job. |
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