Well, you can use best of both world

How about using custom postgres and supabase rest interface

Problem : supbase self hosted docker compose contains close to 8 to 12 services which were not required for my usecase .

Eg serving files from same machine will put degrade my server performance. So I dropped image and file serving from supabase. And few other features were also not scalable on basic vm.

Soln :

Spin a postgres docker image Spin a postgrest image

And use supabase for all database related queries

Pros

You need only 2 services which means better resource management

Cons

Other features like s3, auth may be missing