Supabase Buys Turso to Give Every AI Agent Its Own Database
Supabase announced $150 million in new funding led by GIC and the acquisition of Turso, a database platform that provisions cheap, isolated per-agent databases on demand. The company says 70 percent of the four million databases added to its platform each month are now created by agents or AI tools, and Turso founder Glauber Costa joins as head of agentic services.
On this page
One database per agent, provisioned like a container
Supabase, the company commercializing the open-source PostgreSQL database, announced $150 million in new funding on 2 October led by Singapore's sovereign wealth fund GIC, with CapitalG, IronArc, and SquarePeg participating, and used the moment to announce it is acquiring Turso. Turso's architecture matters more than the price, which was not disclosed: it provisions cheap, on-demand, isolated databases per agent, in public cloud or customer-managed environments, without dedicating a machine to each database. In other words, databases are starting to be allocated the way containers are, created for a task and discarded after it.
The deal logic is visible in Supabase's own usage numbers. The platform counts more than a million users and adds four million databases a month, and it says 70 percent of new databases are now created by agents or AI tools rather than people filling in forms. A workload profile like that, thousands of short-lived, unpredictable, individually tiny databases, breaks the assumptions of classic database hosting, which is exactly the gap Turso grew up in.
The numbers behind the deal
This is Supabase's second large round this year: the company raised $500 million at a $10.5 billion post-money valuation in June, following a $100 million Series E at a $5 billion valuation, and the new money includes employee liquidity. Chief executive Paul Copplestone called the past year the fastest growth in the company's history by a wide margin and said the future is agents, with Turso's architecture accelerating Supabase as the backend for that future. Turso founder Glauber Costa, whose stated goal has been to serve upwards of a billion databases to customers, joins as head of agentic services alongside co-founder Pekka Enberg, and the Turso platform keeps operating with a graduation path into Supabase for workloads that outgrow their sandboxes.
CapitalG's Derek Zanutto described Supabase as the critical open infrastructure layer powering the AI revolution, which is the kind of thing investors say, but the round's composition is notable for a company serving agents: much of Supabase's growth is downstream of agent adoption, not enterprise seat counts.
What per-agent databases change for developers
The interesting engineering shift is that isolation becomes cheap enough to be the default. When an agent gets its own database per task, cleanup, permissions, and failure recovery all become per-task operations: a compromised or misbehaving agent leaves behind a bounded, disposable artifact instead of sharing tables with everything else. That is the same instinct behind the agent-sandbox tooling that shipped across the industry this season, from NVIDIA's agent runtime guardrails to the per-session approvals desktop agents now request.
It also quietly changes data practice. Ephemeral per-agent databases make it easier to scope what an agent can read, to delete what it wrote, and to audit what happened, because the record is not interleaved with a production application's tables. Developers wiring agents into real systems should treat the database boundary as part of the agent's permission model: name the instance for the task, grant it the minimum schema, and let the lifecycle end when the task does. The companies selling agent infrastructure have decided this pattern is the future; the 70 percent number suggests their customers already agree.