The database company behind Supabase is buying Turso, the startup that rebuilt SQLite in Rust, and the deal keeps both products alive. The acquisition centers on agents, with the combined team now working to build infrastructure for the agent-built future. The two companies were solving similar database problems before the merger, and now their joined effort is aimed at that shared direction.
What the acquisition means
The company behind Supabase sees a growing need for databases as agents build more software, and it believes that demand will eventually exceed the world’s current ability to supply them. That is the reasoning behind the acquisition, which is designed to close that gap. Supabase currently starts up over one million databases per week.
The deal keeps Supabase’s existing Postgres-based offering running while bringing in Turso’s work on SQLite. Together, the two companies are creating something new that will bring the Supabase experience to every agent.
Nothing alters for current users. Supabase keeps developing around Postgres, and Turso carries on with its work on SQLite.
The tech behind Turso
Turso rebuilt SQLite in Rust and created a cloud platform where a single server can manage millions of databases, loading them when needed and suspending them when they’re not. That architecture makes it possible to provision a database for each agent on demand, whether on Turso Cloud or in customers’ own clouds.
The company’s customers include Superhuman, Sauna.ai, CTO.new, and Mastra. All four use Turso’s multi-database management system to handle small, on-demand workloads.
Why the merger makes sense
Supabase is buying Turso with the aim of building a fresh type of database infrastructure capable of scaling up to match the expansion of agent-built software. Both firms are united by their dedication to open source, their attention to developer experience, and their willingness to take on difficult infrastructure challenges.
Glauber Costa and Pekka Enberg are joining Supabase as part of the deal, along with the rest of the Turso team. Glauber will take charge of the agentic infrastructure work.
How the two systems compare
| Feature | Supabase (Postgres) | Turso (SQLite) |
|---|---|---|
| Use case | Production applications | Prototypes, explorations, dashboards, small workloads |
| Scale | One million databases per week | Millions of databases managed by a single server |
| Cost model | Provisioning a dedicated machine | Cheap to create, available on demand |
| Path to production | Clear | Clear |
The pairing delivers a consistent developer experience across every stage, from early prototyping through full production deployment. It eliminates the need to set up a separate machine for each small workload, while also keeping database costs low and making them ready whenever they’re needed.
What this means for the future
Supabase’s mission is to store the world’s data, and agents are going to create a lot more of it. This acquisition gets the company closer to that goal.
The deal is notable because it keeps both products alive. Supabase isn’t replacing its Postgres offering with Turso’s SQLite work; it’s combining the teams to build something new. That’s a rare move in acquisitions, and it reflects how closely the two technologies actually fit together.
This is a win for developers who want a consistent experience across prototype and production, and it’s a bet that agents will keep creating more software than the world’s current database capacity can handle.
Source material: “Supabase is acquiring Turso,” supabase.com.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.