News · 2026-10-03

Supabase is buying Turso to give AI agents cheap databases of their own

Supabase, the hosted Postgres database company, is acquiring Turso, the company that rewrote the SQLite database in Rust, to build infrastructure for the flood of small databases that AI agents now create. Both companies announced the deal on October 2 without disclosing a price. Supabase says it is already launching more than one million databases a week.

Key facts

• Scale: Supabase says it launches "over one million databases per week," and that agents are spinning up "millions of databases."
• When: announced October 2, 2026, by both companies.
• People: Turso founder Glauber Costa becomes Supabase's Head of Agentic Services; cofounder Pekka Enberg and the Turso team join too.
• Primary sources: Supabase's announcement and Turso's announcement.

Most applications have historically had one big central database. Coding agents have changed that arithmetic. When an agent builds a prototype, a dashboard or a quick internal tool, it needs somewhere to keep the data, and an agent can start hundreds of such projects in the time a person starts one. "AI is enabling builders to create an immense amount of software," Supabase chief executive Paul Copplestone wrote. "Today, agents are spinning up millions of databases to power the prototypes, explorations, dashboards, and apps they're building."

Turso puts the thesis more bluntly: "One agent, one task, one user. Each agent deserves its own isolated database and the economics have to work at millions of databases."

What Turso built

SQLite is the most widely deployed database in the world. It lives as a single file inside an application rather than as a separate server, which makes it tiny and fast but historically awkward for busy server workloads, because only one writer can change the data at a time. Turso rewrote SQLite from scratch in Rust to lift limits like that one, and built a cloud service where, as Supabase describes it, "a single server can manage millions of databases, loading them when needed and suspending them when they're not."

The trick is that most of those databases are idle most of the time. Turso's architecture post describes keeping each database's recent changes in Amazon's fast S3 Express storage, periodic full snapshots in ordinary S3, and a local disk as a cache. Think of a hotel that has a room for every guest who has ever booked, but only turns on the lights and heat in rooms that are actually occupied tonight. That is how the cost per database can drop low enough to give each agent its own.

Customers already use it in two different ways. In a case study published in August, Turso says CTO.new gives each project's team of agents one shared database that acts as a task board, with tens of thousands of databases in total. In a 2024 post, Turso described another customer creating hundreds or thousands of throwaway databases for a single agent's tasks, using branching to roll back mistakes. Both sets of numbers are vendor-reported.

What changes for users

Supabase says that for existing users "nothing changes." Supabase keeps building around Postgres, Turso keeps working on SQLite, and the plan is a path from a small SQLite database into full Postgres when an application grows. Turso lists four promises: existing databases, APIs and workflows continue; Turso Database stays open source and actively developed; there will be a route into Supabase's Postgres; and "deeper integration" is coming in the coming months. Copplestone said, "Agents have become the primary users of technology."

Note that "Turso" names more than one project. The newer Turso Database is the Rust rewrite; libSQL is an older fork of SQLite that the company says it still maintains. Both repositories currently carry MIT licenses. The open-source promise in the acquisition post names Turso Database specifically.

Why it matters

This is a bet that the agent era needs a different shape of infrastructure, not just more of the old shape. Ground Truth has covered the harness side of this, such as a composable agent harness and coding agents that keep a persistent picture of a repository. Somewhere to keep an agent's state cheaply is the storage half of the same problem; our lesson on agent memory covers why it matters.

The caveat

Neither company disclosed financial terms, and Supabase's million-databases-a-week figure is not broken down into how many are created by agents, actively used, or paid for. Reaction on Hacker News was mixed: some developers said the deal made them more comfortable choosing Turso, while others worried that acquisitions often end with products being closed or deprioritized. Commenters also raised a slow data import in one public benchmark attempt; Enberg replied that the problem was in data loading rather than the benchmark itself and that the team intended to improve it. Promises about open source and product continuity are commitments to watch, not outcomes yet.

Primary source, verified: read the paper →

Ground Truth. (2026, October 3). Supabase is buying Turso to give AI agents cheap databases of their own. Ground Truth. https://groundtruth.day/news/supabase-acquires-turso-to-give-every-agent-its-own-database.html

@misc{groundtruth:supabase-acquires-turso-to-give-every-agent-its-own-database,
  title  = {Supabase is buying Turso to give AI agents cheap databases of their own},
  author = {{Ground Truth}},
  year   = {2026},
  month  = {oct},
  url    = {https://groundtruth.day/news/supabase-acquires-turso-to-give-every-agent-its-own-database.html}
}

Topics: industry · acquisitions · databases · agents · open-source · infrastructure