11 ms·
Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative
Hi HN! We're Zai and Konsti, and we're building Stack Auth (https://stack-auth.com/ https://stack-auth.com/), an open-source managed authentication and authorization platform. Basically, we build your login and signup pages, and everything that comes with that.
Our GitHub repo is at https://github.com/stack-auth/stack https://github.com/stack-auth/stack, and there’s a zero-budget demo video here: https://www.youtube.com/watch?v=LTkjdPf2E2Q https://www.youtube.com/watch?v=LTkjdPf2E2Q
Stack Auth was born out of years of frustration with the incumbents. We wanted to build something that is developer-friendly and open-source at the same time.
The dominant player in this space is Auth0, who appeals to enterprises but lags behind in developer-friendliness and has strong vendor lock-in. A newer one is Clerk, which markets directly to devs, but is still entirely proprietary. Open-source solutions like Supabase Auth or Auth.js/NextAuth are only authN, and don't provide the rest of the toolchain.
On the other hand, building your own auth infrastructure is tedious work. Rolling your own crypto is already hard enough, but on top you'll have to deal with OAuth flows, access tokens, RBAC, permission syncing, API keys, and so on. Most handcrafted OAuth or password-based applications in the wild are vulnerable in at least some of these areas.
To us, the solution to this was obvious, so we decided to build it. Stack Auth is 100% open-source, licensed under MIT and AGPL. You can self-host, or choose to use our managed hosting. If you choose the latter, there's no lockin. You can export all your data and/or start self-hosting at any time.
Also, we're more than just authentication — we have authorization (orgs, teams, permissions, RBAC) and user management (impersonation, user dashboard, webhooks).
One interesting feature is what we call "connected accounts": we can manage and refresh your OAuth access tokens even for services that your users don't use for sign in, such as when accessing GMail or OneDrive APIs.
We also put a lot of weight into integrating deeply into the tech stack itself. For now, we support Next.js frontends with a bunch of components and hooks for sign-in, password reset, and organizations. Though, we do have a well-documented REST API (https://docs.stack-auth.com/rest-api/auth https://docs.stack-auth.com/rest-api/auth), so you can access Stack from any language.
For more info, check out our GitHub repo above, or our documentation (https://docs.stack-auth.com https://docs.stack-auth.com).
Would love to hear about your own stories and opinions on auth. Thanks all!
- floydnoel 2y agowow, I've been waiting for a project like this! Clerk seems fine, Auth0 is fine, but I'd rather build on open-source. Can't wait to start integrating this into my next project
- treve 2y agoAbsolutely wild how many of these there are now! I feel like I'm reading an announcement like this every few weeks.
- localfirst 2y agoI think its a sign of a bubble
- samstave 2y agoThere's been a lot of actually useful things in this bubble it seems. Ive been truly inspired how much little tool-age has been popping up. I feel like if you took a bunch of literally just that last month of show/launch/announce HN things one could wrap up a whole secure, scalable, promptable, fully formed stack thats just looking for some sort of content.
- localfirst 2y agowhen you see crowding in one segment its always indicative of a looming recession
- 5Qn8mNbc2FNCiVV 2y agoCurious, can you elaborate?
- telesilla 2y agoHow does this compare to Ory Kratos, also an open source option - https://www.ory.sh/comparisons/ory-versus-auth0/ https://www.ory.sh/comparisons/ory-versus-auth0/