Pomegra
Supabase raised $150M led by GIC and agreed to buy SQLite rival Turso for an undisclosed sum, four months after its $500M Series F in June 2026.
Key Takeaways
- Supabase raised $150M led by GIC, with CapitalG, IronArc and SquarePeg joining; no valuation was disclosed.
- The Turso purchase price is undisclosed; founder Glauber Costa becomes head of agentic services.
- About 70% of new Supabase databases are now created by AI agents or tools.
Lead
Supabase, the open-source Postgres platform, announced on October 2, 2026 that it raised $150M in new funding led by Singapore's sovereign wealth fund GIC. On the same day it agreed to acquire Turso, a startup that rebuilt SQLite in Rust for large fleets of small databases. The round arrives only four months after Supabase closed a $500M Series F, also led by GIC, so this is less a fresh bet on the company than a top-up on an existing one.
What Did Supabase Announce?
Supabase announced two linked deals: a $150M investment and the Turso acquisition. Alphabet's growth fund CapitalG, IronArc and SquarePeg joined GIC in the round. Neither the company nor its investors gave a valuation or labeled the round as a series.
The money has two stated uses. A portion goes to employee share sales, and the rest funds new features aimed at AI agents. Supabase also introduced Supabase Compute, hosted sandboxes for long-running agents, alongside the existing Postgres service, which includes authentication, automated backups, cron scheduling, embedding storage and an MCP server for agent access.
What Is the Valuation After the Series F?
The last disclosed mark is $10.5B post-money, set in the June 2026 Series F, which followed a $100M Series E at $5B in October 2025. That is a doubling in eight months. The new $150M is small beside the Series F, and its unlabeled structure suggests an extension to a recent round rather than a repricing.
The employee liquidity component matters for reading it. A company that lets staff sell shares four months after a $500M raise is managing retention at a valuation that has climbed quickly. It also signals that GIC wanted more exposure without waiting for the next priced round.
Why Did Supabase Buy Turso?
Supabase bought Turso to get a database engine built for agents that create databases by the million. Turso's approach lets one server manage millions of databases, loading each on demand and suspending it when idle. It supports embedding storage and page-level encryption. The core is free and open source, and revenue comes from a paid cloud version.
This is a strategic purchase, not an acquihire. Costa and the engine come together, and he moves into a leadership role at Supabase. Postgres is heavy for the throwaway, per-task databases that agents produce, and a lightweight SQLite-compatible option fills that gap without Supabase building one from scratch. The price was not disclosed, so the market cannot yet judge whether Supabase paid for revenue, code or time.
How Big Is the Agent Workload?
The agent workload is large enough to drive the company's growth numbers. Supabase reports more than 13M developers, up from roughly 10M in June, and about 4M new databases a month. Around 70% of new databases come from AI agents or tools, and database launches are up 600% year over year.
Chief executive Paul Copplestone framed the shift in the announcement. "Agents are spinning up millions of databases to power the prototypes, explorations, dashboards, and apps they're building," he said. These figures are company-reported, and a database created by an agent for a prototype is not equivalent to a paying production customer. Many of these instances may be abandoned within hours.
Competitive Context
Supabase now overlaps more directly with serverless database providers such as Neon and PlanetScale, as well as Firebase, MongoDB Atlas and AWS Aurora. Those rivals mostly center on a single engine. Offering Postgres for durable applications and a SQLite-based engine for disposable ones gives Supabase a two-tier pitch that hyperscalers have not matched natively. It also consolidates a corner of the open-source database market, where Turso was one of the better-known independent names.
What Comes Next?
Three things will determine whether the deal pays off. First, integration: Turso's engine has to work behind Supabase's existing authentication, APIs and tooling without fragmenting the developer experience. Second, monetization: free agent-created databases only matter if they convert to paid usage. Third, closing conditions and final terms, which were not disclosed.
If agent-generated databases keep growing at the reported pace, Supabase's infrastructure costs will rise faster than its paid base unless the lightweight engine lowers per-database costs. That is the case for the acquisition. If growth stalls or conversion stays low, a $10.5B valuation set in June will look stretched.
Outlook
Supabase has paired a modest cash injection with a targeted acquisition, using GIC's continued backing to extend from Postgres into agent-scale SQLite. The valuation, Turso's price and the closing timeline remain open. The next signal will be whether paid usage tracks the 13M developer base, and whether a further priced round follows the June Series F.
