Coz I don't want to
And clerk's much more popular is it? I hear the supabase has way bigger community etc. And lot more GitHub stars. So would wanna pick something that tons of other people are also using. Tho seems they are both popular. But u reckon clerk has wider adoption in nextjs ecosystem does it?
Who make it easy?
Isn't supabase's frontend calling db directly through rls a bit of a vendor lock in. Your code will break if you ever change auth providers right? Standard 3 layer auth doesn't work that way I assume?
How does it compare to clerk purely for auth. Is their auth also equally low headache and fully managed?
Both. But pretty lean team. 2-3 devs max. No need to build anything rn but if there's ever a new project, understanding if it's the right call or not. The admin/editor/viewer thing seems like clerk has native support for. Also heard supabase supports 2 level architecture where frontend talks to db directly. Was thinking might be better to use supabase like a standard auth and verify token in backend so that it's easy to flip auth logic if ever needed. But does that kill the benefits u get from supabase?
At what arr(annual revenue) roughly would you say someone would be better off not using it. Or it doesn't matter and it works well for a 500m$ company too?
Is the flexibility loss really all that much? Or it is genuinely good. I am just asking from curiosity. As I am not a pro at web dev and I have only used self managed dbs. Would genuine multi million $ businesses use them or it feels too restrictive?
Do you think it is genuinely helpful and serious mid level companies would consider using them?
What's your thoughts on it?
Is it convenience? What's the whole BAAS thing. I understand managed db and auth in same provider. But connecting them as same thing and frontend calling the db. And rls stuff. Row level security etc. I am not sure if that's genuinely useful or not. I rn have a auth provider and I verify and send the user access that they deserve based on their plan. And don't think it's all that complicated.