{ } DatJavaClass.com.com
Data Science Grad Student → Product Manager → Software Developer → Forever GM
Victor Sverdlin
Victor Sverdlin

“Cry Woe! And unleash the Agents of Claude!”

package www.blog;

@Personal public class LassoingTheCloudCloudRouter extends Blog

Lassoing the Cloud: Cloud Router

Hermes from Futurama dancing as he files away every item in the central bureaucracy

Every cloud service wants to own your files. Dropbox wants you in the Dropbox folder. OneDrive wants its mirror. Google Drive mounts a whole drive letter like it pays rent. Run two or three at once and “put this file over there” turns into a chore. You drag across windows that refuse to both stay visible. You dig through a Save As dialog three levels deep. You copy a path, paste it, fix the slash you fat-fingered.

The file was ready to move thirty seconds ago. The friction was never in the file. It was in the plumbing.

That landfill on your desktop? Same disease.

Zoidberg at Area 51 calling the food disorganized files, then devouring it

Cloud Router meets the file where it already lives. The right-click menu, under your hand. Right-click any file or folder, open the Cloud Router submenu, pick a destination. Moved. Or copied. No drag, no dialog, no path-typing. The submenu fans out into your clouds and network folders. Dropbox, OneDrive, Google Drive, Box, Mega, Proton, iCloud, plus any mapped or WebDAV drive. Each shows up with its real icon, so the menu reads at a glance.

Install is one file. Double-click CloudRouterSetup.exe and a setup window opens already listing every cloud folder it found. Tick the ones you want. Add a network share it couldn’t guess. Pick Move or Copy as your default. Click Install. That’s it. No runtime, no account, no admin rights.

Daily use is trivial. Route a file and a brief notification tells you where it went. Click the notification and Explorer opens with the file selected, so you can confirm it landed. Select a whole stack at once and each one routes in turn. On Windows 11 the entry lives under Show more options (or Shift+F10 if you’re impatient), because Cloud Router deliberately uses the classic context menu. That’s the trade that keeps the install dead simple.

That’s Part 1. Filing made into a reflex. Part 2 is for the people who want to know why it costs nothing.


Here’s the part I’m proud of. Cloud Router is one self-contained executable. C# on .NET 9. No background service. No tray agent. No watcher. When you aren’t routing a file, nothing of Cloud Router is running at all. The menu is pure Windows registry data living in your user hive (HKCU), the app sits in %LOCALAPPDATA%\CloudRouter, and the cost of having it installed is effectively zero. Pick a destination and Windows just runs CloudRouter.exe move <destination> "<file>". Uninstall and the menu and the copy leave clean. A tool that costs you nothing while idle is a tool you never resent.

The detection is the clever bit. Rather than ask where your clouds live, it probes each one the way that app records itself. OneDrive from its account keys, Dropbox from its info.json, Google Drive from its mount-point value (and if that’s missing, the drive literally labeled “Google Drive”). Box, Proton, Mega, iCloud from their own footprints. Every probe is sandboxed from the others, so one missing provider can never blow up the rest of setup. And if detection misses something? The Add folder button takes a browsed path or a pasted UNC share like \\nas\backups. Detection is a convenience. The manual button is the guarantee.

A few touches for the people who’ll notice. Each destination can enforce a subfolder, so you point at a junk-drawer root like S:\ and everything quietly lands in S:\Inbox. Name clashes get the Explorer treatment, report.pdf becomes report (2).pdf, nothing silently overwritten. Keep one destination set to Copy as an archive target and you fan a file out without losing the original. Moves across different volumes fall back to copy-then-delete on their own, so C: to a WebDAV NAS just works.

Which matters more than it sounds.

Bender taking damage while Leela berates him for only having one cloud storage provider

Config is plain text in destinations.json, hand-editable, environment variables and all. No telemetry. When something breaks, errors go to a local log, and the Report a problem button opens a pre-filled GitHub issue for you to review before you send it. Nothing leaves your machine unless you choose to send it.

So who’s this for? Students juggling a school drive and a personal one. Professionals routing a deliverable to a NAS or a client folder without window-juggling, and without begging IT for admin rights. Creatives shoving a fat render out to the cloud before their working drive fills up. Honestly, anyone whose downloads folder has become an archaeological dig.

The real win isn’t speed. It’s that the gap between “I should file this somewhere sensible” and actually doing it shrinks to one right-click. Deferral is what turns a desktop into a landfill, and deferral compounds. Collapse the cost and the deferral stops. File as you go, because filing is finally cheaper than not filing.

And it asks for none of your attention. No window, no icon, no badge, no process. It waits inside a menu you already open for other reasons. Out of sight, out of mind, out of the way.

Grab it here: https://github.com/DatJavaClass/CloudRouter

Bender in a crowd captioned Neat
// pick one: