Supabase is acquiring Turso: Postgres stays, SQLite stays, Glauber leads agentic infra

Supabase’s blog on October 2, 2026 announces that it is acquiring Turso—Turso is joining Supabase to build database infrastructure for agent-scale, on-demand databases (blog). The post does not state a deal price, equity terms, or close date.

What stays the same (engines)

Supabase’s continuity line is explicit: Supabase will continue building around Postgres, while Turso will continue its work on SQLite. This is not framed as a forced single-engine migration or an end to either product. Supabase also says that for existing users, nothing changes—a vendor assurance, not a newsroom SLA guarantee.

Why Turso (architecture)

Supabase describes Turso’s path as a Rust-rebuilt SQLite and a cloud design where a single server can manage millions of databases, loading when needed and suspending when not—suited to provisioning per-agent databases on Turso Cloud or in customer clouds. Named examples in the post include Superhuman, Sauna.ai, CTO.new, and Mastra running that pattern—nominative, Supabase-attributed, not partnership exclusivity claims.

Separately, Supabase says it is already launching over one million databases per week—a Supabase-attributed scale figure, not independently verified here.

Who joins and who leads

Supabase welcomes Glauber Costa and Pekka Enberg with the rest of the Turso team. Glauber will lead the agentic infrastructure effort at Supabase. Roadmap language about a path into the broader Supabase ecosystem as workloads grow stays vision-level; the post does not ship a merge timeline or product rename GA.

Who should care

Teams on Supabase Postgres, Turso SQLite, or agent stacks that spin up many short-lived databases should read the announcement for the continuity and leadership framing—and wait for contractual/product detail beyond “nothing changes” before treating plan terms as locked.