Hi HN! I am building Roled (https://roled.io), an open-source platform for centralized user & role management across multiple applications.

At several companies I've worked at, I noticed the same pattern: we built multiple products, and each needed users, roles, and permissions. Eventually we'd end up building some form of centralized backoffice or user management ourselves.

I started Roled because I wondered whether that could simply be infrastructure that we don't have to rebuild.

One design choice in Roled is that users aren't modeled around organizations. Instead, each project has its own users, roles, permissions, and authentication settings. This makes it possible to manage multiple independent applications from one place without requiring them to share the same user base.

It provides ready-to-use authentication flows such as sign-up, sign-in, password reset, email verification, and user invitations. The user-management APIs can also be used directly from your backend if you want to build your own flows. Applications integrate with Roled using OAuth2.

Roled is open source and can be self-hosted, or you can use the managed version at https://console.roled.io. The documentation is at https://docs.roled.io.

I'd really appreciate it if you gave it a try, and I am looking forward to any feedback on your experience!

I'm especially interested to know if any of you have a similar experience to mine. How did you solve it? Thanks!