One Evening, One File, Fifteen Wasted Minutes
It was a perfectly ordinary evening until it was not. There was a file — an important one — somewhere in my cloud storage. I was certain of it. I had saved it myself. So I opened my first Google Drive account and started looking. Nothing. I opened the second account. Still nothing. Then a third. Then a fourth. Folder after folder, scroll after scroll, the file stayed hidden as though it never existed.
15 minutes passed. Frustration had long replaced patience. I gave up.
The next morning, out of curiosity more than anything else, I asked a friend if he had ever experienced the same thing. He did not even hesitate. “Yes,” he said immediately, as if the memory was fresh. That single word sparked a much larger question: was this just the two of us, or was this a problem far more people silently lived with every day?
Asking the Question Out Loud
To find out, I put together a quick survey and shared it across WhatsApp groups. 65 people responded. The results that came back were more striking than I had anticipated. What I had dismissed as a personal inconvenience turned out to be a frustration that a significant portion of people quietly shared.
Use more than one cloud storage account regularly
Spend at least 10 minutes searching for a single file
Feel frustrated by forgetting a file's name or location
The numbers told a clear story. Searching through multiple cloud accounts was not a niche annoyance. It was a real, recurring problem that affected the majority of people who used cloud storage at all. That was enough to begin taking it seriously.
The Problem, Clearly Stated
People today spread their files across multiple services — Google Drive, Dropbox, OneDrive — often without a unified system. Over time, file names become vague memories, folder structures grow inconsistent, and what was once neatly organised quietly becomes a scattered archive spread across platforms that do not speak to each other.
The result is not just wasted time. It is the slow erosion of trust in one’s own storage system. People stop relying on it, start duplicating files as a safeguard, and build makeshift workarounds that solve nothing permanently.
What Already Existed
Before building anything, I studied what was already out there. Several tools had attempted to tackle parts of this problem, though none addressed it in full.
- MultCloud — Moves and syncs files across clouds, but offers only a basic search function with no depth of content understanding.
- odrive — Combines all connected clouds into one local folder on your machine, but is not searchable by content.
- CloudFuze — Designed for businesses managing large collections of cloud files, far too complex for individual users.
- Otixo — Lets teams collaborate on files from different clouds in one shared space, not a personal search tool.
- ExpanDrive — Mounts cloud storage as local drives at the system level, technical, narrow, and not built for discovery.
Each tool solved a slice of the problem. None of them made it genuinely simple for an everyday person to connect all their cloud accounts and find any file by just describing what they were looking for.
Why This Is Harder Than It Looks
Understanding the gap was one thing. Understanding why the gap existed was another. Building a unified cloud search tool came with challenges that were not immediately obvious.
- Connecting Different Clouds — Every cloud service operates on its own API structure and authentication logic, making them difficult to combine into one coherent system.
- Keeping Data Safe — Users would be granting access to their most private files, making security not just a feature but a foundation.
- Smart Searching — Building an AI that understands file content, not just file names, requires serious technical infrastructure.
- Keeping Costs Low — The people who need this most are individuals, not enterprises. Affordability had to be a design constraint, not an afterthought.
- Avoiding Subscription Fatigue — People already pay for multiple cloud services. Adding yet another subscription needed very clear justification.
- Earning Trust — Asking someone to hand over access to all their files requires transparency and reliability that takes time to build.
Setting the Goals
With the challenges clearly mapped, the goals became equally clear. Every decision made in building this product would be measured against five commitments.
- Make connecting all cloud accounts a seamless, frictionless experience from the very first minute.
- Keep every user’s data private and secure without exception.
- Enable intelligent search — finding files by meaning, not just by name.
- Keep the product genuinely affordable for individuals, not priced for enterprises.
- Build trust by being transparent, reliable, and honest in every part of the experience.
Introducing ScoutFiles
With those goals as the foundation, I built ScoutFiles — a unified platform that connects all your cloud accounts in one place, allowing you to search for any file using simple, natural keywords.
Everything worked. The connections were live. The search was functioning. The experience was clean. It was ready to ship.
When Reality Arrives Uninvited
And then, just as I was preparing to move the product into production, the wall appeared — quietly, bureaucratically, and entirely unmoveable.
Google Drive is the most widely used cloud storage platform in the world. It is, in many ways, the centrepiece of what ScoutFiles was built to solve. But Google’s Drive API operates under a restricted scope. To use it in a live, public-facing product — to let real users connect their accounts — requires passing a Cloud Application Security Assessment, more commonly known as CASA certification.
CASA certification costs approximately $500 to obtain and must be renewed every single year. Without it, the Google Drive API can only operate in test mode, capped at a maximum of 100 users total across the entire application.
One hundred users. For a product built to reach thousands of people who search through their files every day and come up empty, that ceiling felt less like a limitation and more like a locked door.
The Answer to Why It Was Never Built
I had spent weeks wondering why no one had built a simple, clean, personal cloud file search tool. The problem was obvious. The demand was clearly there. The technology existed. And yet, the space was empty of exactly what people needed.
The CASA requirement answered that question definitively. It is not that no one thought of it. It is not that no one tried. It is that the moment any builder, developer or startup got close to shipping this product with Google Drive support, they ran into the same wall.
Five hundred dollars a year — before a single user has paid, before a single dollar of revenue has been earned — is a significant barrier for an indie builder or early-stage product. And without Google Drive, you are not building a unified cloud search tool. You are building an incomplete one.
This is the part of product building that rarely makes it into the case studies — the moment when you discover that the obstacle is not a design problem, not a technical problem, and not a market problem. It is a structural one, sitting quietly between a great idea and the people it was meant to serve.
A Story Left Open
ScoutFiles was not abandoned. The problem it was built to solve has not disappeared. The people searching through multiple cloud accounts every week and who spend ten minutes looking for a single file still exist.
Some walls are worth going around. Some are worth paying to pass through. And some are worth documenting carefully — so that the next builder who arrives here knows exactly where they stand.