> So I have to ask, with software coming out of things like Zanzibar and open source implementations around it - why did you decide to build the same thing again, instead of collaborating with one of these projects?

Supertokens is not a recent project.

Previously:

Launch HN: Securely manage tokens (Aug 2020), https://news.ycombinator.com/item?id=24306572

Show HN: Stripe for Auth (Dec 2020), https://news.ycombinator.com/item?id=25458033

Auth0 alternative (Aug 2021), https://news.ycombinator.com/item?id=26880554

> But the problem is, permissions are actually a representation of business processes snd communication structures. They are rarely user <-> role <-> permissions (I wish they were!).

UMA2 is available in Keycloak. Known as Authorization Services. I have written about it in the past: https://gruchalski.com/posts/2020-09-05-introduction-to-keyc....

But the problem is, permissions are actually a representation of business processes snd communication structures. They are rarely user <-> role <-> permissions (I wish they were!).

Thats true.

For us this was about coupling authorization with an authentication system so that developers could have both with a single product.

Ory Keto is in Go. Maybe they wanted an alternative available in Java perhaps?