What does dual licensing AGPL/MIT do? Isn’t the MIT license more permissive in all cases?
Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
31–40 of 146 posts
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#32Auth doesnt need a new service/company. It needs an ai chatbot that walks engineers through adding auth to their project. Its the developer experience that is the problem
You might like what we built then — we have a setup wizard that adds auth to your Next.js project for you, including creating all the necessary pages, handlers, and config ;) npx @stackframe/init-stack@latest
Alright sir! I may have a look with my current nextjs project.
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#33What does dual licensing AGPL/MIT do? Isn’t the MIT license more permissive in all cases?
Our clients are MIT, our servers are AGPL.
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#34This is really awesome. On almost every project I’ve worked on, I’ve never been able to trust and truly rely on proprietary services and companies to handle my authentication and authorization. I’ve been forced (i.e., it was already decided) to use Auth0 before and I hated every minute of it. Congratulations on launching Stack Auth and providing a better alternative!!!
This exact set of problems is precisely what we're trying to solve. Reading this feels like great validation :)
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#35Would be interested to hear a comparison with keycloak.
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#36This is great. Competition is definitely needed in the Authentication/Authorization space.
Quick question. How would this compare to supabase/gotrue [0] and permify [1]?
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#37A bit of a meta point, but Clerk must be doing really well if they're already positioned as the thing to make alternatives to.
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#38Looks nice, congratulations on the launch! I suspect the answer is "no" here, but can Stack be used as an OAuth provider itself? I think all I see in the documentation is using other OAuth providers for authentication.
In theory yes — actually, we already are an OAuth provider behind the scenes — though we haven't documented this anywhere yet. What would you use it for?
If I'm going to reach for a 3rd party auth provider like this, I want to be able to use it across all of my potential properties. For example a Discourse forum, or a Shopify store, etc.
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#39I think Clerk looks great but it starts to get quite expensive if MFA is a requirement. Do you have 2FA/MFA in your roadmap?
Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
#40This is great. Competition is definitely needed in the Authentication/Authorization space. Quick question. How would this compare to supabase/gotrue [0] and permify [1]? [0]: https://github.com/supabase/auth [1]: https://github.com/Permify/permify
Supabase Auth is only authentication; it doesn't do organizations, permissions/RBAC, impersonation, etc. We are working on some fancy Postgres connectors to let you use Stack Auth with the DB part of Supabase and RLS.
GoTrue and Permify are on a lower abstraction level than us; we connect the entire stack (from frontend to database), while GoTrue and Permify still require a lot of setup and manual integrations.