IBM Cloud App ID vs. Keeper

Whenever you need to provide Security Provider functionality for a web based application it is well suited. You can also integrate with other directory services (e.g. SAML, Facebook, Google), but not so easily with other Auth0 based services. The customization of the login page is very intuitive, but does not allow much customisation. using the integrated Cloud Directory, you do not need to integrate with existing security providers and you can build up your own user base - including Multi-Factor Authentication settings and password policies.

Incentivized

I can only think of scenarios where Keeper is well-suited, in my experience. I work in small business (i.e., sole proprietor, 1 employee) environments and Keeper is well-suited to my needs. I imagine it would also be well-suited to multi-user environments, but would require a great deal more management and organization in such environments.

• Uses OIDC/OAuth, so the protocols for accessing user info and token management is familiar
• Clear pricing model
• API binds nicely with IBM Cloud Functions
• Billed as part of our IBM Cloud, along with our other services
• Front-end SDK for Vue, works well

Incentivized

• Easy to use - you can easily access it anywhere and anytime you want (it has mobile apps, web and desktop versions)
• High level of security - 2-step authentication with your phone number
• Simple to save and get passwords and login information. Keeper fills it in for you. It may create complex passwords for you
• Syncs across all devices

Incentivized

• Pricing can be heavy on small organizations.
• User interface updates could be timely.
• Cloud services hangs at times, but very rarely.

Incentivized

• I find that Keeper could use some work with their desktop interface, a sleeker and friendlier user interface would definitely benefit them.
• Keeper doesn’t have a Security Dashboard, which makes it more complicated to evaluate the strengths and weaknesses of your passwords.
• The automatic web form filling is somewhat limited at the time, but im sure they will improve it soon.

Incentivized

It's just easy to use, plain and simple. It has the complexity and user-interface that gives you confidence in its build but the ease-of-use that keep things from getting too complicated. A huge plus when you have to onboard new members of the team or summer interns when you need them to step in and make orders on your behalf.

Incentivized

Because it is so good. It always works, has not crashed even in 3 years; I have a lot of data in it (never any problems).

Both the software have different use cases, like IBM Cloud App ID, which will be more suitable for internal websites and apps or specific event website authentications, Auth0 can be suitable for consumer websites, e-commerce sites, where social media login is preferred more by the users. Both have their own capabilities so can be chosen according to their needs.

Incentivized

From a password manager, they are all similar in terms of organisation and credential management but what Keeper has above these organisations is the MSP/Admin console.

Its intuitive, great to setup and the reporting functionality is second to none compared to the other reviewed tenants.

Incentivized

• This has had a positive impact on security while developing our company's first major application.
• It has impacted our development process heavily by making authentication simpler than ever.
• It has helped reduce time in our development process by having easy integration and useful guides.

Incentivized

• The spreadsheets and printed papers being passed around the office with passwords on them have gone! This is a huge security hole plugged.
• Users actively use the software which says something - it is easy to use and intuitive. When software is not intuitive, it tends to not get used.
• It gives IT control over who does what with passwords, and while difficult to quantify it is certainly a dramatically positive impact on the organization.

Incentivized