Supabase raises $150M and agrees to acquire Turso for agent databases

Why it matters

Supabase is using fresh capital and an agreement to acquire Turso to move from benefiting from AI-built apps to supplying infrastructure for agents that create and manage many isolated databases.

Supabase said on October 2nd it had raised $150 million led by GIC and agreed to acquire Turso, adding a database built to provision large numbers of small, isolated databases for AI agents. The financing arrives four months after Supabase's $500 million Series F and includes employee liquidity, according to the announcement.

For co-founder and CEO Paul Copplestone, the move extends a product thesis that began with a backend problem at an earlier startup. Copplestone has said he wanted to build a database company; while working on his second startup, he ran into scaling limits with Firebase, moved the product to Postgres, and built and open-sourced real-time functionality around it. That work became the starting point for Supabase.

Supabase says it is now adding more than 1 million users and 4 million databases each month, with agents or AI-driven tools creating 70% of new databases, according to the announcement. Those are company-reported figures, and the announcement does not define how it counts users or databases. Supabase also says more than 13 million developers use its platform. Its June Series F post reported nearly 10 million developers; Supabase has not explained whether the counting method changed.

From usage growth to database architecture

One constraint in agent-built software is that a system running many agents may need separate data stores for individual agents, tasks, or customers. Supabase says Turso's architecture can provision databases on demand in its public cloud or in customers' own cloud environments, without assigning a dedicated machine to every database.

Turso is an open-source, SQLite-compatible database written in Rust. Its architecture treats a database as a lightweight file rather than a long-running server process, a design its developers say makes it possible to create and operate very large numbers of small databases. The deal gives Supabase a different database model alongside its Postgres-centered platform, which includes authentication, storage, edge functions, real-time subscriptions, and vector search.

Turso founder Glauber Costa (@glaubercosta) will join Supabase to lead the effort. Turso's founder profile says Costa worked on Linux, virtualization, storage, and containers at IBM and Red Hat, spent nearly a decade at ScyllaDB, and later authored the Glommio Rust asynchronous executor at Datadog. Turso co-founder Pekka Enberg and the rest of the team are also joining, according to the announcement. Costa has described his ambition as serving more than a billion databases; he said joining Supabase brings that goal closer.

Supabase says Turso will continue operating, with a path into the broader Supabase platform. The acquisition price and the timing and conditions for closing were not stated in the announcement. Developers will need details on how Turso's separate product, cloud service, and open-source projects will fit alongside Supabase after the deal.

A second round with employee liquidity

Supabase's June Series F was led by GIC at a $10 billion pre-money valuation, according to the company's funding post. The new $150 million round also includes CapitalG, IronArc, and SquarePeg, according to the announcement. Supabase did not state a valuation for this financing. Both funding announcements identify employee liquidity as a use of proceeds, giving staff a way to sell shares while Supabase continues investing in product development.

Supabase is pairing employee liquidity with an infrastructure bet. Supabase says AI coding tools are driving successive waves of people building software, and that agents are increasingly creating the databases those applications need. The agreement to acquire Turso adds a lightweight, many-database architecture to Supabase as it serves that usage alongside growth in its existing Postgres service.

UpGuard's September 25th report identified roughly 300,000 unique domains with Supabase indicators and 16,326 databases exposing readable tables. More than half of those readable databases had table-schema indicators of personally identifiable information; UpGuard said its assessment was based on schemas, not a review of every record. RuntimeWire's September report covered the findings, which UpGuard attributed to customer or application configuration misconfigurations rather than a Supabase platform breach. The proposed acquisition does not directly address those misconfigurations, while the growth in automatically created databases puts safe defaults and clear isolation controls on Supabase's infrastructure agenda.

Supabase's bet depends on whether developers use Turso's architecture as part of the Supabase stack and whether integration preserves Turso's standalone appeal. Supabase has committed to continued Turso operations and a path into its platform; the announcement does not lay out the technical transition or how the products will be packaged. For Copplestone, the bet is that the next wave of software creation will need backends designed for agents to create databases as readily as they create code.