Devise vs Keratin AuthN: What are the differences?
What is Devise? Flexible authentication solution for Rails with Warden. Devise is a flexible authentication solution for Rails based on Warden.
What is Keratin AuthN? Accounts and Auth Microservice in Go. AuthN manages a database of user accounts with sign-in credentials and related attributes. Your application frontend relies on AuthN for creating accounts, logging in, forgotten passwords, and session maintenance.
Devise and Keratin AuthN belong to "User Management and Authentication" category of the tech stack.
Devise and Keratin AuthN are both open source tools. Devise with 20K GitHub stars and 4.76K forks on GitHub appears to be more popular than Keratin AuthN with 775 GitHub stars and 45 GitHub forks.
What is Devise?
What is Keratin AuthN?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Keratin AuthN?
What are the cons of using Devise?
What are the cons of using Keratin AuthN?
What companies use Keratin AuthN?
Sign up to get full access to all the companiesMake informed product decisions
We use OmniAuth with Devise to authenticate users via Twitter, GitHub, Bitbucket and Gitlab. Adding a new OmniAuth authentication provider is basically as easy as adding a new Ruby gem!
The only drawback I could see is that your OmniAuth+Devise
OmniauthCallbacksController redirection logic can easily get hairy over time. So you have to be vigilant to keep it in check.
Devise handles user registration with low effort. Also is configurable in so many levels, from custom views to create-your-own controllers.
4 years of experience using Devise for User management, authentication, and authorization.