What’s the ideal use case for Supabase? It seems oriented towards “serverless” apps given the mentions of edge functions, but does it fit in as a component of an app with a more traditional back end?
We provide additional tools that make it easy to use/connect to the database (PostgREST, pgbouncer, etc), but these are completely optional
Did you port the libraries to TypeScript? Or is the enteprise/managed cloud hosted infrastructure reliant on Go for internal things not available on the self hosted option?
Supabase Auth uses GoTrue, which is a Go server. It's all open-source, so you can self host it as much as you want.
You can see how it fits into the full Supabase Architecture here: https://supabase.com/docs/guides/getting-started/architectur...
There are already great platforms out there (e.g. Netlify and Vercel), whereas there are still a lot of unsolved problems in the database/postgres space. We're focusing on database problems first-and-foremost and the backlog hasn't shrunk enough to even think about website hosting.
I believe the unfortunate situation with Push Notifications for Android is that you still need to sign up for Firebase project (because you need a Google/Firebase Server API Key).
Link to code example https://github.com/OneSignalDevelopers/onesignal-supabase-sa...
If you need it sooner feel free to reach out, my contact details are in my profile.
In case it's not clear - MFA is Multi Factor Authentication, and this one is for you, the developer, to use within your own apps
The neat thing about this one is that it flows all the way through to the JWT so that you can use it in a Postgres Row Level Security Policy:
You can see the `aal`, which is "Authenticator Assurance Level". This is aal1 for "no MFA", aal2 is 2 factor auth, etc...A few of the team will be here to answer questions