The Pulse
Supabase Acquires Turso to Give AI Agents Their Own Databases
Supabase is acquiring Turso to build infrastructure for AI agents that need cheap, on-demand databases. The companies say Turso will keep supporting SQLite while Supabase continues to build around Postgres.
AI.info Team · Written with AI ·
Supabase says existing users will see no change, even as its acquisition of Turso sets up a new database offering for AI agents. The companies plan to keep Supabase’s Postgres work and Turso’s SQLite work running in parallel, then build a path between the two as applications grow.
Announced on October 2, 2026, the deal addresses a mismatch the companies see in agent-built software: each agent or task may need a small database on demand, while a conventional database setup can require more infrastructure than a short-lived workload warrants. Neither company disclosed a purchase price or other financial terms in its announcement.
Millions of databases, created on demand
Supabase says it is already launching more than one million databases a week. Its argument is that agent-generated prototypes, dashboards and applications will drive demand beyond what current infrastructure can economically support, particularly when each task needs an isolated database rather than a shared central store.
For those smaller workloads, Supabase points to SQLite: it can be created on demand without provisioning a dedicated machine for every database. Postgres remains the intended destination as an application grows. The proposed product direction is to give developers a similar experience from prototype to production, while changing the database technology beneath it.
Turso’s architecture is the acquisition’s foundation
Turso rebuilt SQLite in Rust and developed a cloud service in which one server can manage millions of databases, loading them when needed and suspending them when idle, Supabase says. The architecture can provision databases for individual agents in Turso Cloud or in customers’ own clouds. Supabase names Superhuman, Sauna.ai, CTO.new and Mastra as companies using that model.
The Turso announcement describes its service as using a diskless architecture with write-ahead logging on S3, and says it addressed SQLite’s limits for server workloads, including concurrent writes. Turso says customers can continue using its databases, APIs and workflows; its database remains open source and actively developed.
Existing products stay separate for now
The companies’ assurances to current customers sit alongside a promise of deeper integration in the coming months. They have not specified what that integration will look like or when a migration path between SQLite and Postgres will become available. Turso says customers will have a route into standard Postgres through Supabase when SQLite no longer fits, with Multigres as an option for larger-scale workloads.
Paul Copplestone, Supabase’s CEO, framed the deal around the shift in who builds and uses software: Agents have become the primary users of technology, and Supabase is the leading database for the agentic era. The full statement appears in Turso’s acquisition announcement.
Glauber Costa will lead agentic services
Supabase says Turso founder Glauber Costa will lead the agentic infrastructure effort, joining Supabase with co-founder Pekka Enberg and the rest of the Turso team. Turso identifies Costa’s new role as Head of Agentic Services.
The immediate change for Turso customers is limited: the service continues, and its open-source database remains under active development. The larger test for the acquisition is whether the companies can connect lightweight, agent-specific SQLite databases to Supabase’s Postgres platform without disrupting the products developers already use.