This was a fun project to test the full capabilities of Opus 5.5. It took roughly 1.5 weeks and about 1,400 commits, from the initial plan and design to the actual build. It now runs 3 of my production apps with real customers / heavy load, and real traffic.
Why
Self-hosting Supabase the usual way is hard , we all know that. Coolify for instance deploys a full stack of about 13 containers for every project, all sharing one kernel. A few projects and the box is full, and security wise is also not great at all and nothing isolates them from each other. I wanted something closer to how Supabase Cloud itself functions: a control plane that creates, resizes, backs up and restores projects, running on hardware I own.
How I split Supabase’s 13 containers
Supabase’s docker-compose runs 13 containers per project. Most of that is fixed overhead every project pays even when it’s idle. So I split them up:
The requirements
How it works
What’s not done yet (being honest)
Should I open-source it? Would you run this on your own server if I did? What would you need from it first?
A user has built a custom implementation of Supabase Cloud on their own hardware, optimizing container usage and resource allocation. They are considering open-sourcing the project and seek community feedback on its potential use and any additional requirements. The discussion includes technical details of the setup and asks for opinions on the risks and benefits of open-sourcing.
You know, I think it might be risky ... But do it. Go ahead and open-source it. I think it might be something extraordinary if you do ...
How so? I'm only here to get feedback on the build to see how others could use it before the actual release. But I don't understand the risky part, could you elaborate?
I'd be interested in it for dev.