Disclosure up front: I've used both Supabase and Turso. I've evaluated both for real projects, and I recommend both. That's part of why I have an opinion here. I want both of them to keep being great.
Two databases I actually like just became one company
Supabase announced it is acquiring Turso. Glauber Costa, Turso's cofounder and CEO, joins Supabase as Head of Agentic Services, along with cofounder Pekka Enberg and the rest of the team. No price was disclosed.
If you haven't followed both products: Turso rebuilt SQLite from the ground up in Rust and built a cloud platform around a "many databases" architecture. One database per user, per agent, per task, provisioned on demand, on a WAL-on-S3 design, in their cloud or yours through BYOC. Supabase is the leading Postgres platform: database, auth, storage, and a broad integration ecosystem, launching over a million databases a week.
Two of the best commercial open source companies in the database space, and one just bought the other. COSS is alive and well, and that's worth celebrating on its own.
Why this deal makes sense on paper
The strategic logic is actually good. AI agents are creating a new workload shape: one agent, one task, one user, millions of small databases that come online instantly and get created at a rate infrastructure has never seen. SQLite is the natural fit for that. Postgres is what you want when the application outgrows it. Supabase's own announcement says it plainly: "SQLite is well suited to these small, on-demand workloads. Postgres is what you want as your application scales."
And the migration story isn't hand-waving. Turso is building a Postgres frontend on the same Rust core as its SQLite engine. Their framing is "the LLVM of databases": one modern core, many frontends. A "seamless path to Postgres when an application outgrows them" is credible engineering, not marketing. Teams like Superhuman, Sauna.ai, and Mastra already run agent workloads on Turso at scale.
So yes: on paper, this is a smart acquisition. Start small on Turso, scale into Supabase, stay in one ecosystem the whole way. I get it. I'd make a version of that pitch myself.
The instinct will be to consolidate
Here's the part I'll believe when I see.
The announcements promise continuity. Supabase: "For existing users, nothing changes." Also Supabase: "Turso will continue operating, with a clear path into the broader Supabase ecosystem as workloads grow."
Take those seriously, but read them carefully. "Nothing changes" is exactly what you say to calm users and avoid churn in the weeks after an acquisition closes. It's churn management, not a strategy guarantee. And "Turso will continue operating" is a lower bar than it sounds. A product can keep operating and still get absorbed: same dashboard, same billing, same sales team, same brand slowly dissolving into the parent platform. Operating and independent are not the same thing.
I've watched this pattern from the inside of enough companies to recognize it. The business instinct after any acquisition is consolidation: one brand, one platform, one toolset, one sales team. It feels efficient. It demos well to a board. And for products that are actually different, it's usually a mistake — the buyer gets confused about what to buy and which solution to use, the value props get muddied, and you end up chasing multiple ideal customer profiles with one muddled message. Salesforce and Adobe built empires on the monolith M&A pattern, and even there, the products that kept their identity thrived while the absorbed ones became feature checkboxes.
Neither company has said they'll do this. I'm not predicting they will. I'm saying the pressure will exist, especially from business leaders who may not understand what makes COSS companies valuable in the first place, and resisting it is the actual hard part of this deal.
Why these two can't merge
Could Supabase and Turso converge into one platform? I won't say it's impossible. I'll say it would be challenging, and it would almost certainly cost something from one or both.
They're different technologies. Turso is SQLite rebuilt for server workloads: concurrent writes, millions of small databases, per-user economics, BYOC. Supabase is platform Postgres: fewer, larger, more powerful databases with an ecosystem around them. Those aren't two flavors of the same problem. They're two different problems.
The communities are different too. Turso runs an open-contribution model — the full test suite is open, contributions welcome — and its engine is MIT licensed. Supabase's community is the Postgres ecosystem. Smash the two together under one brand and one roadmap, and you don't get a bigger community. You get two communities wondering which one they belong to.
Convergence would mean one of these products stops being fully itself. That's the sacrifice. It would be a shame, because both are great at what they actually do.
The winning play: loose coupling
The best version of this deal is the least dramatic one: keep Turso Turso.
Separate brand, separate pricing, separate community. Turso keeps solving its problem its way, Supabase keeps solving its problem its way, and the connection between them is a bridge, not a merger. Real migration and scaling tooling, cross-promotion, and maybe shared services like billing and identity behind the scenes where the buyer never has to think about them.
That preserves two clear value propositions and two clear customer profiles instead of muddying both. It's the difference between a portfolio and a monolith. Portfolios compound; monoliths average.
To be clear, this isn't me telling Supabase how to run their company. They've earned the benefit of the doubt, and they've been one of the most disciplined open source companies in the space. It's me naming what I'll be watching.
What I'm watching
The next 12–24 months will tell the story. The signals are observable:
- Good outcome: Turso keeps shipping as its own product, with its own branding, pricing, and community. The SQLite-to-Postgres path stays a bridge between two platforms.
- Warning signs: a shared sales motion appears, "Turso" becomes a feature inside the Supabase dashboard, the brand starts dissolving into unified platform messaging.
And I'll hold myself to the same standard: if Turso is still independent and both platforms are thriving through 2027 and 2028, my caution was overweighted. I'll be glad to be wrong.
Both of these are great platforms solving real problems, built by teams that have earned their communities. COSS is alive and well. The question now is whether this deal becomes the example of how to combine strengths without collapsing identities, or one more data point for the monolith rule.
I'm rooting for the exception.
Top comments (0)