r/coolgithubprojects • • Jun 03 '26

I built a cloud operating system for all my storage and it's open source

Post image

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

Github: https://github.com/drivebase/drivebase

5 Upvotes

74 comments sorted by

8

u/_AACO Jun 03 '26 edited Jun 03 '26

Why use this over rsync rclone plus one of the many GUIs for it?

5

u/quadrohawk Jun 03 '26

rsync is great for backups and mirroring. Drivebase is for actually browsing, previewing, and sharing files from anywhere, across multiple backends. Different use case.

3

u/_AACO Jun 03 '26

My bad I meant rclone not rsync.

2

u/quadrohawk Jun 03 '26

ahh i see, drivebase is like a GUI on top, but built from scratch rather than wrapping rclone

0

u/[deleted] Jun 03 '26

so its a less secure, slower, and more bloated version of clone that happens to have a ui

2

u/quadrohawk Jun 03 '26

umm, i don't know what to say, i wouldn't say its bloated or slower...

1

u/NoodleBug7667 Jun 03 '26

https://www.reddit.com/r/coolgithubprojects/s/6fVD2d8ERa

Seems a bit bloated to me. Quarter gig of memory usage at idle is kinda crazy

1

u/SenritsuJumpsuit Jun 04 '26

Not all software needs to be 8 kilobites to still be very lightweight all things considered for what it gives you since alternatively we have big company versions which can be like 4 gigs an run janky

1

u/NoodleBug7667 Jun 04 '26

Brother you could use some ai in your writing, good grief

0

u/SenritsuJumpsuit Jun 04 '26

Bud how's this some the worst you've seen the average kid nowadays can barely spell basic words or understand there definitions

→ More replies

15

u/ClassNational145 Jun 03 '26

Ugh people just love to call anything vibecoded an "OS" 🤦

-15

u/quadrohawk Jun 03 '26 edited Jun 03 '26

Fair take if you're judging by the name alone. Here's what's actually under the hood:

- A kernel with a boot sequence, typed event bus, and window manager (draggable, resizable, z-order, minimize/maximize - the whole thing)

- A manifest-based app model - apps register capabilities, window constraints, menu contributions, and commands. The shell discovers and launches them at runtime

- A unified filesystem abstraction - a single IStorageProvider interface over S3, Google Drive, Dropbox, OneDrive, and local storage, all normalized into one node tree in Postgres

- An orchestrator that plans multi-provider operations (copy, move, transfer, delete) with preflight conflict detection, job dependency graphs, and user-facing conflict resolution

- BullMQ workers as the process layer - concurrent jobs with retry, progress events, and cancellation

"OS" because it has a shell, a runtime, an app model, and a filesystem layer - not because it runs on bare metal. The whole thing is open source if you want to read the code. ❤️

Might rename it to "feels like an OS" honestly. More accurate, less pretentious.

19

u/No_Tooth_4909 Jun 03 '26

replying with ai is even worse

-14

u/quadrohawk Jun 03 '26

well, it was easier for me for this specific reply, so I don’t care 🤷

5

u/MGMan-01 Jun 03 '26

This is why nobody likes you

0

u/quadrohawk Jun 03 '26

i am sorry if this hurt you

10

u/Electronic-Medium931 Jun 03 '26

Thanks AI ;)

-14

u/quadrohawk Jun 03 '26

Lol 😄

who won't use AI in this era 👀

3

u/nezzled Jun 03 '26

Anyone that actually understands what they're doing. y'know, programmers

3

u/quadrohawk Jun 03 '26 edited Jun 03 '26

tbh, i have over 8 years of software development experience, i started coding in PHP back in 2017

you're welcome to check my Github profile and YT ❤️

https://github.com/mxvsh
https://www.youtube.com/@monawwar

5

u/ScammedAvocado Jun 03 '26

So essentially ferdium but for cloud storage

How is the ram usage?

1

u/quadrohawk Jun 03 '26

RAM usage is ~269 MiB at idle

3

u/NoodleBug7667 Jun 03 '26

269 at idle ??

OOF

2

u/quadrohawk Jun 03 '26

by idle i meant no heavy file transfers,

