Supabase announced on October 2, 2026 that it is acquiring Turso, the company behind a Rust rewrite of SQLite and a cloud service built to run very large numbers of small databases. As of November 7, neither company has disclosed a price or a closing date, Turso Cloud is running and shipping as before, no pricing change has been announced, and Supabase is building a SQLite-based product called Spark on top of Turso’s work.

On the same day Supabase said it had raised $150 million in new funding led by GIC, with CapitalG, Alphabet’s independent growth fund, as well as IronArc and SquarePeg participating. The deal was announced in three places: Supabase’s blog post, Turso’s blog post and a press release covering the funding.

Where the deal stands on November 7

  • Price and closing date: still not disclosed. Supabase’s post still says it “is acquiring” Turso, and neither company has published closing conditions or a completion notice.
  • Turso Cloud: still operating under its own name. Since the announcement Turso has listed itself in the Cursor Marketplace (October 8), added Singapore and Frankfurt (November 4, bringing Turso Cloud to 12 AWS regions) and published new engineering work on change data capture (November 5).
  • Pricing: neither company has announced a change. Turso’s pricing page lists a free plan with 100 databases, 5 GB of storage, 500 million rows read and 10 million rows written a month, and paid plans from $4.99 a month on yearly billing with unlimited databases.
  • Spark: a Supabase job listing for the Spark team describes it as “a lightweight implementation of Supabase written in Rust” that runs on an embedded SQLite-based engine with a Postgres-compatible SQL layer, with APIs compatible with Supabase’s PostgREST and Auth so apps written against supabase-js “work as-is”, and an upgrade path to full Supabase. Supabase has not published a launch date or a price for it.

Supabase’s and Turso’s announcements, Turso’s blog and pricing page, and the Spark job listing were checked on November 7, 2026.

Why a Postgres company wants SQLite

Supabase is built around Postgres. Its reason for buying a SQLite company is the way AI coding tools now create databases. The press release says Supabase is adding more than one million users and four million databases a month, and that 70% of new databases are created by agents or AI-driven tools. Supabase’s post puts it as “over one million databases per week.”

Most of those databases are small. Supabase’s post argues that “agents should be able to create a database as easily as creating a file,” and that a small workload should not need a dedicated machine each time. Its split is plain: “SQLite is well suited to these small, on-demand workloads. Postgres is what you want as your application scales.”

Turso’s contribution is the infrastructure for the small end. According to Turso, it rewrote SQLite from the ground up as open source, removed the single-writer limit that held SQLite back on servers, and runs it on a diskless cloud service that stores the write-ahead log on S3. Supabase describes the result as a platform where a single server can manage millions of databases, “loading them when needed and suspending them when they’re not.” Customers can use it on Turso Cloud or in their own cloud accounts. Both companies name Superhuman, Sauna.ai and Mastra as users; Supabase also lists CTO.new.

Spark is where the two halves meet: the Supabase developer experience on a database small enough to hand to every prototype, with a move to full Postgres when an app grows.

What changes for Turso users

For now, both companies say nothing changes for existing customers. “For existing users, nothing changes,” Supabase writes; Turso will keep working on SQLite while Supabase continues with Postgres. Turso’s post lists four commitments:

  • the Turso platform keeps running, with existing databases, APIs and workflows unchanged;
  • Turso Database stays open source and actively developed;
  • applications that outgrow SQLite get a path into standard Postgres through Supabase, up to Multigres for very large deployments;
  • deeper integration between the two products is planned “in the coming months.”

The five weeks since the announcement match those words: new regions and features have shipped under the Turso name. What the posts still do not contain is any commitment about future Turso Cloud prices or limits, so today’s plans are a statement about today.

If you run production data on Turso, three checks cost little now:

  • export one database and confirm you can restore it elsewhere; our guide to testing an export before you migrate applies to databases as much as to notes apps;
  • note which plan limits you rely on (database count, rows written, point-in-time restore window) so you can spot a change when one is announced;
  • if you want the Supabase API on SQLite, wait for Spark’s published terms rather than planning around the job listing.

Turso founder Glauber Costa joins Supabase as Head of Agentic Services, together with co-founder Pekka Enberg and the rest of the Turso team.

The funding

The $150 million round comes four months after what the press release calls Supabase’s $500 million Series F; the new round is not given a series letter. It is a separate transaction from the Turso purchase, not its price. Supabase says the money will go into product work on databases created by agents and will also provide liquidity for employees. The company says more than 13 million developers use its platform. No valuation was announced.

For other 2026 rounds in AI, security and developer tools, see the tech funding tracker.