Live data from Hacker News

Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

github.com

51–60 of 146 posts

Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

#51

A bit of a meta point, but Clerk must be doing really well if they're already positioned as the thing to make alternatives to.

Clerk has quite a few dark patterns in their free tier, eg: if your app is on Clerk free tier, all your users will be forced to log out and re-login every 7 days (and they try to obfuscate this fact until you're locked in). For this reason, I've recently had to migrate away from them - I'm really glad there are alternatives.

Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

#52
post #35

Would be interested to hear a comparison with keycloak.

Surprisingly your the only one who has mentioned Keycloak so far?! I switched several projects from Auth0 to it some time ago and didn't look back... particularly when they started tightening things since said projects were not even profitable.

Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

#54
post #51

A bit of a meta point, but Clerk must be doing really well if they're already positioned as the thing to make alternatives to.

Clerk has quite a few dark patterns in their free tier, eg: if your app is on Clerk free tier, all your users will be forced to log out and re-login every 7 days (and they try to obfuscate this fact until you're locked in). For this reason, I've recently had to migrate away from them - I'm really glad there are alternatives.

What did you migrate to instead?

Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

#55
how does this compare to Supabase Auth?

I want to be able to just put self-hosted Clark in front of my postgres DB

but I'm forced to use Supabase because of its Auth integration and I don't know what open source self-hosted Authentication/Authorization out of the box exists

Lucia-Auth v2 left me just confused state. It's frustrating that everything requires $$$/month

Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

#57

Do you guys only offer SAML in your hosted SaaS?

Everything is open-source.

We implement providers when a paying customer requests them (Team plan for OIDC-compatible providers, Growth plan for everything else, including SAML). Once we've implemented them, though, everyone benefits.

To our surprise, as of right now we haven't received any requests for SAML from our customers.

Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

#58

how does this compare to Supabase Auth? I want to be able to just put self-hosted Clark in front of my postgres DB but I'm forced to use Supabase because of its Auth integration and I don't know what open source self-hosted Authentication/Authorization out of the box exists Lucia-Auth v2 left me just confused state. It's frustrating that everything requires $$$/month

Supabase Auth is just authN, and it doesn't do authZ (organizations, permissions/RBAC) or user management (impersonation, user metadata, etc.). It also doesn't integrate as deeply into Next.js as we do.

I'm a big fan personally of Supabase-the-database; we've been building an integration so that you can combine RLS with all of our cool authZ features.

Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

#59
Regarding managed hosting - I don't see a mention of using your own custom domain anywhere. Did I miss it? Which tiers can use custom domains, if they are supported?

Also, do you support m2m tokens, ie. client credentials flow? What are the limits, if any?

Re: Launch HN: Stack Auth (YC S24) – An Open-Source Auth0/Clerk Alternative

#60
post #59

Regarding managed hosting - I don't see a mention of using your own custom domain anywhere. Did I miss it? Which tiers can use custom domains, if they are supported? Also, do you support m2m tokens, ie. client credentials flow? What are the limits, if any?

Our approach to sign-in pages is a bit different than Auth0's; instead of redirecting you to us, all of our components live on your very own website. The only time the browser will redirect to our domain is momentarily during the OAuth callback. We also don't brand our components, so your users may never even see that you use us for auth.
Post reply on HN