Pull to refresh
Logo
Supabase acquires Turso to give AI agents their own databases

Supabase acquires Turso to give AI agents their own databases

New Capabilities

Postgres platform raises $150M and adds a lightweight SQLite engine as agents create most new databases

3 days ago: Supabase announces $150M round and Turso acquisition

Overview

Updated 2 hours ago

Supabase, the open-source Postgres platform, is acquiring Turso, the company behind a Rust rewrite of SQLite built to spin up millions of small databases on demand. The deal, announced October 2, aims to give every AI agent its own instant database.

The same day, Supabase closed $150 million in new funding led by Singapore's sovereign wealth fund GIC, four months after a $500 million Series F. The two engines stay separate, Postgres and SQLite, with a "graduation path" from lightweight Turso databases into Supabase Postgres as workloads grow.

Why it matters

If the deal works, every AI agent gets a dedicated database in milliseconds, changing how developers provision backend infrastructure.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

No questions yet — be the first to ask.

Key Indicators

$150M
New funding round
Led by Singapore's GIC, with CapitalG, IronArc, and SquarePeg participating.
$10.5B
Supabase valuation
Set by its $500M Series F in June 2026, four months before the Turso deal.
4M
Databases added per month
Supabase adds over a million users and four million databases monthly.
70%
Databases created by agents
Share of new databases on the platform created by agents or AI-driven tools.

Voices

Curated perspectives — historical figures and your fellow readers.

Ever wondered what historical figures would say about today's headlines?

Sign up to generate historical perspectives on this story.

People Involved

Organizations Involved

Timeline

June 2026 October 2026

3 events Latest: 3 days ago
  1. Supabase announces $150M round and Turso acquisition

    Latest Acquisition

    Supabase announced new funding led by GIC and its agreement to acquire Turso, with Turso Cloud continuing operations.

  2. Supabase raises $500M Series F at $10.5B valuation

    Funding

    The round valued Supabase at $10.5B and came amid 600% year-over-year database growth.

  3. Agents already deploy most new databases

    Milestone

    Supabase reported that agents were deploying the majority of new databases on the platform, driving 600% YoY growth.

Scenarios

1

Supabase ships a Turso-based database tier for agents

Likely Resolves by Q2 2027

Discussed by: SiliconANGLE, which notes Supabase could use Turso technology to enhance Supabase Compute, its hosted sandboxes for long-running AI agents.

Supabase integrates Turso's lightweight engine as a cheaper, instant-provisioning database tier, letting agents spin up per-agent databases in milliseconds. A graduation path then moves them into Postgres as they scale. This is the outcome both companies' announcements point toward.

2

Turso Cloud stays independent, with only loose integration

Possible Resolves by Oct 2, 2027

Discussed by: FounderMag, which notes that "nothing changes immediately" and flags roadmap focus as the open question.

Turso keeps operating as its own cloud product and open-source project. Supabase integration stays limited to a documented migration path, while the promised deeper integrations remain minor. This holds if both engines prove hard to bridge technically or strategically.

3

SQLite-to-Postgres graduation path stalls on migration friction

Possible Resolves by Q1 2027

Discussed by: Layerbase, which notes the upgrade path points one way and that neither company has explained how schemas, auth, and row-level security will move between engines.

The pitch is the same developer experience from prototype to production. That depends on moving schemas, auth, and security policies from SQLite to Postgres, work neither company has detailed. If migration tooling ships late or poorly, developers stick with Turso standalone or skip both for new projects.

Historical Context

2 moments from history that rhyme with this story — and how they unfolded.

October 2014

Google acquires Firebase (2014)

Google acquired Firebase, founded in 2011 as a real-time database and backend platform for mobile apps. The startup's synchronization model let developers add server-side backends without managing servers.

Then

Firebase became Google's mobile development platform, kept its product identity, and was rebranded and integrated with Google Cloud.

Now

Firebase grew into a core Google Cloud product used by millions of apps, an example of a developer tool that survived an acquisition intact.

Why this matters now

Like Turso, Firebase was a developer platform acquired to slot into a larger cloud ecosystem while keeping its own product and community.

January 2008

Sun Microsystems acquires MySQL AB (2008)

Sun Microsystems acquired MySQL AB, maker of the open-source MySQL database, for about $1 billion. MySQL was the most popular open-source database and a pillar of the LAMP web stack.

Then

A year later, Sun itself agreed to be acquired by Oracle. MySQL's future under Oracle alarmed parts of the open-source community.

Now

Concern over Oracle's stewardship helped spawn MariaDB, a fork led by MySQL founder Monty Widenius, which spread widely.

Why this matters now

Shows how an open-source database acquisition can shift product trajectories and even spawn forks, a possibility for SQLite under Supabase, which committed to keeping Turso's engine open source.

Sources

(7)