PlanetScale as Supabase Graduation Path

This reveals that Supabase wins the first week of app building, but not necessarily the next two years of scaling. Supabase bundles Postgres, auth, storage, and functions so a small team can launch in minutes. PlanetScale competes by selling only the hard database layer, which matters later when traffic grows, schema changes get risky, and companies want more control over uptime, sharding, and compliance. Convex then sits one layer up, using database infrastructure underneath while competing for the developer relationship.

• PlanetScale is the clean graduation path because it strips away the bundled backend and focuses on the database itself. Developers still connect with standard drivers, but get branching, online schema changes, horizontal scaling, and optional deployment in their own cloud account.
  3 sacra
• Convex competes with Supabase on developer experience, not raw database depth. It gives frontend developers a reactive backend where UI updates automatically when data changes. But its stack can still rely on third party database infrastructure below, so PlanetScale can profit even when Supabase loses the app layer.
  4 sacra 5 sacra
• The scaling risk is real because some serious teams already view Supabase as a fast starting point rather than a forever home. Interview evidence shows larger or regulated teams often prefer Aurora or self managed Postgres once infra engineers, compliance needs, and migration concerns become central.
  1 sacra 2 sacra

Going forward, the market is likely to split in two. Bundled backends like Supabase and Convex will keep winning new builders, while specialists like PlanetScale capture the workloads that become larger, more regulated, or more performance sensitive. The biggest prize is owning the handoff between those two stages, because that is where the highest value database revenue sits.