Need advice about which tool to choose?Ask the StackShare community!

Amazon Cognito

547
828
+ 1
34
Devise

382
225
+ 1
56
Add tool

Amazon Cognito vs Devise: What are the differences?

Developers describe Amazon Cognito as "Securely manage and synchronize app data for your users across their mobile devices". You can create unique identities for your users through a number of public login providers (Amazon, Facebook, and Google) and also support unauthenticated guests. You can save app data locally on users’ devices allowing your applications to work even when the devices are offline. On the other hand, Devise is detailed as "Flexible authentication solution for Rails with Warden". Devise is a flexible authentication solution for Rails based on Warden.

Amazon Cognito and Devise can be categorized as "User Management and Authentication" tools.

Some of the features offered by Amazon Cognito are:

  • Manage Unique Identities
  • Work Offline
  • Store and Sync across Devices

On the other hand, Devise provides the following key features:

  • Is Rack based
  • Is a complete MVC solution based on Rails engines
  • Allows you to have multiple models signed in at the same time

"Backed by Amazon" is the top reason why over 11 developers like Amazon Cognito, while over 31 developers mention "Reliable" as the leading cause for choosing Devise.

Devise is an open source tool with 19.9K GitHub stars and 4.74K GitHub forks. Here's a link to Devise's open source repository on GitHub.

StackShare, Movielala, and DeveloperTown are some of the popular companies that use Devise, whereas Amazon Cognito is used by Sendhelper Pte Ltd, Strain Merchant, and ChromaDex. Devise has a broader approval, being mentioned in 56 company stacks & 30 developers stacks; compared to Amazon Cognito, which is listed in 40 company stacks and 12 developer stacks.

Decisions about Amazon Cognito and Devise
Brent Maxwell
Migrated
from
Amazon CognitoAmazon Cognito
to
Auth0Auth0

I started our team on Amazon Cognito because I was a Solutions Architect at AWS and found it really easy to follow the tutorials and get a basic app up and running with it.

When our team started working with it, they very quickly became frustrated because of the poor documentation. After 4 days of trying to get all the basic passwordless auth working, our lead engineer made the decision to abandon it and try Auth0... and managed to get everything implemented in 4 hours.

The consensus was that Cognito just isn't mature enough or well-documented, and that the implementation does not cater for real world use cases the way that it should. I believe Amplify has made some of this simpler, but I would still recommend Auth0 as it's been bulletproof for us, and is a sensible price.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More