I havent used either beyond hobby scale, but I’ve followed both for a while because my day job runs a very large Postgres deployment.
You can run both Neon and Supabase in your cloud account by self hosting. They may also offer on-prem managed deployment, I haven’t looked. I think anyone at large scale interested in using them will “colocate” them.
They have different capabilities over the incumbent cloud provider managed Postgres service.
Neon is very interesting for:
- scale up & scale out. Get more cores for your DB than the max incumbent single instance size.
- fast SSD cache in front of S3. Incumbent DB often uses glacially slow network block storage like EBS.
- branching and schema management wizardry
Supabase is “just” a vanilla Postgres instance plus a suite of extra services and tooling. In their case the collocated version can add the services around an incumbent cloud managed DB.
You can run both Neon and Supabase in your cloud account by self hosting. They may also offer on-prem managed deployment, I haven’t looked. I think anyone at large scale interested in using them will “colocate” them.
They have different capabilities over the incumbent cloud provider managed Postgres service.
Neon is very interesting for:
- scale up & scale out. Get more cores for your DB than the max incumbent single instance size.
- fast SSD cache in front of S3. Incumbent DB often uses glacially slow network block storage like EBS.
- branching and schema management wizardry
Supabase is “just” a vanilla Postgres instance plus a suite of extra services and tooling. In their case the collocated version can add the services around an incumbent cloud managed DB.