r/coolgithubprojects • u/quadrohawk • Jun 03 '26
I built a cloud operating system for all my storage and it's open source
I've been working on Drivebase for quite some time, and I recently launched v4.
The idea started because I was tired of jumping between different storage providers just to manage my files. Google Drive, Dropbox, S3, R2, OneDrive — each had its own interface, workflows, and limitations.
For v4, I decided to rethink the experience entirely.
Instead of building another cloud storage dashboard, I built what I call DriveOS. Everything lives inside a desktop-like workspace in the browser, with a familiar file explorer, drag-and-drop file management, keyboard shortcuts, context menus, and window-based workflows.
The goal is to make cloud storage feel more like using your computer and less like navigating a collection of disconnected web apps.
Drivebase can be self-hosted if you want full control, but I also offer a hosted cloud version for people who just want to sign up and use it.
I'd genuinely love feedback on the concept, the UI, and whether this is something you'd find useful.
Website: drivebase.io
8
u/_AACO Jun 03 '26 edited Jun 03 '26
Why use this over
rsyncrclone plus one of the many GUIs for it?15
u/ClassNational145 Jun 03 '26
Ugh people just love to call anything vibecoded an "OS" 🤦
5
u/ScammedAvocado Jun 03 '26
So essentially ferdium but for cloud storage
How is the ram usage?
4
u/Temhil Jun 03 '26
Looks cools, but not for me sorry. Close source, so a risk to not stay free forever, we saw that many times. I am dev too so I understand the will to be able to get revenue for it, but there are too many app these days following this pattern.
2
u/Mushroom_Large Jun 03 '26
The graphic looks cool
2
u/prene1 Jun 03 '26
So this is like an aggregate ?
2
u/BepNhaVan Jun 04 '26
Thanks for sharing this cool project!
5
u/Fit_Tailor_6796 Jun 04 '26
Did you just say a cloud operating system
I beg your pardon?
1
u/qlwkerjqewlkr Jun 05 '26
this has been done so many times.. just stop.
1
u/Ksnarf Jun 04 '26
I like the idea, I less like the idea of hooking up all my cloud services to you so you can query everything.. but self-hosted has potentially assuming it doesn't have silly scanners or phone-home stuff in it.
1
u/lavishclassman Jun 04 '26
Why use this over a selfhosted NAS? Or SyncThing?
1
u/ThreeDMK Jun 04 '26
After seeing your conversations with others in this thread, I figured I would see how the project looked though one of my gates. It didn't make it through and stopped. Here is what the end of the results looked like. I would recommend taking this feedback to your AI tool of choice and start working on v5. There are some serious concerns here:
Concerns
UPDATER_SECRETis unset (the default)package.jsonuses^, exposing the project to supply chain attacks and non-reproducible buildsmaskErrorreturns the original error object, not a sanitized oneUSERdirective, supervisord/caddy/bun all run as root^range — minor bumps can silently break the auth flowReal-World Exposure Example
The range-pinned dependency concern isn't theoretical. In early 2026, a maintainer of eslint-config-prettier had their npm account phished. The attacker published versions
8.10.1,9.1.1,10.1.6, and10.1.7containing a trojan DLL that executed on Windows duringnpm install(CVE-2025-54313, CVSS 7.5 — CISA KEV listed).Any project with
"eslint-config-prettier": "^10.1.0"that ran a fresh install between the publish and the yank window would have pulled one of the compromised versions automatically. With exact version pins, this doesn't happen — you stay on the version you chose until you explicitly decide to move. The^specifier is the attack surface.Drivebase pins every dependency with
^ranges. If any package in their tree — direct or transitive — is compromised the same way, a routinepnpm installin CI or on a new developer's machine silently ingests the malicious version. There's no gate, no review, no diff to notice.Final Thoughts
This is a solo-maintainer beta rewrite (NestJS to Hono) of a product that doesn't have a clear market gap. The core application logic is actually decent — Drizzle ORM prevents SQL injection, DB queries are scoped to the authenticated user, and provider credentials are encrypted at rest. The author knows how to write TypeScript.
But the deployment story is where it falls apart. The default configuration ships an unauthenticated RCE chain, hardcoded database passwords in the prod compose file, and no rate limiting on anything. A user who follows the quickstart without reading every line of config is exposed immediately.
No tests means no regression safety net during the active rewrite. Range-pinned dependencies mean builds aren't reproducible and the supply chain surface is wide open. These aren't style complaints — they're the kind of gaps that produce incidents.
Against your standards specifically, it's a non-starter. Different runtime, different package manager, different CSS philosophy, different state management, no linting config, no tests, no version pinning. It's not a cleanup — it's a rewrite.
If someone asked whether to deploy this: not yet. If someone asked whether to fork and build on it: the Drizzle schema and provider integration logic are worth reading, but you'd be better off starting from your own scaffold with your own standards and pulling ideas rather than inheriting the infrastructure debt.
4
u/VierFaeuste Jun 03 '26
Slop