You wanted a backend. You got an orchestra.
That’s what self-hosting Supabase feels like. You spin up Postgres, GoTrue, PostgREST, Realtime, Storage, Kong, a migration runner, and half a dozen other services — all wired together with Docker Compose configs that look like they were written by someone who definitely doesn’t want you to touch them. Twelve containers. For a side project. For something that started as “I just want auth and a database.”
We’ve confused ‘production-ready’ with ‘operationally exhausting.’ The industry sold us a story that real backends require real infrastructure — and then made infrastructure so heavy that only platforms could carry it.
Enter Instancez. It’s a Supabase drop-in replacement that runs as a single binary, configured by one declarative file. No container orchestra. No twelve services whispering to each other over localhost. One process. One config. Done.
The developer who built it said it plainly: they loved Supabase’s DX, but self-hosting it meant a dozen containers, and for small projects that always felt like more infrastructure than the project deserved.
That sentence should hit harder than it does. Because it’s not just about Instancez — it’s about the entire trajectory of developer tooling over the last five years. We built incredible platforms, then made them impossible to self-host without a Kubernetes certification and a prayer.
Supabase’s real moat isn’t Postgres or GoTrue or Realtime. It’s the muscle memory of a million developers who reach for supabase-js before they’ve even decided what they’re building.
That moat is deeper than people think. It’s not about the database engine. It’s not about row-level security or edge functions. It’s about the API surface — the exact shape of the SDK calls, the auth flow, the realtime subscriptions, the storage buckets. Developers don’t learn “a backend.” They learn the backend. The one their tutorial used. The one their coworker recommended. The one that’s already in their package.json.
Which means building a drop-in replacement isn’t just an engineering challenge. It’s a bet that the ecosystem will accept a smaller, simpler compatibility layer as “good enough” — while the original keeps expanding in every direction.
That’s the tension nobody talks about. A true drop-in replacement implies matching Supabase’s entire API surface. A single binary succeeds only by aggressively reducing scope. Compatibility and simplicity pull in opposite directions, and Instancez is betting that most developers don’t need the full surface — they need the 80% they actually use, delivered in a way they can actually own.
A drop-in replacement that’s simpler than the original isn’t a clone. It’s a correction.
And that correction matters more than the technology itself. Because the gap between managed-service convenience and self-hosted ownership has been widening for years. Platforms get easier. Self-hosting gets harder. The cloud wins by default, not because it’s better, but because the alternative has become genuinely unbearable.
Instancez is a signal that this gap is closing. Not because Supabase is getting simpler — they’re adding features, expanding the surface, deepening the moat. But because someone looked at the whole stack and said: what if we just… didn’t? What if the same developer experience could live in one file, one binary, one process that a single person can understand, deploy, and debug without a distributed systems PhD?
The answer isn’t perfect. It won’t match every API call. It won’t have every feature. And the moment Supabase ships something new, Instancez falls further behind. That’s the cost of being a replacement instead of an original.
But here’s what most people miss: the developers who self-host aren’t looking for feature parity. They’re looking for dignity. The dignity of running their own backend without it becoming a second job. The dignity of a docker run that doesn’t require a 200-line Compose file. The dignity of reading one config file and understanding their entire infrastructure.
The best infrastructure is the kind you forget exists — not because it’s managed by someone else, but because it’s so simple you don’t need to think about it.
Instancez won’t kill Supabase. It’s not trying to. It’s trying to kill the idea that self-hosting has to hurt. And if that idea spreads — if more developers start demanding single-binary alternatives to multi-container stacks — the infrastructure landscape shifts in a direction that favors ownership over convenience, simplicity over completeness.
That’s the real story here. Not a GitHub project. A philosophical bet that the future of self-hosted infrastructure isn’t more services, more containers, more orchestration — but less. One file. One binary. One developer who actually understands what’s running on their machine.
Twelve containers was never the answer. It was just the tax we accepted because nobody showed us the alternative.
FAQ
Q: Can Instancez really be a true drop-in replacement for Supabase if it's a single binary?
A: No — and that's the point. A single binary succeeds by aggressively cutting scope. It targets the 80% of the API surface that developers actually use, not the full breadth. It's 'good enough' compatibility, not perfect parity. The bet is that most projects don't need everything Supabase offers.
Q: What does this mean for developers choosing between managed Supabase and self-hosting?
A: The gap between 'platform convenience' and 'self-hosted ownership' is closing. If you can run a Supabase-like backend with one binary and one config file, the calculus changes: you get the DX without the operational tax. For side projects and small teams, this could eliminate the managed-service lock-in entirely.
Q: Isn't Supabase's real advantage its ecosystem and constant feature expansion?
A: Exactly — and that's why Instancez will always lag behind. Supabase's moat isn't Postgres; it's the SDK in your package.json and the tutorial you followed. Every new feature Supabase ships widens the gap. But Instancez is betting that most developers don't need the cutting edge — they need something they can actually own and operate without losing their minds.