Supabase buys Turso: agents now make 70% of new databases

Supabase announced $150M in new funding and a deal to acquire Turso on October 2. The money is the headline. The number underneath it is the story: 70% of new Supabase databases are created by AI agents or coding tools, not by people. The database market is now being shaped by software that spins up a backend, uses it for an afternoon, and forgets it exists.

What actually happened

Per Supabase's press release and SiliconANGLE:

• $150M led by Singapore's GIC, with Alphabet's CapitalG, IronArc and SquarePeg. It lands four months after a $500M Series F
• Supabase says it adds over 1 million users and 4 million databases a month, and that database count was up 600% year over year as of June 2026
• Turso builds a SQLite-compatible database (it created the libSQL fork) designed so one server can hold huge numbers of small databases, load them on demand and suspend them when idle
• Turso founder Glauber Costa becomes Head of Agentic Services; co-founder Pekka Enberg and the team come along
• Price was not disclosed, and neither company said the deal has closed

Turso's own post says the service keeps running, the database stays open source, and SQLite users get a path into Postgres "when SQLite isn't enough." SiliconANGLE also reports a new Supabase Compute service for hosted, long-running agent sandboxes; Supabase's announcement does not detail it, so treat specifics as pending.

Why agent-created databases matter for your business

Count what your tools have created. If your team uses Lovable, Bolt, Cursor or Claude Code, some of your backends were provisioned by an agent. Each one has keys, a schema and maybe customer data. We wrote about 16,326 Supabase databases left readable because row-level security was off. Agent-made prototypes are where that happens.

Turso customers: nothing breaks today. The promise is continuity, with "deeper integration in the coming months." That phrasing usually means pricing and plan changes arrive later. Export a backup now and note your current plan terms.

The lock-in is in the extras, not Postgres. Supabase's core is standard Postgres, which you can move. Auth, storage, edge functions and now agent sandboxes are the sticky parts. Use them where they save real time, and keep your schema and business logic portable.

Sources: Supabase via PR Newswire, Turso, SiliconANGLE.