All articles
Tools2 min read

Neon, Supabase or PlanetScale: which PostgreSQL for a SaaS that is starting

Three hosted databases, three different promises. The short version of my comparison, and how to choose without a benchmark.

by Vidhal Elame

Several of my products stand on PostgreSQL. So the question is not "which database" but "hosted by whom". I compared three services in a full article on Le Dev Augmenté. Here is what to keep from it.

The verdict in one sentence

Neon for a SaaS that is starting and wants a database that switches off when nobody uses it. Supabase for a complete backend, ready to use. PlanetScale for those coming from MySQL or aiming at very large scale.

Three different promises

These three services do not sell the same thing, which makes the choice simpler than it looks.

  • Neon sells a serverless database. Compute stops after five minutes without activity, and you only pay for what runs. Its free tier covers 100 projects, with 1 GB of storage each. Its "branches" copy the production database to test a migration safely.
  • Supabase sells a whole backend. The database, but also authentication, file storage, realtime and functions. The free tier covers 2 active projects and 500 MB; the paid plan starts at $25 a month.
  • PlanetScale sells scale. No free tier, an entry price of $5 a month, and a service built for teams that already have volume.

Prices noted on 6 November 2026 from the official pages, in US dollars before tax.

Choosing without a benchmark

I did not rank these services on a speed test. A latency figure measured one day, from one place, is worth nothing six months later. I compared what can be checked: public prices, limits, branches, the billing model.

For a project that is starting, three questions are enough.

  1. Does my project sleep at night? If so, a database that switches itself off divides the bill.
  2. Do I already have authentication and file storage? If not, Supabase saves assembling five services.
  3. Do I need a copy of production to test on? Branches change how you run a migration.

What I take from it

The trap with an all-in-one backend is that you use every piece of it. The day you want to leave, you must replace everything at once: the database, the authentication, the files. A database alone moves much more easily, because PostgreSQL stays PostgreSQL everywhere.

That is also why I keep my user accounts in my own database: the less a service knows about my product, the freer I am to change.

Read the full comparison

The full table, with the limits of each offer and the sources, is on Le Dev Augmenté (in French): Neon, Supabase ou PlanetScale : quelle base PostgreSQL en 2026 ?