Supabase gives developers a backend built around open-source Postgres, while Turso uses SQLite to create large numbers of small, isolated databases on demand. Supabase announced $150 million in financing and an agreement to acquire Turso, pairing more capital with an architecture designed for software agents. GIC led the financing, with CapitalG, IronArc and SquarePeg participating.

A developer can use Supabase for the database, user authentication, file storage, real-time updates, edge functions and vector search instead of assembling those services separately. The business commercializes its open-source foundation with paid features: SiliconANGLE reports that those include login management, backups and scheduled database tasks.

Turso addresses smaller workloads. Its team rebuilt SQLite in Rust and designed a cloud platform that loads a database when needed and suspends it when idle; Supabase says one server can manage millions of them. An individual agent can therefore receive its own database without a dedicated machine for every short-lived task. SiliconANGLE reports that Turso keeps its core feature set free and charges for a managed cloud version.

Supabase plans to keep Turso operating while connecting it with the broader Supabase ecosystem. The intended progression is straightforward: SQLite handles small databases that must appear quickly, while Postgres supports applications as they grow. Supabase says it adds 4 million databases monthly and that agents or AI tools create 70% of them.

The company said the financing will support agent-focused database development and employee liquidity. It did not disclose the portion allocated to that liquidity, so the primary financing amount cannot be separated from the headline total. The announcement came four months after a $500 million Series F at a $10 billion pre-money valuation; Supabase disclosed neither a valuation for the latest financing nor the Turso purchase price.

Publication history

Published versions remain available when an article is updated or corrected.

  1. Revision 1 · Initial publication

    Initial publication