We got an immediate response by a very motivated sales person who insisted to be connected with management and refused to put us in touch with anybody technical. It was a pretty off-putting experience, because it basically presumed that our eng team wasn't the decision maker (it was). I know a lot of companies throw their sales people at you, wanting to get in touch with somebody higher in the org chart, but it's still a pretty insulting experience for a tech-driven organization.
Needless to say we went with something else (not Auth0 either) and have been very happy.
I work at an auth company as well, Stytch, and this is something that we treat as obvious but we've seen a lot of reports like yours. Auth is such critical infrastructure, it is always going to come down to the technical team in the end.
I was confused about that for a while.
Ex:
Login & Authentication -> Kratos
Permissions & Access Control -> Keto.
You could take some cues from Grafana here.
Similarly to Ory, their product is backed by OSS.
Their frontpage’s navigation bar makes it clear which is backed by which.
I was also confused what a network has to do with auth. Is this some kind of distributed auth product? Who knows.
Also, I don't think anyone looking at a saas auth product would consider rolling their own. Presumably they're on your site because they aren't interested in that.
So I just didn't know what your value proposition is.
LE: I guess it's being tracked in this GitHub issue: https://github.com/ory/kratos/issues/274
not sure if that is everything.
It makes cost much lower and more consistent.
I would have thought the opposite given that they'd be charging per user per day as opposed to an all you can eat in a given month for a single user.
I do run Keycloak in a container but I'm pretty sure spinning up a new instance for every realm would be more resource intensive than using multiple realms in the same instance.
It's just a question of use case at the end of the day. In my use case I only need this for small internal tools so it's easier to just spin up one instance for me.
Seems like it's 1 extra click to disallow compared to allow, so yeah, non-compliant. Should be exactly as easy to say yes as saying no. In this case it's not.
Not at all. My point was that they are not offering that as product.
The banner should have a Reject All option, preferably as default action.
Also relevant: https://noyb.eu/en/where-did-all-reject-buttons-come
https://www.ory.sh/comparisons/ory-vs-keycloak/
the chart may be hidden "below the fold," so scroll down.
I gave up previously because having the user create button "above the fold" implied that an account was needed to view the comparison. SMH.
Do I trust them to be as diligent in their product?
And yeah, what gives GDPR bad rep is exactly these kinds of dark patterns and other forms of malicious compliance by non-caring companies.