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.

we integrated Gotrue with PostgREST at Supabase and it works beautifully together https://github.com/supabase/gotrue (forked from Netlify)

Broken how? Feel free to open an issue on http://GitHub.com/supabase/gotrue/issues

That's why PG has been adopted by Heroku early on, to the new Heroku-like render, and Supabase. They can offer a low or even free database plan because they can serve many users with a single PG instance.

Just a note to say every Supabase free tier deployment is a dedicated instance

Imo the hardest part is timing - meeting like minded people who are ready and available to start building now.

The best solution I’ve seen so far is https://joinef.com , they run programs in a bunch of major cities.

we wrote a bit about our launch week strategy here: https://supabase.com/blog/supabase-how-we-launch

We've tweaked it a bit since this post however based on the learnings from last time, we're actually running one next week - it will have more pre-recorded video content

https://twitter.com/supabase/status/1557437785815990272?s=21...

We offer 10 years exercise period for leavers at Supabase, hopefully it becomes the new norm

At Supabase we have tracked “Time to first query” from the start, which includes things like signing up, provisioning a database, creating a schema, adding supabase-js to your app, and querying your data for the first time

We generalised it over time to “time to value” for anything that isn’t onboarding/data-fetching

not to be a conspiracist, but are they still hosting wikileaks data? https://en.wikipedia.org/wiki/OVH#WikiLeaks

Hey everyone! We put a lot of work over the last few months into performance benchmarking. We're very keen for people to run the benchmarks themselves and report your results: https://github.com/supabase/benchmarks

Zero lock in is the killer feature for me

I also like that you can edit the wasp file and the app regenerates live in the local environment, feels super fluid

we provide a layer on top of postgres which includes: auto-generated CRUD apis that update as you change your schema, a realtime api so you can listen to all the changes happening in your database over websockets, and now an auth system to register users and control which data they have access to without having to write any middleware

what it boils down to is writing apis and connector code to your database can be a laborious process - we're automating that part away

client side auth is not in production yet - but is on the way, more details here: https://news.ycombinator.com/item?id=23320443

Thanks for the feedback! We've had a few people asking for on-prem + support, it's looking like it's going to be bumped up the feature queue.

Also thanks for sharing the android use case - we definitely want people to use this directly from the client. We're working hard to get the auth model right for this.

here's a list just for fun/chaos: https://todo-zeta.now.sh/?uuid=7e5217bf-7c76-4525-8783-21747...

here's something small I[supabase co-founder] built with supabase as an example: Realtime Collaborative Task Lists https://todo-zeta.now.sh/

in addition to @kiwicopple's response, you can also:

- use the js lib - https://supabase.io/docs/library/get

- use your RESTful and Realtime endpoints directly - e.g. <my-app>.supabase.co/rest/v1/users?select=first_name,age

- or even just connect to the db directly using your favorite SQL tools/ORM

I'll definitely regret this but here is a public one just for fun: https://todo-zeta.now.sh/?uuid=db9135e9-6749-4a04-b2e3-d0587...

Last week I witnessed a Yellow Vented Bulbul scolding a Female Asian Koel in a nearby tree and wondered what the relationship was, after looking into it it appears that the Koel is a "Brood Parasite" that lays it's eggs in the nests of other birds. The fascinating thing about the Koel in Singapore is that it usually lays it's eggs in the nests of crows, however as crows are considered pests here (and therefore their nests are destroyed on sight), it has adapted to laying in the nests of much smaller (non-pest) birds. It's interesting to see that the host parents still feed these much larger adopted children - as is photographed in the article.

A more in depth study is available here: https://www.jstor.org/stable/23034196?seq=1

the best thing about this was discovering https://git.sr.ht/

there was a great demo of this mating ritual in one of the royal institution's christmas lectures a few years ago, having trouble finding it on youtube

I find the UX patterns in the demo section pretty jarring. Having new pages animate in from off screen feels like it requires a fair amount of cognitive load to model the navigation hierarchy in your head (especially on a per application basis)

"Conflict of Interest Disclosures: Dr. van Dam received a research grant from the Nestec Company. No potential conflicts of interest relevant to this article were reported."

Guys, Nestec own the world's biggest coffee machine company, Nespresso.