Neon Challenges PlanetScale with Serverless Postgres

Neon matters because it turned PlanetScale’s best developer idea, database branching, into a Postgres native serverless product at the moment Postgres became the default choice for new app backends. In practice, that means a developer can spin up a database for every preview deploy or AI generated app, pay mostly when it is active, and keep the familiar Postgres ecosystem instead of adopting MySQL or managing infrastructure.

• The product overlap is concrete. PlanetScale lets teams branch a production database, test schema changes, and merge them back with deploy requests and non blocking schema changes. Neon offers the same branch per workflow for Postgres, but adds compute that suspends when idle because storage and compute are split apart.
  1 sacra 2 sacra
• The pricing overlap is also direct. Both companies use usage based pricing, but Neon’s architecture makes true pay per use easier to feel at the developer level. Neon moved to fully usage based pricing in August 2024, charges by compute and storage, and reported $25M ARR in May 2025 as that model scaled with high volume database creation.
  1 sacra 2 sacra
• This is part of a broader shift in who controls the app database layer. PlanetScale stayed focused on being the reliable standalone database, while Neon became a natural fit for Postgres centric AI and backend platforms. Databricks buying Neon for about $1B in May 2025 shows that this layer is strategic, not just a developer convenience feature.
  1 sacra 3 sacra 4 sacra

Going forward, competition centers less on raw database performance and more on owning the default workflow where apps get created automatically, previewed, deployed, and scaled. PlanetScale’s move into native Postgres expands its room to compete, but Neon proved that serverless Postgres with branching can become a distribution wedge into the next generation of app development.