auth system that worked well with static file buckets would cut like 40% of backend DB / server needs
Only Logto and Hanko seem to offer sane "I can vouch [email protected] logged in, create a user and start their session in Django if you please" workflow that can beat vendor lockin.
It has
-an admin UI
- Supports (LDAP, SAML, OAUTH, social logins)
- MFA, Passkeys
- Application access based on user groups etc
Unfortunately, my project is not using jsx, so I can't really implement anything that relies on it. I would love to check this out, if I can use it without Next.js or any kind of jsx compatability. But, until then, it's not something useful for any of my use cases.
I have a question - what if I want to integrate Stack with React and NestJs app? I couldn't find any docs for a backend authentication.
will it adapt to PrimeReact
Any plans to create components for Flutter?
Or, honestly, why anyone would chose to use react server components at all.
I was just kicking the tires on cal.com and saw the same thing - they did all their stuff with the react server components and next.js. And then? Well, it turns out that they needed an API, because apps do.
So they ended up reimplementing most of the logic in a RESTful API anyway.
I just SMH.
On a more useful note... I kind of wonder what the target audience for this is. Big companies? Dont want to roll their own auth. Startups? Dont want to roll their own auth...
> That's why we built Stack.
I’m not convinced this is a strong USP. One could make a decent argument “Stack” doesn’t have “all” the features (yet) - I’ve seen the roadmap.
Firebase, Superbase etc. arguably have more features.
In a nutshell, I think it might be better to have that paragraph really drive home the USP of the product e.g., open source accountability, fairer pricing model etc.
Those are strong tells, instead of the “all the features” narrative. That’s a hard battle to win :)
Regardless, awesome work! And congrats on the launch