Your Cloud Files, Where You Already Look For Them

Here is a small ritual that quietly eats an afternoon. You need to change one file that lives in cloud storage. You open a browser tab, sign in, find the file, download it, dig it out of your Downloads folder, open it in the app that made it, save, switch back to the tab, click upload, find the file on disk a second time, and confirm that yes, you meant to replace the old one.

That is nine steps to change one file. Do it forty times over the life of a project, with two people, and you start to understand why so much real work never makes it into the shared folder at all. A cloud drive that shows up in Finder is not a prettier interface for that ritual. It deletes the ritual.

The loop is the problem, not the interface

Browser-based storage is fine for the things browsers are good at: sending someone a link, checking that a file arrived, seeing how much space is left. It breaks down the moment the file is something you need to work on rather than something you need to move. Every download-edit-reupload cycle introduces the same three failures, and none of them are failures of attention.

• Two copies exist: one in the cloud, one in your Downloads folder. The second you close the laptop before finishing the upload, they disagree, and nothing anywhere tells you which one is current.
• The file loses its place: it came out of a folder structure someone designed on purpose and landed in a flat pile next to a tax form and an installer. Putting it back in the right folder is a separate act of memory.
• The app cannot save where the file lives: design tools, spreadsheets, editing software, and compilers all assume Save writes to a path on disk. A web upload form is not a path. So every save becomes an export, and every export becomes a decision about what to name the thing.

That last one is why proposal-final-v2-REAL.pdf exists in every company on earth. The naming chaos is not sloppiness. It is what happens when the tool cannot overwrite in place, so people version by filename instead.

What changes when the drive is just a drive

Mount cloud storage as a drive in Finder and the file has a path again. Command-O in any app reaches it. Save writes back to it. Drag a folder onto it and the folder goes up. Nothing about your habits has to change, which is the entire point, because the habits are not the problem.

The practical effect shows up in the boring places. Your app's recent-files list starts working again, since the path stays stable between sessions. Quick Look previews the file without downloading it first. Spotlight finds it by name. A build script or an export preset that points at a folder keeps pointing at the same folder whether you are at the studio desk or on a borrowed Mac. None of that is impressive on its own. Together it is the difference between storage you use and storage you visit.

This is the shape we built Orbit around. You connect your own cloud storage, S3-compatible services like Amazon S3, Cloudflare R2, DigitalOcean Spaces, Backblaze B2, and Wasabi among them, and it opens as a drive on your Mac. The files are in your storage account, not ours. Orbit is the part that puts them where your hands already go.

Handoffs stop being a packaging exercise

The clearest gain for a small team is not personal convenience. It is what happens at the seam between two people.

Consider a hypothetical two-person shop finishing a client project. Under the browser model, handing off means packaging: zip the folder, upload it, send a link, and then answer three questions about which subfolder the final exports are in. The person receiving it unzips into their own Downloads folder, which means the project now lives in two unrelated places with two separate futures. Any change made on either side is invisible to the other.

Connect both Macs to the same storage location and the handoff is just a sentence. The folder is where it has always been. Nobody packages anything. The structure the first person built is the structure the second person opens, which means the folder layout itself becomes a form of communication that survives the transfer.

Be clear about what this is and is not. Connecting two Macs to one bucket gives you a shared set of files, not a collaboration product. Orbit does not create team accounts or manage invitations, and it does not do live co-editing, file locking across machines, or merging two people's edits into one document. Access is something you grant with your storage provider, one authorized set of credentials per person. If two people open the same file at the same time, you are relying on the same thing you relied on before: a conversation about who has it.

What you give up

A drive that lives in the cloud still has to reach the cloud. Opening a file means pulling it across your connection, and that cost is real in ways a local disk never is.

• Large files feel large. A scratch folder for a video edit or a working library of raw photos is a workload that wants fast, consistent local disk access. A network mount is the wrong home for it.
• A bad connection is a bad drive. Hotel Wi-Fi does not degrade your storage gracefully. It degrades your entire workflow, because now the drive you are saving to is the slow part.
• Transfer and storage cost money. You are paying your provider for capacity and, depending on the provider, for data moving in and out. A habit of opening a 2 GB file to check one thing has a bill attached.

The answer to the connection problem is choosing what travels with you. In Orbit, you pick specific folders to keep offline, they download to a folder on your Mac, and you work from those local copies with no connection at all. Only what you select is stored locally, and those copies use your own disk space. The regular cloud drive still needs internet. That tradeoff is not a limitation to route around; it is the actual decision, and it is worth making deliberately per folder rather than hoping.

The takeaway

The test for any storage tool is not how good the interface looks. It is how many steps sit between you and a saved change. A browser tab puts nine there. A drive in Finder puts one, and one is the number where people stop keeping private copies on the desktop "just for now."

Orbit is currently a Mac preview we distribute directly, and it expects you to bring your own storage account and have rclone installed, so it is not a one-click product yet. If your team is passing zipped folders around and losing track of which version is real, that is the problem worth fixing first, with or without us. Tell us what your handoffs look like and we will tell you honestly whether this is the right shape of fix.