Devise vs Guardian: What are the differences?
Devise: Flexible authentication solution for Rails with Warden. Devise is a flexible authentication solution for Rails based on Warden; Guardian: Remove the OAuth dance with one request. Avoid dealing with OAuth logic in your code, and spend more time creating your product. Guardian reduces the OAuth footprint in your code to a single request. Built with modularity in mind, Guardian leverages plugins to handle OAuth flows, should you encounter a flow that Guardian doesn't handle, create a small flow plugin to do so and carry on. Guardian comes with 5 pre-made plugins that cover 99% of OAuth services.
Devise and Guardian can be categorized as "User Management and Authentication" tools.
Devise and Guardian are both open source tools. It seems that Devise with 20K GitHub stars and 4.76K forks on GitHub has more adoption than Guardian with 628 GitHub stars and 42 GitHub forks.
What is Devise?
What is Guardian?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Guardian?
What are the cons of using Devise?
What are the cons of using Guardian?
What companies use Guardian?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Guardian?
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.