awalias

(I'm on the supabase team)

I'd also like to offer some corrections to the linked post:

- Supabase is SOC2 type 2 and HIPAA compliant (https://supabase.com/security)

- Supabase works with all the same Postgres tooling that neon does (dbeaver, PgHero, PgAdmin, etc.)

- Supabase also offers integrations with Auth0, Clerk, and Okta etc.

- Supabase does offer verify-full SSL mode

- Supabase encrypts data in transit and at rest

- Supabase does offer pg_stat_statements and additionally the newer pg_stat_monitor

And I just want to call out that this author works for neon (self-proclaimed: https://www.reddit.com/r/SideProject/comments/1dy2r8b/commen...)

Probably poor word choice from me but when I reference superior distribution I'm assuming 'value-capture'.

This is true! Supabase db after all is "just" Postgres. In fact it's one of our product principles to adopt existing open source projects before writing our own.

You're also correct on the second bit, everything in the stack is MIT, apache2, postgres licensed so it would have been ok to run a closed fork if we'd have been that way inclined.

Maybe I should have addressed this one more directly in the post.

>Your users can just host their own version instead of paying you.

The main value in Supabase (the hosted service) is we do the hosting, maintenance, monitoring, compliance, security etc. which otherwise requires (expensive) in-house expertise.

This should be enough without needing to resort to deliberately leaving out features, and I think this generalizes to other products as well (sentry, plausible, the-open-source-strava-alternative, etc.)

Great point! I should probably add that to the article. In our case (Supabase) we have indeed spent the last few years working on compliance (SOC2, HIPAA, GDPR etc.) in order to meet these requirements so your comment here is on point.

>It's really hard to make any money

Open sourcing your code doesn't necessarily mean that you're giving your product away for free.

The value in a lot of businesses (most?) is in the distribution and my core argument in the post is that being open source actually gives you an edge here, especially in markets where your competitors are unwilling to take this approach.

I wrote a bit about why we’ll stay remote at Supabase (https://supabase.com/blog/why-supabase-remote), there’s plenty of drivers both on the company side and on the employee side.