Turso is going to Supabase. Now watch the pricing.

There is now one less independent database company. Supabase is buying Turso, the libSQL company, and has been for about a month: the announcement predates every breach on this week's front page, which is part of why it is already slipping into "older than you think" territory.

Consolidation of this kind reads as consolidation of responsibility. Turso's pitch was edge-first: distributed libSQL replicas close to users, a generous free tier, and a CLI everybody enjoyed finding. Supabase's pitch is platform-first: Postgres as the spine, auth and storage and realtime hung off it, pricing that starts at free and climbs a plan ladder with seats and compute limits sitting on every landing stage. Those two sentences used to describe two companies that competed for your next project's database. They describe one roadmap now.

What the pricing might do

Nobody has announced what Turso's plans become under Supabase, so everything past this paragraph comes with a label: speculation, clearly marked as such.

The base rates say consolidation usually goes one of two ways. In the friendly version, the free tier survives as an acquisition funnel, existing databases keep grandfathered pricing until they graduate into Supabase's plan structure, and the two audiences talk to each other without either product being disabled. In the unfriendly version, the generous free tier gets quietly reshaped into somebody else's plan walls: databases capped at count, compute metered in a currency nobody chose, and a mid-tier you used to fit under now holding features you used to consider baseline. The second version has plenty of precedents, and the warning sign to watch is whether Turso's pricing page starts describing what Supabase's pricing page describes.

The people with real skin in this are running libSQL to production, often on a free tier they chose precisely because it was generous. If you are one of them, the checklist is short and boring, which is what makes it effective. Read the migration notice when it comes, note your current bill and your current limits, and be honest about how hard you would be hit by a plan reshuffle. Waiting for the answer is not a plan: the intelligent move is having an exit route priced up before you need it.

What we would do, talking as the operators

We write this blog, and we also run a database host, so take the recommendation with the disclosure attached rather than assuming neutrality.

If what you liked about Turso was libSQL, there is a way to keep it without betting on anyone's post-acquisition pricing. Layerbase hosts managed libSQL: free to start, priced to stay affordable as you grow, and the database branches like a git repo, which is the feature that made libSQL interesting in the first place. That is an underline-free dofollow, because we mean it: if the consolidation wave has taught one thing, it is that the durable answer is picking a host whose pricing you can read today, not the vendor you hope will be generous tomorrow.

The database market consolidates the way the cattle market does. Somebody always ends up with the brand. Your job is to be the person whose migration was boring.

From the desk that wrote this

This blog is run by the team behind Layerbase, so every post comes with a conflict of interest attached rather than concealed behind it.