[wenbo]

> finding the building blocks of modern applications (database, auth, functions, presence, realtime subscriptions), making them easy to use, and then sharing the source code.

Great observation!

> I’ve learned a ton just from cruising around supabase GitHub.

Glad to hear it!

> Can you say which of these new components will be open sourced?

All of these components are open source and licensed under Apache License v2.0.

> There are some other features (e.g. function hooks) that are also closed-source at the moment.

I actually worked on the initial implementation of function hooks. We've actually already open sourced both the client (see: https://github.com/supabase/supabase/tree/88bcef911669595428...) and the pg_net extension it requires (see: https://github.com/supabase/pg_net). I think we've yet to open source the SQL commands needed to create the schema, functions, etc. I'll talk to my team and we'll open source it.

> Is Supabase heading for an “open core” model?

I don't think so. We want to continue to open source our projects under either MIT (client libs) and Apache License v2.0 (server libs).

[wenbo]

Wanted to follow up on this. I spoke to the team and just wanted to re-iterate that we will be open sourcing the SQL very soon.

[zaking17]

On the function hooks, that would be awesome. I was just implementing some of those SQL commands.

And I will look more at the realtime libraries to see the new stuff. Thanks for all the open code!!

[wenbo]

> I was just implementing some of those SQL commands.

Way to take the initiative! I think it was more of an oversight on our part than intentionally choosing to keep it closed.

> And I will look more at the realtime libraries to see the new stuff.

Awesome! We have a lot of updates and better documentation coming in the next couple of weeks so stay tuned.

> Thanks for all the open code!!

You're very welcome and it's the least we can do!