Supabase Raises $150M and Acquires Turso for Agent Databases

Supabase has raised $150M in new funding led by GIC and announced an agreement to acquire Turso. CapitalG, IronArc, and Square Peg also participated in the October 2, 2026 financing. Supabase did not disclose a round label, valuation, ownership terms, or the split between primary capital and employee liquidity.

The company says the financing will support product development around agent-driven databases and provide liquidity for employees. The Turso agreement puts architecture behind that capital plan: Supabase is adding a SQLite-compatible system designed to provision large numbers of small, isolated databases while continuing to build its Postgres platform.

The combination matters because AI agents change the unit of database demand. A development team may once have planned one database around one application. An agentic system can create databases for prototypes, tasks, users, or agents at a rate that makes provisioning cost, isolation, observability, and the path to production part of the product itself.

What Supabase Announced

The company-issued funding announcement identifies GIC as the lead investor and CapitalG, IronArc, and Square Peg as participants. Supabase said the money will accelerate development around agent-driven databases and support employee liquidity. It did not name the financing as a Series G, Series F extension, or other round, so the accurate label is simply $150M in new funding.

The financing arrives four months after Supabase's $500M Series F, which GIC also led. Supabase described that June financing at a $10B pre-money valuation; the corresponding release described $10.5B post-money. The October announcement includes no new valuation, and both financings included employee liquidity, so adding every headline dollar together as fresh operating capital would overstate what the company disclosed.

Supabase also announced that it is acquiring Turso. The companies did not disclose the purchase price, expected closing date, consideration, conditions, or post-transaction ownership. Supabase said Turso will keep operating and will have a path into the broader Supabase ecosystem, while existing Supabase customers should see no immediate change.

Why Turso Fits the Agent Database Problem

Supabase's core platform combines Postgres databases with authentication, storage, Edge Functions, realtime subscriptions, vector search, APIs, and a partner marketplace. That model gives developers a production-capable relational database without requiring them to assemble every backend service independently.

Turso addresses a different workload shape. Its team rebuilt SQLite in Rust and created an architecture that can manage millions of databases on one server by loading and suspending them as needed. Supabase says that makes it possible to give each agent a database on demand in Turso Cloud or a customer's own cloud without provisioning a dedicated machine for every database.

The distinction between SQLite and Postgres is central to the strategy. Supabase argues that SQLite fits small, on-demand workloads, while Postgres becomes the stronger choice as an application grows. The acquisition is meant to connect those stages so an agent can create a cheap database for an early task without forcing a developer to discard the surrounding experience when that task becomes a production system.

That connection is still a plan, not a completed integration. Supabase has not disclosed packaging, pricing, migration behavior, integration milestones, or how Turso's existing service and open-source projects will be governed inside a larger platform. The engineering value will depend on whether the promised graduation path works without turning two clean product ideas into one complicated control plane.

The Scale Supabase Is Reporting

Supabase says more than 13M developers use its platform. The October announcement reports more than 1M users and 4M databases added per month, with agents or AI-driven tools creating 70% of new databases. Supabase's Turso post separately says the platform is launching more than 1M databases per week.

Those are company-reported figures, and the reviewed sources do not define whether every developer, user, or database is active, paid, or retained. They still describe the operating pressure that Paul Copplestone, Supabase's co-founder and CEO, and Ant Wilson, its co-founder and CTO, are trying to address. In June, the company reported nearly 10M developers, 600% year-over-year growth in database launches, and more than 60% of new databases created by AI tools.

Turso co-founder Glauber Costa will join Supabase as Head of Agentic Services, while co-founder Pekka Enberg and the rest of the Turso team will also join. Keeping the team and the existing Turso service matters because the acquisition is buying operating knowledge and an open-source community, not only database code.

What the $150M Changes

The round gives Supabase more capital to build for a market where software creation is accelerating faster than traditional infrastructure planning. It also gives employees another liquidity window, continuing a practice Supabase highlighted in its June financing. What the announcement does not establish is how much of the $150M is new primary capital, how the financing changes ownership, or whether the valuation moved from June.

GIC's repeat lead shows sustained institutional conviction only four months after the Series F. CapitalG described Supabase as infrastructure beneath the expansion of software creation and connected its investment to the Turso acquisition. IronArc and Square Peg add to the syndicate, although the official announcement did not identify individual deal partners from those firms.

The harder obligation begins after the capital lands. Fast database creation raises the number of systems that need safe defaults, access controls, auditability, backup behavior, cost visibility, and a clear owner. Making a database feel as easy to create as a file is useful; making the responsibilities inside that file disappear would create a much less charming kind of scale.

What Developers and Infrastructure Buyers Should Watch

Supabase is betting that the next backend platform will serve both human developers and software agents. Turso gives the company an architecture for lightweight, per-agent databases, while Supabase provides a Postgres-centered route toward larger production workloads. If that handoff works, developers may be able to move from experiment to durable application without changing the surrounding platform every time the data model grows up.

Buyers should watch the integration roadmap, pricing, database-isolation model, observability, migration path, and governance for automatically created resources. They should also separate scale from quality: millions of new databases demonstrate demand and provisioning volume, while reliability, retained workloads, paid adoption, and production outcomes determine whether that activity compounds into infrastructure value.

Supabase's $150M and the Turso agreement put capital, architecture, and people behind one clear thesis. Agents are going to create more software and more databases, and the company wants to control the moment when a disposable experiment becomes a system somebody has to trust.