From Dev.to
One Supabase Project per Customer: Apply a Template, Catch Hand-Made Changes With a Schema Fingerprint, Hand Over, and Split the Costs
If you give every customer their own Supabase project, the hard part is not creating them. It is keeping them the same, knowing who owns each one, and handing one over. I tried the first two on two fr...