Live data from Hacker News

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

github.com

81–90 of 146 posts

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

#81
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.

Ehh I actually don’t think that’s that bad — they do have to run a business! What limitation would work better on the free tier?

This came up on Reddit and the founder responded directly there, seemed like they were going to add a tool tip or something to make it clearer.

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

#83
Congrats on the launch. What's your approach to security? I notice there's no mention of any penetration testing, no security policy, no responsible disclosure policy, no place to report security vulnerabilities.

You're absolutely right (in other comments) that getting the UX and so on right for authn/authz is really hard, and there are a ton of edge cases, but I know from experience that there are a ton of security edge cases too. Things like rotating session tokens at the right time, how that interacts with password resets, HTTP referrers, etc, is all quite tricky to get right. I've built with battle-hardened, decades-old frameworks and still gotten a few details wrong.

To delegate all of this responsibility to a third party product, even if it's open-source, rather than building it yourself, is to give up control. Sure you can edit the code, but can you find the bug in an unfamiliar codebase, effectively test in a testing environment your unfamiliar with, and create a valid build? That's a lot harder.

If I were to delegate that responsibility to a product like this, I'd want to know that they've taken security at least as seriously as I do, ideally much more seriously because it's the core of their product. Right now I'm not convinced.

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

#85

Congrats on the launch. What's your approach to security? I notice there's no mention of any penetration testing, no security policy, no responsible disclosure policy, no place to report security vulnerabilities. You're absolutely right (in other comments) that getting the UX and so on right for authn/authz is really hard, and there are a ton of edge cases, but I know from experience that there are a ton of security…

We added a security policy: https://github.com/stack-auth/stack/blob/dev/.github/SECURIT...

If it helps you, we delegate the most vulnerable parts of the application, such as OAuth, to lower-level frameworks — similar to the unmanaged auth libraries people use today. We are essentially a thick wrapper around those, to create a full-stack platform from primitives. (Of course, that doesn't mean the thick wrapper cannot be vulnerable, but it helps with some of the most hideous bugs.)

The point I disagree with is that building it yourself is better than delegating it to a third-party — at best, you can secure your auth against vulnerabilities you're aware of. Unfortunately, this fallacy keeps coming up, but generally it's the case that homebrew auth is not more secure than open-source libraries, nor is proprietary code.

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

#86
post #5

Absolutely wild how many of these there are now! I feel like I'm reading an announcement like this every few weeks.

I think its a sign of a bubble

There'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.

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

#88
post #80
post #74

Congrats on the launch. I have a golang backend, postgres db and a react app. I have added auth using email, password salting and saving in pg. It was about 1 day of work to implement all of this. I do not have OAuth or SAML however. Is that the differentiating factor, if I have to use your solution ? Is a basic auth setup such a complex thing to handroll ourselves ? I do not intend to be snide but genuinely curios a…

First, incorporating Stack into your project is really easy if you use Next.js — literally just a single command: npx @stackframe/init-stack@latest If you use our managed hosting, we'll deal with deployment, backup, ... for you. . Anyways, here are a few things that you'd have to build for yourself but come for free with Stack Auth: - Session management, because you probably don't want to store passwords in cookies,…

Nice list. You came well prepared.

    > Email shenanigans — for example, some mail clients click verification links automatically to check them for spam and then even interact with the page
What is the technical workaround for this issue? Do you check user agent?

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

#89

This 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 is a great HN anecdote. Can you share more about why Auth0 was frustrating? I would like to learn more.

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

#90
Hmm. Am I the only one who immediately jumps to the thought that any VC backed "open source" tool is just using open source as a cost of customer acquisition, and will soon find a way to pay-wall necessary features? The majority of the effort will be in the paid SaaS product, not the open source stuff.

Maybe I'm getting old and jaded, but that's not really the spirit of open source.

Post reply on HN