Supabase Raises $150M, Agrees to Buy Turso

On October 2, 2026, SiliconANGLE reported that Supabase raised $150 million in a round led by GIC, with CapitalG, IronArc and SquarePeg participating, and agreed to buy Turso for an undisclosed sum. The financing and acquisition were disclosed together, but the amount raised is not the purchase price. The proposed combination gives Supabase a way to serve fleets of small databases created by AI agents while keeping Postgres for applications that grow beyond those early workloads.

In Supabase’s October 2 acquisition post, CEO Paul Copplestone wrote, “For existing users, nothing changes,” and put the company’s current pace at more than one million database launches per week. Turso will continue work on SQLite, while Supabase continues building around Postgres. A route from a lightweight agent database into that broader application platform is the product ambition behind the agreement, rather than a newly released, unified service.

The financing and the purchase have separate economics

The new capital is intended partly for employee liquidity and partly for features aimed at AI agents. Employee liquidity can involve shares held by staff, so the stated round size alone does not show how much fresh cash will be available for product development. Nor does a round announced alongside an acquisition establish the consideration paid to Turso’s owners. The undisclosed purchase price makes it impossible to calculate a transaction multiple or infer how much of the financing will support the deal.

Why Turso fits fleets of small agent databases

The workload begins with frequency and isolation. An agent may create a prototype, exploration or dashboard that needs its own persistent state, even if it never becomes a large application. At high creation rates, assigning a dedicated, continuously running machine to every project would add overhead before the database has earned it. A small database that can be provisioned on demand and suspended while idle changes the economics of maintaining many separate projects. That is the infrastructure problem the acquisition is meant to address.

Turso’s acquisition account describes its open-source SQLite rewrite for server workloads, including concurrent writes, and a diskless cloud architecture built around a write-ahead log on S3. The service can provision isolated databases in Turso Cloud or in a customer’s own cloud. SQLite’s small footprint suits short-lived or narrowly scoped work, while concurrent-write support addresses a limitation of conventional SQLite in busier server environments. The architecture is about running a large population of databases economically, rather than maximizing the size of any single agent database.

SQLite first, Postgres as applications grow

The two engines have different intended jobs. Turso’s SQLite-based system supplies a lightweight database for an individual agent, task or early application; Supabase’s Postgres platform is the destination envisioned when an application needs to scale. Postgres also sits inside a wider backend offering with authentication, storage and integrations. A project that begins as isolated agent state may later need those services and more demanding database operations. This makes the transition between systems central to the strategy, rather than merely a change of database brand.

That transition has practical questions attached to it. Moving a growing application requires a way to transfer its schema and records, adapt code that depends on a particular SQL dialect, and connect the result to surrounding backend services. A path into the Supabase ecosystem is part of the plan, but no migration workflow or compatibility guarantee has been released. For developers, the useful distinction is between a database they can provision on Turso now and a simpler path into Postgres that the combined team intends to build.

Continuity for users, with integration still ahead

Existing Turso databases, APIs and workflows are set to continue operating, and Turso Database remains open source and under active development. The Turso team is joining Supabase: founder Glauber Costa takes the Head of Agentic Services role, alongside cofounder Pekka Enberg and their colleagues. Those commitments preserve the current SQLite service while putting its builders inside the organization that operates the Postgres platform. They also give the agent infrastructure effort a named leader.

Deeper integration is expected in the coming months. The key product question for that next phase is how an agent-created Turso database graduates into a Supabase Postgres application without making the developer rebuild the surrounding workflow by hand. Until that path is specified and delivered, customers have two continuing systems and a stated direction for connecting them. The migration mechanics and provisioning experience will show how much of that journey the combined platform can handle.