What happens when a connection pool saturates at 3am and you're reading a status page instead of a query plan is what decides a SaaS database. Neon's branching is something I would actually use, because you can point a migration at a copy of production data without a restore. Supabase gives you auth, storage, edge functions and a dashboard, so you are not stitching those together yourself. Prisma's pitch is that the client and the host are the same company, which is worth something right up until it isn't.