Try our new research platform with insights from 80,000+ expert users

Frontegg vs Okta Customer Identity comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Frontegg
Ranking in Customer Identity and Access Management (CIAM)
8th
Average Rating
9.6
Number of Reviews
6
Ranking in other categories
Single Sign-On (SSO) (18th), Authentication Systems (31st)
Okta Customer Identity
Ranking in Customer Identity and Access Management (CIAM)
6th
Average Rating
8.4
Number of Reviews
13
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2024, in the Customer Identity and Access Management (CIAM) category, the mindshare of Frontegg is 8.3%, down from 14.0% compared to the previous year. The mindshare of Okta Customer Identity is 8.9%, down from 12.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Customer Identity and Access Management (CIAM)
 

Featured Reviews

reviewer1658712 - PeerSpot reviewer
Great granularity for roles and permissions and is multi-tenant by design
Today the features we’re using the most include the registration page, user and tenants management (including storing custom data on the tenant level to use as “feature flags”), and the admin portal. I like the admin portal since it allows us a full-stack solution for user management. The frontend side is a major benefit that I am happy I can give my customers from day one, without compromising. It helps us grow fast and focus our dev team on the core product while providing important user infrastructure to our customers. Another important benefit we discovered is the ease of integration. The integration with Frontegg is almost immediate, and the support is great. If you’re thinking of developing it on your own, don’t.
SaravanaKumar8 - PeerSpot reviewer
Useful for authorization and other zero-trust authentication
If we wanted to access the Azure portal or any other portal, we used to scan with Authenticator. Once it was approved, we accessed the portals. The product is equivalent to Microsoft’s solution. I used Duo instead of Authenticator to authorize applications. People use Conditional Access Policy. People generally prefer Microsoft because it is free. I will recommend the tool to others. Our recommendations are based on the customer’s requirements, bandwidth, and budget. Overall, I rate the tool an eight out of ten.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Every feature is multi-tenant by design, making different customer requests effortless to provide."
"It has Audit Log and many cool features that if we were to develop them by ourselves, it would require a lot of research and development resources. Frontegg gives us everything we need to ensure that our customers have a safe and reliable authentication system in which they can also manage some of the features and roles by themself which gives them more control over their environment."
"Their developers were always willing to meet even though we are in very different time zones."
"The MFA policy via Frontegg allows us to enable/disable/enforce the Multi-Factor Authentication policy of our users and to enhance security and adhere to modern standards."
"The admin portal layer is super useful and saves valuable front-end development time."
"We like the SSO, permissions and roles, multiple workspaces, and react login components."
"The end user's ease of use is the most valuable feature."
"The most valuable feature of this solution for most customers is access management."
"As far as our security team is concerned, the ease of implementing multifactor authentication is definitely the biggest value for our organization."
"It is very seamless."
"The most valuable features of Okta Customer Identity are there is no infrastructure cost, integrated, has plenty of documentation, and is user-friendly."
"Okta has more when it comes to the policy level. It has distinctive features where you can do a mix and combination to have users access applications for various business cases."
"The most valuable feature of Okta Customer Identity is its SSO because it's very easy to use and it's user-friendly. Even the admin portal of the solution is very user-friendly, and you can walk through it with ease. Okta Customer Identity is not a complicated solution, and even the workflow automation feature is very, very easy to understand."
"We can integrate two-factor authentication with the applications."
 

Cons

"We really like the ability to add the same user across tenants. From a UX perspective, the flow can be betterized."
"We're hoping to see more user management-related features, according to Frontegg's roadmap."
"The PHP SDK is limited. It's not a huge deal as we can just use their web API directly, but it is something to note if you're using PHP.‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎ ‎‏‏‎"
"The web interface is missing a way to delete a workspace. I have accidentally created a workspace and was not able to delete it. It's a minor thing that should be supported."
"It would be nice to have a backup export with all tenant/users so that in case of a mistake we can have the option to restore the users."
"Frontegg is fairly stable, however, we are looking forward to some promised capabilities, such as more tightly integrated Feature Flag support."
"The initial setup could be easier to do."
"I would like to see the provisioning simplified."
"There is an access request system that is very limited access to the systems available for end-users. The access request should improve in Okta Customer Identity."
"What I'd like to see improved in Okta Customer Identity is the process of exporting users. Currently, it lacks this feature, and you have to use a third-party tool to export users from the group. Exporting users should be very easy, though I did notice that Okta Customer Identity is being upgraded from time to time, and I've been seeing much improvement in it compared to the previous years."
"Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta user profile."
"This solution would be improved by adding biometrics features."
"In the future, we'd like to see the product implement more security features, like, for example, zero-trust."
"Some limitations in scalability. Each application we work with can be completely different, resulting in highly variable implementation processes."
 

Pricing and Cost Advice

Information not available
"Okta's pricing is right where it needs to be and right in the middle of the market."
"Okta Customer Identity is not an expensive solution."
"Pricing might be high, but it comes down when the number of people using the product goes up."
"The solution is really expensive."
"We pay 23 pence (approximately $0.30 USD) per user, annually, for 150,000 users."
"The price of the solution is fair for what it offers."
report
Use our free recommendation engine to learn which Customer Identity and Access Management (CIAM) solutions are best for your needs.
816,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Government
10%
Financial Services Firm
6%
Retailer
6%
Financial Services Firm
13%
Computer Software Company
12%
Government
9%
Healthcare Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about Okta Customer Identity?
Okta has more when it comes to the policy level. It has distinctive features where you can do a mix and combination to have users access applications for various business cases.
What is your experience regarding pricing and costs for Okta Customer Identity?
The pricing model for the Customer Identity product is based on Monthly Unique Users (MUI). The pricing itself is a bit more expensive than the other products in the market so far. Since I know the...
What needs improvement with Okta Customer Identity?
Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta ...
 

Learn More

Video not available
 

Overview

 

Sample Customers

Information Not Available
FedEx, Adobe, National Geographic, Tyson, Hewlett Packard Enterprise
Find out what your peers are saying about Frontegg vs. Okta Customer Identity and other solutions. Updated: October 2024.
816,406 professionals have used our research since 2012.