Amazon Cognito vs DailyCred: What are the differences?
Amazon Cognito: 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; DailyCred: Everything you need to manage users for your website or app. Everything you need is included: email verification, password resets, session cookies, and all the UI you need for sign in, and sign up. Skip all this work and get running instantly. If you already have a sign-in system, DailyCred sits side-by-side with the full power of user APIs and dashboards.
Amazon Cognito and DailyCred can be primarily classified 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, DailyCred provides the following key features:
- One API for 12 OAuth Providers- Regardless of how your users sign up, DailyCred gives you access to identity information with a single consistent API. Sometimes users forget exactly how they signed up, so DailyCred prevents duplicate accounts for the same user.
- Security- Use our sign in UI, and get secure authentication over https for free. Don't waste another moment buying or implementing ssl certs ($70 on GoDaddy). Credentials are stored as salted hashes using bcrypt, the industry standard designed by Niels Provos and David Mazieres. DailyCred is securely hosted by Amazon AWS.
- CRM & Backoffice without the Hassle- We create a record of every user and lead that signs up on your website. We even show you how they found you, what campaign they came from, and what they did on your site before signing up. Resetting passwords, monitoring events, banning users, deleting or creating accounts and viewing your website as your users can be handled by any team member.
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.