Build · founder · 6 min read

Supabase Bought Turso Because Your AI Agent Keeps Creating Databases

Supabase raised $150M, acquired Turso and previewed Supabase Compute. What it means for the backend your Lovable or Bolt app quietly runs on.

Published October 7, 2026 ·

supabase turso backend funding ai-agents database

On October 2, Supabase announced three things at once: a $150 million raise led by GIC with CapitalG, IronArc and SquarePeg, the acquisition of database company Turso, and an early look at a product called Supabase Compute. No valuation was disclosed, and no price for Turso.

That sounds like a pile of infrastructure news. It’s actually one story, and it affects how your vibe-coded app is built.

The number that explains the deal

Supabase says it is adding more than one million users and several million databases every month, and that roughly 70% of new databases are created by agents or AI tools rather than by a person clicking “new project.” Co-founder Paul Copplestone put it plainly: agents are spinning up millions of databases for prototypes, explorations, dashboards and apps.

If you’ve built anything in Lovable, Bolt or Claude Code, you’ve been one of those humans delegating the decision. You described an app, and a database appeared. You probably never chose it.

We covered the earlier $10.5B raise in Supabase Just Hit $10.5B. This round is smaller, but it tells you where the company thinks the next wave of demand comes from: software, not people.

What Turso brings

Turso is a SQLite-based database platform built so that one server can hold millions of tiny databases, loading each when needed and suspending it when idle. Think of it as the difference between renting a warehouse and renting a locker. Postgres, which Supabase is built on, is the warehouse: powerful, shared, and priced accordingly. SQLite-style databases are lockers: cheap, instant, and disposable.

That matters for agents. An agent testing an idea doesn’t need a full Postgres project. It needs a scratch space it can create in milliseconds and throw away. Turso’s existing customers include Superhuman and Mastra, and its founder Glauber Costa is joining Supabase to lead its agentic services work.

Supabase says Turso will keep operating as its own product, with a path into the wider Supabase platform as projects grow. It hasn’t said whether the deal has closed, or spelled out what happens to Turso’s open source projects. Watch for that.

What Supabase Compute is (and isn’t, yet)

Supabase Compute is a managed service for running code next to your database: short-lived sandboxes for untrusted or agent-written code, and always-on backend services. It scales to zero when idle and supports Node, Deno or your own Docker containers. Use cases listed include agent sandboxes, long-running agent sessions, background jobs and hosting MCP servers.

Two caveats. It is in private alpha behind a waitlist, and no pricing has been published. Today’s Edge Functions keep working unchanged. Nothing about this changes what you build this week.

What to do about it

You don’t need to act, but you should be a little more informed than you were.

Know which backend you’re on. Open your builder’s settings and find out whether your project uses Supabase, and under whose account. If an AI tool created it, the database may sit in an organization you didn’t set up deliberately.

Count your projects. Agents don’t clean up after themselves. If you’ve run a dozen experiments, you may have a dozen live databases, some holding test data that looks a lot like real customer data. Delete what you don’t use.

Check row-level security. This is the setting that decides who can read which rows. Generated apps have shipped with it off before, which is the root of several exposure stories we’ve covered. See Vibe Coding Security Guide.

Don’t build on the alpha. Compute is interesting. Plan around products you can buy today.

The honest read

This is infrastructure companies chasing the same customer everyone else is: the AI agent that builds on a founder’s behalf. Supabase is smart to do it, and consolidating the “cheap scratch database” category into the same company that runs your production Postgres is a sensible bet.

But notice who benefits first. Supabase gets more databases created. You get a faster path from prompt to prototype, and a larger pile of things you’re responsible for. The tools are making infrastructure decisions for you at a rate that outpaces your ability to review them.

The takeaway isn’t to avoid agents. It’s to treat the backend as a thing you own, even when you didn’t pick it.