ZITADEL Cloud — A turnkey user and access management that works for you and supports multi-tenant (B2B) use cases. Free for up to 25,000 authenticated requests, with all security features (no paywall for OTP, Passwordless, Policies, and so on). - Source: dev.to / 4 months ago

Indeed. It is a bit misleading. ZITADEL(https://zitadel.com/), for example, pretty much checks all the boxes. - Source: Hacker News / 8 months ago

Try out this simple web app with a ReactJS frontend and a Python API backend, and add a layer of security with ZITADEL, an open source and free identity provider. See how user login and authentication, and then accessing a protected API take place:. Source: 12 months ago

When I was building a website and companion app, I researched a lot of the open-source options for auth. My primary requirement was ease of setup and operation. I didn't want to mess around with JVM dependencies and 100% didn't want to start messing around with k8s for such a small project. I was also very intimidated by the ORY stack. I didn't know how all the pieces fit together. And to self-host you pretty much... - Source: Hacker News / 12 months ago

Https://zitadel.com/ Simplify Your SaaS: Multi-Tenancy and Delegated Access Management with ZITADEL Organizations https://www.youtube.com/watch?v=Cx_WgyY4TOo ZITADEL Roadmap. - Source: Hacker News / 12 months ago

IMHO the stateful opaque token approach is simple enough that it can (and often does) get baked into whatever language/framework you’re using to write your app. In addition, the very nature of session tokens is such that the logic for what the token actually means/represents lives in your app, on the server. So, that may be why we don’t see more “opaque session token” standards/libraries out there as an... - Source: Hacker News / 18 days ago

Users can signup and login via the Devise gem and create their organizations. - Source: dev.to / about 1 month ago

However for smaller apps it might be an overkill. In "real-life" production systems, overengineering is one of the biggest crimes. This is true any framework and technology, so in Rails you might want to use Rodauth since it is big and interesting and challenging, but then again, if you are building a simple greenfield MVP you do not have the time or need, for a big, complex solution. In those cases Rails... - Source: dev.to / about 1 month ago

Since Rails 7, there's more and more tooling that enables us, developers, to roll our own authentication. Devise is great and has been an amazing companion over the years. It also has this neat little feature - an authenticated route constraint which "hides" certain routes from people that are not signed in. - Source: dev.to / about 2 months ago

As much as this article is about user authorization, there's something important we need to cover: user authentication. Without it, any authorization policies we try to define later on will be useless. But there is no need to write authentication from scratch. Let's use Devise. - Source: dev.to / 8 months ago