Blog
2 min read

Supabase Is Acquiring Turso to Build Database Infrastructure for AI Agents

Supabase announced on 2 October 2026 that it is acquiring Turso, the company that rebuilt SQLite in Rust and runs a platform for millions of on-demand databases. Turso keeps operating, Supabase stays Postgres-first, and nothing changes for existing users. Why agent-created databases are driving the deal and what to watch.

Supabase announced on 2 October 2026 that it is acquiring Turso. Turso's team, including co-founders Glauber Costa and Pekka Enberg, is joining Supabase, with Costa leading a new "agentic infrastructure" effort. (What Is Supabase?)

Why: agents create a lot of databases

Supabase's explanation is about AI agents and app builders. Agents now spin up millions of databases — for prototypes, dashboards, one-off apps — most of which are small and idle most of the time. That's a different workload from the traditional "one big production database".

Turso is built for exactly that:

  • It has rebuilt SQLite in Rust.
  • Its cloud platform can manage millions of databases, loading each when needed and suspending it when idle.
  • Databases can run on Turso Cloud or in customers' own clouds.

What changes for users

According to the announcement:

  • Nothing changes for existing Supabase users. Supabase keeps building around Postgres.
  • Turso keeps operating and continues its work on SQLite.
  • The long-term goal is one developer experience from prototype to production: SQLite for small, on-demand workloads, Postgres for applications that scale, with a "clear path" between them.

No pricing changes or timelines were announced.

What to watch

  • The migration path. "Start on SQLite, graduate to Postgres" is appealing, but SQLite and Postgres differ in types, SQL dialect, concurrency and features (row-level security, extensions, LISTEN/NOTIFY). How smooth Supabase makes that move will matter. (SQLite in Production, SQLite WAL Mode)
  • App builders. Lovable, Bolt and others lean heavily on Supabase-style backends; cheaper per-app databases could change how AI-built apps store data. (Best Database for an AI-Generated App)
  • Consolidation. Database infrastructure for agents is a hot space; expect more deals.

The practical advice hasn't changed

Whichever database your app starts on, the same checklist applies before real users arrive: access rules, backups you've restored, migrations in version control, and secrets kept server-side. (Supabase Row-Level Security Explained, Backups for Beginners)

Source: Supabase blog: Supabase is acquiring Turso

EasySpawn runs PostgreSQL right next to your app on every server, with daily backups — the "scale to production" half of the story from day one. See how it works or join the waitlist.

Related: Neon vs Supabase · Supabase vs Firebase · What Is PostgreSQL? · Postgres vs MySQL

Keep reading