WillItSurvive
Data and analytics companies · subsidiary of Databricks · United States

Neon

Serverless Postgres database company, now a wholly owned Databricks subsidiary.

Defensible for now
Assessed 21 July 2026 · Evidence as of 21 July 2026
Real protection, with named pressure against it.
On the recordSince 21 July 2026 · Checkable from Summer 2026 · Every call on the record Checkpoint: Databricks' $188B strategic funding round, led by Coatue, closes
The call

Neon's database engine is safe inside Databricks' $188B war chest, but whether 'Neon' survives as a name distinct from Lakebase is still an open question.

Neon makes a type of database storage that automatically scales up and down based on how much work it has to do, which is useful for companies using AI to create lots of databases quickly. The technology is genuinely difficult to copy because it requires deep engineering work, but Neon's real problem is that its parent company Databricks built an identical product called Lakebase and is now selling both at the same time, which almost never happens in big tech companies. The one thing that could change everything: whether Databricks decides to keep Neon as its own brand or quietly merges it into Lakebase over the next six months, which would erase Neon as an independent product.

Why
01
AI pressure: None apparent. AI agents feed Neon rather than replace it: 80% of the 12M daily database launches on its platform come from agents, not humans. Could AI do the core job? Unlikely.
02
Bigger players: Databricks' own Lakebase product (same engine) plus Snowflake Postgres via its Crunchy Data purchase. Databricks now sells Lakebase on Neon's identical architecture, raising the odds Neon gets folded in or rebranded within 6 to 12 months. Could a giant copy it? Probably.
03
What protects it. Databricks needs Neon's storage engine to run Lakebase at 12M database launches a day, so the technology stays alive even if the brand does not.
What would change this call
Databricks rebrands or merges Neon into Lakebase within 6-12 months of the May 2025 close. Would show Neon's standalone brand and team were absorbed rather than kept distinct.
Neon headcount or leadership departures reported after the acquisition. Would indicate an acqui-hire wind-down pattern rather than sustained independent investment.
Snowflake Postgres or AWS/GCP ship scale-to-zero serverless Postgres features matching Neon's branch/copy-on-write model. Would show a hyperscaler or rival closing Neon's technical differentiation.
Key numbers
  • Databricks paid about $1B to acquire Neon (2025-05-14)
  • 12M Postgres databases started daily on Neon (2026-05-26)
  • 80% of new Neon databases created by AI agents (2025-05-14)
Named risks
  • Neon and Lakebase are architecturally identical, raising consolidation or rebrand risk within 6-12 months. Severity: high
  • Headcount flat-to-declining since June 2024 peak, consistent with acqui-hire absorption rather than growth. Severity: medium
  • Parent Databricks faces active copyright class-action (In re Mosaic LLM Litigation) filed March 2024. Severity: medium
  • Crowded competitive field: Supabase, Snowflake Postgres, PlanetScale, and hyperscalers pressuring differentiation. Severity: medium
Rivals, as read in July 2026
RivalDirectionEvidence
Databricks (Lakebase, parent)contestingLakebase, on Neon's engine, hit GA early 2026 and handles 12M launches/day as of 2026-06-16
Snowflakegaining onAcquired Crunchy Data for ~$250M on 2025-06-10, launched Snowflake Postgres
SupabasecontestingMost-cited direct head-to-head rival in serverless Postgres as of 2026
AWS/GCP/AzurecontestingHyperscalers slow but capable of replicating scale-to-zero Postgres features
PlanetScalecontestingEntered Postgres market in 2025 with dedicated-performance, no-scale-to-zero stance
Questions people ask
Is Neon still an independent company?
No. Databricks agreed to acquire Neon on May 14, 2025 for approximately $1 billion, and as of that date Neon became a wholly-owned Databricks subsidiary, marketed as 'Neon, a Databricks company.'
Is Neon profitable?
Neon does not publicly disclose audited revenue or profitability. Sacra estimated Neon's annualized recurring revenue at roughly $25 million around May 2025, but this is a third-party estimate, not a confirmed figure.
Could Neon get shut down or merged into Databricks' Lakebase?
Real risk exists: Lakebase runs on Neon's same storage engine, went GA in early 2026, and handles 12 million database launches per day, making Neon and Lakebase architecturally identical products inside one parent as of June 2026.
Could AI replace Neon's product?
Unlikely to replace it. Databricks reported on May 14, 2025 that roughly 80% of new databases on Neon are provisioned by AI coding agents, meaning AI agents are driving demand for Neon rather than displacing it.
Who is Neon's biggest competitor?
Supabase is the most-cited direct rival, alongside Snowflake, which acquired Crunchy Data for about $250 million in June 2025 to launch 'Snowflake Postgres', and hyperscalers AWS, GCP, and Azure.
Who owns Neon?
Databricks owns Neon outright since the acquisition announced May 14, 2025 for roughly $1 billion; Databricks itself signed a term sheet for a new funding round at a $188 billion valuation on July 20, 2026.
Timeline
  • 2026-07-20Databricks signs term sheet for strategic round at $188B valuation led by Coatue
  • 2026-06-26Neon ships private preview of backend platform: Functions, Object Storage, AI Gateway, Auth
  • 2026-06-16Databricks announces LTAP architecture; Lakebase (Neon-derived) hits GA, 12M launches/day
  • 2025-10Neon doubles free-plan compute allowance from 50 to 100 CU-hours/month
  • 2025-09Neon folds enterprise features (SOC2, HIPAA, SSO) into Scale plan free of extra charge
  • 2025-08Neon cuts compute costs 15-25% and storage price 80%, to $0.35/GB-month
  • 2025-06-10Snowflake acquires Crunchy Data for approximately $250 million
  • 2025-05-14Databricks agrees to acquire Neon for approximately $1 billion
  • 2024-04-15Neon reaches General Availability
  • 2023-08-02Neon closes $46 million Series B led by Menlo Ventures
Revision history
21 July 2026
First assessed. Defensible for now. The text above is fixed as of this date and is not edited afterwards.
In the same band
Sources