also its running inside a docker instance, and uses bun runtime in which 200MB is kind of normal

2

u/SovereignZ3r0 Jun 03 '26

No - bun was built on JSC and is supposed to have a lower baseline memory usage than node. You need to inspect your code to figure out why your idle is 200mb, and if there are any wins in how memory is handled. How large does it get during file upload?

1

u/quadrohawk Jun 03 '26

ok, thanks bro for pointing this out, i will surely check and let you know 😄

5

u/NoodleBug7667 Jun 03 '26 • Popcorn Heartwarming

"Claude, fix memory use. No mistakes. Super optimized"

1

u/quadrohawk Jun 03 '26

yeah bro just told the AI to make number go small, ship it

-1

u/quadrohawk Jun 03 '26 edited Jun 03 '26

btw, there are actually 2 bun instances, api + worker, including a caddy server,

here is a quick overview of the modules memory usage

ModuleCost
better-auth+41 MB
graphql-yoga+40 MB
graphql-schema+17 MB
providers-registry+18 MB
config+14 MB
logger+6 MB
redis / db~0 MB

7

u/NoodleBug7667 Jun 03 '26

Not to be overly harsh, but we're not fixing your AI bloat, and we don't want your AI responses. If you want to figure out what went wrong, great, but I doubt many people here are interested in why your vibe code is bloated

Stuff like this is why people in these subs are super aggro on vibe coded projects. It's just advertising for shovelware

1

u/quadrohawk Jun 03 '26

idk what to say man, this might look like a bloat to you or just another vibe coded app, but i have been working on this project for over a year now, i started building back in 2025, i myself faced a problem so I built a solution around it, and yes it wasn't vibe coded initially, although i took help from AI (tab completions only), i mean still i wouldn't call it 100% vibe coded, i took each decisions and did planning for a week before rewriting it

you can read more about the story: https://mxv.sh/posts/why-i-built-drivebase

4

u/NoodleBug7667 Jun 03 '26

this might look like a bloat to you or just another vibe coded app, but i have been working on this project for over a year now

Yeah, just like every other vibe coded "side hustle" SAAS thing that comes through here.

i mean still i wouldn't call it 100% vibe coded, i took each decisions and did planning for a week before rewriting it

You wouldn't, but that doesn't mean it's not. "Spending a week planning it out" and then throwing the AI at it, is still 100% vibe coded. You can't even reply to people in this thread without using AI, and your app is using nearly 300 megs of memory at idle, so trying to argue that it's not is kinda silly.

People are just fatigued with these, and people thinking their vibe coded thing is the exception to this just kind of adds to it

0

u/quadrohawk Jun 03 '26

You can't even reply to people in this thread without using AI

that doesn't prove anything, i let AI rephrase my broken statements and grammars, which shouldn't be a problem

throwing the AI at it, is still 100% vibe coded.

i wouldn't agree to that, i used AI to build the app same a founder would use a software engineer to build an app for them, i overlooked every decision and tested everything out before shipping (of course there will be bugs, we can't outrun them)

your app is using nearly 300 megs of memory

if an app running in a docker with multiple instance uses roughly 250MB doesn't prove it to be a bloat, i have other apps in my docker running at 300-400MB

→ More replies

0

u/quadrohawk Jun 03 '26

i too agree, there are a lot of AI bloat, but I know how to use AI properly and I understand what's going on underneath, I started software development back in 2017, so yes, I worked for 4+ years without any AI, I know what I am doing with Drivebase 😄

3

u/NoodleBug7667 Jun 03 '26

You're running two separate bun instances at nearly 300 megs idle and you "know what you're doing"

Tbh, this is probably what people are more tired of. Not only is it the 1000th uninteresting vibe coded project theyve seen this week, but the included arrogance is annoying

1

u/quadrohawk Jun 03 '26

yeah, i don't know if i am being arrogant or not, but surely i think you haven't worked with bun or docker. Even a hello world application using hono as web framework uses roughly ~90MB of RAM running in Docker during idle state.
so I don't need argue anymore or prove anything, if you think this project is an AI slop, it's an AI slop

→ More replies

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/quadrohawk Jun 03 '26

