A statistic, then a purchase

Supabase announced on Friday that it has raised $150 million led by Singapore’s GIC, with Alphabet’s CapitalG, IronArc and SquarePeg participating, and that it is acquiring Turso, the company behind the SQLite fork libSQL. Terms of the acquisition were not disclosed.

The number underneath both announcements is the interesting one. Supabase says it now adds more than a million users and four million new databases a month, and that 70 per cent of those databases are created by agents or AI-driven tools rather than by a person clicking a button. In June the company reported a 600 per cent year-on-year increase in database creation, with agent-driven deployments already in the majority.

Why SQLite and Postgres both

Supabase is a Postgres company. Postgres is an excellent database and a slightly heavy one to spin up four million times a month for workloads that may last ninety seconds.

A laptop open on a desk with code on the screen
Seventy per cent of new databases are created by agents or AI tools, the company says. Illustrative photo. Daniil Komov · pexels · Pexels License

That is the gap the acquisition addresses. “Agents should be able to create a database as easily as creating a file, with just as little concern about cost,” Supabase chief executive Paul Copplestone wrote. “SQLite is well suited to these small, on-demand workloads. Postgres is what you want as your application scales.”

The stated plan is to route small agent tasks to Turso first and migrate them to Postgres as they grow. Supabase says existing users see no change: it continues building around Postgres, Turso continues on SQLite, and the products integrate gradually. Glauber Costa, Turso’s founder, will lead the agentic infrastructure effort at Supabase.

The shape of the market this implies

A database created by an agent is a different product from a database created by a developer. It is created without a human deciding it was worth the money, it may be abandoned minutes later, and there will be a great many of them. Provisioning cost, not query performance, becomes the thing the architecture is optimised around.

Stacked hard drives on a shelf
Turso will keep working on SQLite while Supabase continues on Postgres. Illustrative photo. Marta Branco · pexels · Pexels License

That is a reasonably specific bet, and it is being made with a specific amount of money. The round closes roughly four months after Supabase’s $500 million Series F in June, which is a short interval, and part of it provides liquidity to employees rather than funding operations.

CapitalG general partner Derek Zanutto said Supabase “has established itself as the critical open infrastructure layer powering the AI revolution” — an investor describing a company he has just put money into, and worth reading as such.

What to watch is whether the 70 per cent figure holds as agent-written code gets more selective about what it provisions. A number that high can mean agents genuinely need their own storage, or it can mean they are wasteful in a way that improves.