61–70 of 146 posts
Have you seen this? https://github.com/logto-io/logto How does it compare?
(For Logto specifically, I'm actually surprised by what they consider "enterprise" features — something like OIDC, 2FA or RBAC should not be gated behind a paywall, IMO.)
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.
Would be interested to hear a comparison with keycloak.
I keep repeating this comparison throughout this thread, but Stack is to Keycloak/Ory/etc. what Clerk is to Auth0.
Though, I regularly recommend Keycloak in sales calls when I talk to larger companies willing to invest time and effort into a custom IdP. We are not really looking to replace those use cases.
I think Clerk looks great but it starts to get quite expensive if MFA is a requirement. Do you have 2FA/MFA in your roadmap?
> Rolling your own crypto is already hard enough Wait, what? Do you role your crypto to handle standard auth flows? Is this some machine generated text?
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.
I notice you're mentioning: "We support Next.js frontends" and "Idiomatic Next.js APIs". What is it about your product that is NextJS specific? Can someone who has no interest in using NextJS still use your product?
Our backend and dashboard are language-agnostic, and you can access their REST API from anywhere. However, there is a Next.js SDK with server & client components, hooks, and functions that integrate very deeply into the framework — that one is Next.js-only. We also have a setup wizard, which installs Stack Auth into your project, which works only on Next.js apps with the app router. It's as simple as: npx @stackframe…
Earlier quoted context omitted.
Our clients are MIT, our servers are AGPL.
Just for clarification, So you can't really host this without open-sourcing my product (since your server is AGPL). Isn't it a stretch to call this really open-source? I compare this to something like a temporal which I can self-host without worrying (and which I believe is MIT license [ https://github.com/temporalio/temporal/blob/main/LICENSE ])