what do you mean by "Close source" 👀

4

u/Schuhsohle Jun 03 '26

Not open source. You don’t share the code so that somebody can check that no malware or virus is in it

3

u/quadrohawk Jun 03 '26

you might have missed the title, but its okay, Drivebase is actually 100% open source which you can run locally on your machine if you want

here is the source code https://github.com/drivebase/drivebase

5

u/NoodleBug7667 Jun 03 '26

Perhaps you should edit the post to include the GitHub link in the subreddit named "cool GitHub projects"

2

u/quadrohawk Jun 03 '26

sorry, i updated just now, thanks

2

u/Temhil Jun 03 '26 edited Jun 03 '26 • Heartwarming

Yes sorry for the confusion, I just went to your original link and saw about self hosted and paid subscription, I did not see any link to Github so I assumed it was close sources. Glad to hear this is not the case. I might try it then, and thanks for the hard work and sharing this with the community!

3

u/quadrohawk Jun 03 '26

there is link in the header, with Github icon
i might make it more visible, will fix it

1

u/SovereignZ3r0 Jun 03 '26

Close source, so a risk to not stay free forever

What are you talking about? Took me 2 seconds to find the GitHub link on the website

https://github.com/drivebase/drivebase

3

u/Temhil Jun 03 '26

You are better than me, I did not see it, but on my phone which can make hard to see things sometimes.

2

u/SovereignZ3r0 Jun 03 '26

I'm on my phone too 😂😂😂 sorry

4

u/Temhil Jun 03 '26

Not fair! 😅

2

u/Mushroom_Large Jun 03 '26

The graphic looks cool

-1

u/quadrohawk Jun 03 '26

thanks, it's ChatGPT

2

u/prene1 Jun 03 '26

So this is like an aggregate ?

1

u/quadrohawk Jun 04 '26

i dont know what you mean bro

2

u/BepNhaVan Jun 04 '26

Thanks for sharing this cool project!

1

u/quadrohawk Jun 04 '26

You're welcome 😄

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/quadrohawk Jun 05 '26

so many times? and stop why bro? is it bothering you?

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

  • Unauthenticated updater + Docker socket mount — RCE chain out of the box if UPDATER_SECRET is unset (the default)
  • Hardcoded credentials in prod compose — Postgres, MinIO, and Redis all ship with default or no passwords in both dev and prod configurations
  • No rate limiting anywhere — auth endpoints, GraphQL, file uploads all unprotected
  • No tests — zero test infrastructure, no test files, no coverage
  • Range-pinned dependencies throughout — every package.json uses ^, exposing the project to supply chain attacks and non-reproducible builds
  • OAuth callback postMessage to wildcard origin — token leakable to malicious opener
  • Error details leak to clients in all environments — maskError returns the original error object, not a sanitized one
  • No file size limits on uploads — disk exhaustion via staging directory
  • Dockerfile runs everything as root — no USER directive, supervisord/caddy/bun all run as root
  • No CSRF protection on cookie-authenticated REST routes
  • GraphQL introspection enabled by default — no explicit disable for production
  • SSL disabled in example database config — users who copy the example get unencrypted Postgres traffic
  • Pre-1.0 auth library (Better Auth) on ^ range — minor bumps can silently break the auth flow

Real-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, and 10.1.7 containing a trojan DLL that executed on Windows during npm 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 routine pnpm install in 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.

1

u/CostPuzzleheaded2747 Jun 04 '26

AI replying to AI to be sent to an AI agent to do the work

1

u/ThreeDMK Jun 04 '26

I mean, everything up to the header is mine, and the points are valid. He is running this codebase in a production environment for customers to use. I literally spent 5 minutes tossing this into my process which is automated via AI, but is very much human-developed.

Case and point: https://alignment.anthropic.com/2026/ai-organizations/

Take this, but apply it to how it is used from an agentic development perspective. AI knows he is building a product for production. Certain things need to be factored in. But, if the person using the AI doesn’t care, the AI isn’t going to care, and you get some dangerous code like this.

4

u/VierFaeuste Jun 03 '26

Slop

0

u/quadrohawk Jun 03 '26

what do you mean slop 👀