Supabase Raised $150M and Is Buying Turso. Should Neon and PlanetScale Users Pay Attention?
Supabase Turso acquisition came with a $150M round on 2 Oct 2026. Price and close date are undisclosed. Here is what it means for Neon and PlanetScale users.
On 2 October 2026, Supabase announced a $150M round led by GIC and said it is acquiring Turso, the SQLite-based database company. The $150M is the funding round, not the price of the deal: the purchase price and closing date have not been disclosed.
If you run on Neon or PlanetScale, nothing changes today. But the deal shows where the Postgres vendors think the next fight is: databases created in bulk by AI agents, not by people.
What exactly did Supabase announce?
Supabase announced two things on 2 October 2026: a $150M round and an agreement to acquire Turso. GIC led the round, and CapitalG, IronArc and SquarePeg participated. The release says the round also provides liquidity for employees, and that it came four months after a $500M Series F.
SyncGTM's weekly funding list logged the raise as a "growth round" on the same date and noted the Turso deal as a side item.
Supabase says about 70% of its new databases are now created by agents or AI-driven tools. That is a company-reported figure, and the announcements do not explain how users or databases are counted.
What is Turso, and why would Supabase buy it?
Turso is a database company built on SQLite. Supabase's post says Turso "rebuilt SQLite in Rust" and that its cloud platform lets one server manage millions of databases, loading them when needed and suspending them when not.
That is the opposite shape from Postgres, where one database usually serves a whole app. Turso's pitch is one small database per user, per agent or per task. Supabase's post names Superhuman, Sauna.ai, CTO.new and Mastra as Turso customers.
Glauber Costa, Turso's founder, becomes Head of Agentic Services at Supabase, alongside co-founder Pekka Enberg and the rest of the team.
What happens to Turso customers?
Turso says its platform keeps running. In a section titled "What this means for Turso users", Turso's announcement lists four points:
- Databases, APIs and workflows continue as they do today.
- Turso Database remains open source and actively developed.
- When SQLite is not enough, users can move to standard Postgres through Supabase, and to petabyte scale with Multigres.
- Deeper integration is expected "in the coming months".
Supabase's post says that for existing users, nothing changes. Neither post gives a price, closing date or any commitment on future Turso pricing or limits. Customers who need certainty on those points should ask for it in writing.
How do Turso, Supabase, Neon and PlanetScale prices compare?
They are priced on different units, so a single "cheapest" answer does not exist. The table shows entry-level paid pricing as listed on each vendor's page on 13 October 2026. Last checked: 13 October 2026.
| Turso | Supabase | Neon | PlanetScale | |
|---|---|---|---|---|
| Engine | SQLite | Postgres | Postgres | Postgres and Vitess (MySQL) |
| Free tier | $0, 100 databases, 5GB | $0, 500 MB database, 2 active projects | $0, 100 CU-hours per project, 1 GB per project | None listed on pricing page |
| Entry paid price | Developer $4.99/month | Pro from $25/month | Launch: pay for use, no monthly minimum | Single-node Postgres PS-5 $5/month |
| Pricing unit | Per plan, with overage per GB and per billion rows | Plan plus compute size | $0.106 per CU-hour, $0.35 per GB-month | Fixed instance price plus storage, backups, egress |
| Scale-to-zero | Idle databases cost only storage | Free projects pause after 1 week of inactivity | Yes, suspended compute costs $0 | Not listed |
Sources: Turso, Supabase, Neon, PlanetScale. Turso's page has a monthly and yearly toggle, and the displayed rates may be the yearly ones. Supabase's page carries no date.
What does Neon cost, and is it affected?
Neon is not directly affected. Its pricing page lists Free, Launch and Scale plans, and describes Neon as "from Databricks". Databricks announced its intent to acquire Neon on 14 May 2025, and its release said the same agent-driven pattern was already visible: over 80 percent of databases on Neon were created automatically by AI agents, per what the release calls "recent internal telemetry" (a company claim, with no method given).
As of 13 October 2026:
| Neon plan | Compute | Storage | Notes |
|---|---|---|---|
| Free | 100 CU-hours per project, up to 2 CU | 1 GB per project, 20 GB account total | Scale to zero after 5 minutes, cannot be turned off |
| Launch | $0.106 per CU-hour, up to 16 CU | $0.35 per GB-month | No monthly minimum, 10 branches per project included |
| Scale | $0.222 per CU-hour | $0.35 per GB-month | Uptime SLA, IP allow rules, Private Networking |
The takeaway for Neon users: your vendor was acquired by a data platform in 2025, and the same pattern of a larger company buying a database specialist has now repeated at Supabase. If you valued Neon for being independent, that point was settled last year.
What does PlanetScale cost, and is it affected?
PlanetScale is also not directly affected. It sells Postgres and Vitess on fixed instance prices rather than usage metering. On its pricing page (AWS us-east-1, as of 13 October 2026), single-node Postgres starts at $5 per month for a PS-5, and a three-node high-availability PS-5 is $15 per month on arm64.
| PlanetScale Postgres | Nodes | Price per month (arm64) |
|---|---|---|
| PS-5, non-HA | 1 | $5 |
| PS-5, HA | 3 | $15 |
| PS-80, HA | 3 | $148 |
| PS-160, HA | 3 | $286 |
| Metal M-10, 10 GiB, HA | 3 | $50 |
Storage beyond the included volume, backups, egress and optional PgBouncer are billed separately, and the page does not list those rates. The page lists no free tier.
PlanetScale competes with Supabase mainly as a place to run production Postgres, and nothing in the Supabase announcements changes that comparison.
Should Neon and PlanetScale users do anything?
No, but there are two reasons to pay attention. First, the competitive framing is shifting from "managed Postgres" to "a database per agent". Supabase and Neon both make the same claim: most new databases are created by software. Each of those numbers is the vendor's own.
Second, if your workload creates many small, short-lived databases, Turso's per-database model may cost less than Postgres compute billed by the hour. That is a question to test with your own usage, not a conclusion the sources support.
If you are a Supabase customer, the sources do not describe any product change. The Turso route to Postgres and Multigres is described as a path, with integration expected later.
Teams weighing a database for an agent product might also read our look at how Databricks and Snowflake are being challenged on agent tooling, since Databricks now owns Neon.
What's still unclear?
Several points remain open as of 13 October 2026:
- Deal terms and status. Neither company has published a price, a closing date or closing conditions. The Supabase post says it "is acquiring" Turso.
- Turso pricing. Neither company has said whether Turso plans, limits or prices will change.
- Open source. Turso says Turso Database stays open source. Supabase's post refers only to a shared commitment to open source and gives no licensing terms.
- The 70% figure. It is Supabase's own number and the definition of "created by agents" is not given.
- Weakest point of the thesis. A SQLite-per-agent database and a Postgres platform are different products. Whether one backend can serve both is Supabase's stated goal, not something shown yet. The Turso post says integration will come "in the coming months".
Frequently asked questions
How much did Supabase pay for Turso?
The price has not been disclosed. The $150M figure is a separate funding round led by GIC, announced the same day, 2 October 2026. Supabase's blog post, Turso's own announcement and press coverage all omit deal terms and a closing date, so treat the purchase price as unknown.
Will Turso prices or plans change after the Supabase deal?
Neither company has said. Turso's announcement says Turso keeps running and existing databases, APIs and workflows continue as they do today. It makes no commitment on future pricing or limits. Turso's pricing page, checked 13 October 2026, lists a $4.99 per month Developer plan.
Do Neon users need to do anything because of the Supabase and Turso deal?
No action is required. Neon is Postgres and is now sold by Databricks, while Turso is SQLite-based. Nothing in the announcements changes Neon's product or pricing. The deal matters mainly as a signal about how vendors are pitching databases for AI agents.
Is PlanetScale affected by Supabase buying Turso?
Not directly. PlanetScale sells Postgres and Vitess (MySQL) on fixed instance prices, from $5 per month for a single-node Postgres PS-5 as of 13 October 2026. The deal is relevant only if you compare PlanetScale with Supabase as a Postgres host.
Is Turso still open source after the acquisition?
Turso's announcement says Turso Database remains open source and actively developed. That is a statement from the company being acquired, and it does not set out licensing terms or a roadmap. Supabase's own post only refers to a shared commitment to open source.
Sources
- Supabase is acquiring Turso, Supabase (2026-10-02)
- Turso is joining Supabase to give every agent its own database, Turso (2026-10-02)
- Supabase Announces $150M in New Funding and Turso Acquisition, PR Newswire (2026-10-02)
- Supabase Raises $150 Million And Acquires Turso To Expand Agentic Database Infrastructure, Pulse 2.0 (2026-10-02)
- Top Funded Startups This Week: October 2026, Week 1, SyncGTM (2026-10-04)
- Neon Pricing, Neon (2026-10-13)
- PlanetScale Pricing, PlanetScale (2026-10-13)
- Turso Pricing, Turso (2026-10-13)
- Supabase Pricing, Supabase (2026-10-13)
- Databricks Agrees to Acquire Neon to Deliver Serverless Postgres for Developers + AI Agents, Databricks (2025-05-14)