Supabase Raises $150M and Is Buying Turso, Betting AI Agents Need Millions of Tiny SQLite Databases

Supabase is buying Turso, the startup that rewrote SQLite in Rust and built a cloud that can host millions of tiny databases on a single server. Both companies announced the deal on October 2, 2026, the same day Supabase said it had raised $150 million in new funding led by Singapore’s GIC.

Neither side disclosed a price or a closing date. What they did spell out is the thesis: AI agents are creating databases faster than traditional infrastructure can handle, and Supabase wants a cheap SQLite layer for that work, with its Postgres platform waiting for anything that grows up.

For developers already running apps on Turso or its open-source libSQL fork, the official line is that nothing changes. That promise is easy to make on day one. The harder questions are about what happens in year two.

What Supabase and Turso Actually Announced

In its announcement post, Supabase said “Turso is joining Supabase” and that “for existing users, nothing changes.” Supabase will keep building around Postgres, and Turso will keep working on SQLite. Turso founder Glauber Costa will lead what Supabase calls its agentic infrastructure effort.

Turso’s own post, “Turso is joining Supabase to give every agent its own database”, says Costa joins as Head of Agentic Services, together with cofounder Pekka Enberg and the rest of the Turso team. It lists four promises to users: the platform keeps running, Turso Database stays open source, there will be a “graduation path” to Postgres, and deeper integration is coming “in the coming months.”

The deal landed inside a funding announcement. Per the Supabase press release, the $150 million round was led by GIC, with Alphabet’s growth fund CapitalG, IronArc and SquarePeg participating. It comes four months after Supabase’s $500 million Series F, which TechCrunch reported valued the company at $10 billion. Supabase says part of the new money provides liquidity for employees. It did not state a valuation for this round.

Why Supabase Wants a SQLite Company

Supabase is a Postgres company, so buying a SQLite specialist looks odd at first. The explanation is in its own numbers, all of which are company-reported.

Supabase says it now launches more than one million databases a week. The press release puts it at more than 4 million databases and 1 million new users a month, and claims 70% of new databases are created by agents or AI-driven tools such as Claude Code and Codex. If you have followed how coding agents behave in the wild, including the 13,000 screenshots they pushed to public GitHub, you already know they spin up resources freely.

A full Postgres instance per prototype is expensive at that volume. “Agents should be able to create a database as easily as creating a file, with just as little concern about cost,” Supabase wrote. SQLite fits small, short-lived workloads. Postgres fits apps that scale. Supabase wants both under one roof with one developer experience.

CEO Paul Copplestone framed it plainly in the release: “The future is agents and the architecture Turso provides will help us accelerate Supabase as the backend platform for supporting that future.”

What Turso Built

Turso’s first big project was libSQL, a fork of SQLite created because SQLite is open source but does not accept outside contributions. It later began a ground-up rewrite in Rust, first called Limbo and now Turso Database, aimed at concurrent writes and server workloads.

The cloud product is the part Supabase is paying for. Turso describes a “diskless, WAL-on-S3 architecture” in which one server manages millions of databases, loads them on demand and suspends idle ones. Customers can run it on Turso Cloud or in their own cloud accounts (BYOC). Both companies name Superhuman, Sauna.ai, CTO.new and Mastra as users.

Costa’s stated goal, repeated in both posts, is to serve “upwards of a billion databases.” That is an ambition, not a metric. Neither company disclosed how many databases Turso hosts today or what its revenue looks like.

Confirmed vs. Unconfirmed

What It Means for Developers

Turso Cloud customers. Your databases, APIs and workflows should continue as before, according to Turso. Turso’s pricing page still lists a free tier with 100 databases and 5GB of storage, and paid plans from $4.99 a month. Nothing in either announcement mentions price changes, but nothing guarantees current prices either. Export a backup and keep your migration options open, which is good practice with any acquired vendor.

libSQL users. The announcements barely mention libSQL. Turso’s docs already call libSQL “where we started” and recommend Turso Database for new projects, while keeping libSQL for “mission-critical workloads that need a battle-tested foundation today.” If you embed libSQL, watch the commit activity on its GitHub repo over the next few months. That will tell you more than any press release.

The license question. Turso Database and libSQL are both MIT licensed, and Supabase’s main repository is Apache 2.0. MIT means any code released so far can be forked and maintained by anyone, forever. What an owner can change is the license on future releases. “Open source stays open” is a welcome promise, but it is a promise from the new owner, not a legal guarantee.

Supabase users. Nothing changes for your Postgres projects today. Reading both posts, the likely direction is a lightweight SQLite option inside Supabase for agent sandboxes, prototypes and per-tenant data, with a path to full Postgres. Turso’s post also mentions Multigres, Supabase’s sharding project, as the step beyond that. If you are already building agent workflows, or tracking efforts like Cloudflare giving agents their own wallets, expect more infrastructure vendors to sell “one resource per agent” as a product.

Across regions. Neither company announced changes specific to the US, Canada, Australia or India. Pricing on both platforms is in USD, so for Indian and Australian developers the main exposure is currency, not policy. Data residency for Turso regions after the deal has not been addressed.

The Skeptic’s Read

The Hacker News thread on Supabase’s post passed 190 points and 100 comments within hours, and the mood was split. Some users welcomed the stability. One wrote that worries about Turso the company had pushed them toward plain SQLite, and that the acquisition would make them choose Turso going forward.

Others were blunt. “As a turso customer, I do not want this,” wrote one. Another pointed to ClickBench GitHub threads where attempts to benchmark Turso kept turning up bugs, and hoped Supabase would put more resources into fixing them. Several asked the obvious question about price and whether Turso’s hosting business was making enough money. Those are commenters’ guesses. Neither company has addressed them.

The pattern is familiar. A well-funded platform buys a smaller infrastructure startup, promises continuity, and then folds the product into its own over time. Sometimes that works out for users. Sometimes the standalone product fades. Supabase has built its business on open-source code, and the founders clearly want this to look like a merger of like-minded teams. Still, “nothing changes” is a statement about today.

What to Watch

Three things will show where this is going. First, whether Turso Cloud keeps shipping features as its own product or turns into a Supabase add-on. Second, what the promised graduation path looks like in practice, since moving from SQLite semantics to Postgres is not trivial for real apps. Third, whether Supabase pricing gets a cheap per-agent database tier, which would be the clearest sign of where Turso’s tech ends up. For a wider view of how agents are reshaping software stacks, see our earlier piece on open-source repos founders and vibe coders rely on, where Supabase already featured.

Frequently Asked Questions

Did Supabase acquire Turso?

Supabase announced on October 2, 2026 that it is acquiring Turso, and Turso confirmed it on its own blog. Neither company has said when the deal closes.

How much did Supabase pay for Turso?

The price was not disclosed. SiliconANGLE and other outlets describe it as an undisclosed sum.

Will Turso Cloud shut down?

Not according to either company. Turso says the platform “keeps running” and that databases, APIs and workflows continue as they do today. No long-term timeline was given.

Is libSQL still open source?

Yes. libSQL and Turso Database are both under the MIT license, so existing code can always be forked. Turso promised that Turso Database “remains open source and actively developed,” but did not make a specific statement about libSQL’s roadmap.

What does this mean for Supabase users?

Nothing changes for existing Postgres projects. Supabase says it plans to use Turso’s architecture to offer cheap, on-demand databases for AI agents, with a path into Postgres as apps grow. Details and a timeline have not been announced.