Devise vs Stormpath: What are the differences?
Developers describe Devise as "Flexible authentication solution for Rails with Warden". Devise is a flexible authentication solution for Rails based on Warden. On the other hand, Stormpath is detailed as "User Management and Authentication for Developers". Stormpath is an authentication and user management service that helps development teams quickly and securely build web and mobile applications and services.
Devise and Stormpath belong to "User Management and Authentication" category of the tech stack.
Some of the features offered by Devise are:
- Is Rack based
- Is a complete MVC solution based on Rails engines
- Allows you to have multiple models signed in at the same time
On the other hand, Stormpath provides the following key features:
- User Authentication as a Service
- Authorization – Easily model and manage your data, including pre-built roles
- Flexible User Profiles
"Reliable" is the top reason why over 31 developers like Devise, while over 26 developers mention "Authentication" as the leading cause for choosing Stormpath.
Devise is an open source tool with 20K GitHub stars and 4.76K GitHub forks. Here's a link to Devise's open source repository on GitHub.
According to the StackShare community, Devise has a broader approval, being mentioned in 56 company stacks & 30 developers stacks; compared to Stormpath, which is listed in 3 company stacks and 4 developer stacks.
What is Devise?
What is Stormpath?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Devise?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake 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.