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

JumpCloud vs Okta Workforce Identity comparison

Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jul 6, 2025

Review summaries and opinions

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

Categories and Ranking

iboss
Sponsored
Ranking in ZTNA as a Service
8th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
19
Ranking in other categories
Secure Web Gateways (SWG) (7th), Internet Security (3rd), Web Content Filtering (1st), Cloud Access Security Brokers (CASB) (7th), Secure Access Service Edge (SASE) (8th)
JumpCloud
Ranking in ZTNA as a Service
16th
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
17
Ranking in other categories
Single Sign-On (SSO) (12th), Identity Management (IM) (19th), Enterprise Password Managers (12th), Identity and Access Management as a Service (IDaaS) (IAMaaS) (13th), Active Directory Bridge (5th), Cyber Asset Attack Surface Management (CAASM) (6th)
Okta Workforce Identity
Ranking in ZTNA as a Service
10th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
68
Ranking in other categories
Single Sign-On (SSO) (2nd), Authentication Systems (6th), Privileged Access Management (PAM) (6th), Identity and Access Management as a Service (IDaaS) (IAMaaS) (3rd), Access Management (4th)
 

Featured Reviews

Matt Crockford - PeerSpot reviewer
It's easy to roll out, and their understanding of our business made it seamless
One aspect we value about iboss is its simplicity. Their customer service is brilliant, and they are super responsive and knowledgeable. It's easy to roll out, and their understanding of our business made it seamless. We were impressed by the solution's mental health function, which can detect if someone needs help. It scans what users are browsing and flags warning signs so we can check to see if they are okay. We've had to use it a couple of times. The user interface is highly intuitive. Our IT team picked it up with minimal training. It's arranged so that it's easy to find where things are. Another advantage is the single pane of glass console, which gives you visibility into what's happening. We're not fully there yet because we haven't implemented zero trust, but we're excited about the possibilities from the demos we've seen. We launched a POC of iboss' ChatGPT Risk Protection feature two weeks ago. AI is a great tool, but you need to be careful what you put into it. My biggest fear is employees inputting sensitive corporate information or customer PII data into one of these chatbots. I was impressed by our trial of the feature. It's exactly what we wanted. Now, when a user goes to ChatGPT, there's a banner warning them not to share information, and we can block conversations containing customer data like bank details and email addresses. I don't want to stop people from using it, but we need visibility. We've only tried it on a test group of 15 people. You can configure it to look for specific keywords or integrate it with your DLP policy if you have that configured
MuhammadAzhar Khan - PeerSpot reviewer
Manage multiple cloud platforms seamlessly with unified credentials
The most impactful feature of JumpCloud is that it allows me to use one credential for all platforms or accounts, reducing the need to remember multiple credentials. This feature is highly beneficial for user management, particularly for clients with multiple cloud accounts. Additionally, JumpCloud simplifies the workflow when I work with different cloud platforms, such as AWS, Azure, and GCP, by integrating directory and credential management.
Tor Nordhagen - PeerSpot reviewer
Extremely easy to work with, simple to set up, and reasonably priced
The drawback of this solution is that in our shops, many staff members sometimes have to be borrowed from one shop to another and the solution does not really support having multiple roles. The user experience we would like to have when a person works in shop A which pays their salary is that they should have access to pretty much everything. Maybe you have somebody who is a manager in that shop A, he should be able to order new wear, he should be able to change the pricing, he should be able to empty the cash registry, and ship it to the bank. But when for instance, in COVID, people had to fill in for people in shops where a lot of people were sick, then they had to actually use user accounts of people that work in shop B. If you were employed in shop A, you could not work in shop B without borrowing somebody else's user ID and password. Which is really bad. We haven't been able to work around that and Okta Workforce Identity does not have a solution for it. We are now piloting their identity governance solution. Obviously, it's easy to give somebody access, give them an account, and give them roles, but it's hard to maintain that. For example, if you moved from, say working in a shop to working in a warehouse. But why do you still have all this shop access? The solution has until now not had anything to really support the process of taking away access. But now we are in a better release program of Okta's identity governance solution. Although it's very basic, the solution has started on a journey, but identity governance is something that Okta Workforce Identity really needs to improve. The ability or the options in the solution for changing the look and feel are not good enough because in our partner portal, essentially what they have is an ugly admin interface. The admin interface is good enough for us technical people because that's all we need. We work with the product and we're able to see the data but when it comes to presenting the service portal, Okta Workforce Identity does not have any capabilities really for making it look pretty. To add branding and different graphical user interface elements than Okta basic for essentially delegated admin for the business-to-business portal is horrifying because you're essentially using the tech admin. The only option we had and used, was to take the tech admin console and strip it. so that a vendor that has some goods that are sold in the shops, when they want to add a user on their side, say a driver or a packer on their side who should know how much they've packed in a truck to come to our warehouse, then the user interface that this vendor is using, these functional people will then have to use an extremely basic user interface.

Quotes from Members

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

Pros

"Because of iboss, I did not have to assign web filtering tasks to my techs on a daily basis."
"I would definitely recommend iboss for web filtering purposes to other organizations or individuals."
"From a use-case scenario, what I like the most is the plug-in. I like the fact that we can do the filtering of these devices offsite independent of the network they are connected to, and we do not have to have traffic coming back inside our network."
"We chose iboss for both zero trust and proxy (SWG) because their SWG was superior."
"First of all, the security policies are essential. I do not have to rely solely on Active Directory for our users."
"Granular setup, which was able to set different levels of filters using the OUs in the AD."
"iboss has significantly lowered the number of security incidents. It is crazy how much it blocks and how much it is aware of the outside danger."
"Technical support is pretty sharp and very responsive."
"I rate the stability of JumpCloud ten out of ten."
"Azure Cloud services are on time and run well and if we use a JumpCloud, the benefits we receive are the ease of management and the solution is completely user-friendly. End users can do identity management easily."
"As a cloud-based directory, JumpCloud allows me to integrate nearly every system I have come across that supports SAML 2.0. That's a specific technology that allows different services to integrate for user authentication and identification purposes. That means that with JumpCloud, I can then have one single password. Single sign-on for a particular user that works with VPN, radius authentication for WiFi, logging into Office 365, and their email. Their individual computers use that same password. It's extensible which allows us to tie in customers' security systems. We don't have to provision a new user, 12 different places with 12 different passwords. I only have to create them once and assign them privileges."
"The whole product is great. The device management is amazing. The fact that you can basically set up an entire machine without having the machine in front of you is most valuable."
"The solution is stable."
"The most valuable features of JumpCloud are flexibility, policy management for devices, and device patch management. For example, we can limit access to devices only in Chile or send a number of commands to the devices to manage them."
"Some of the most valuable features of Jumpcloud have been the use of the policies. They have been very helpful. There are modules in there for policies where you can create your own which indirectly are GPOs similar to what you have for Microsoft environments, however, they are only doing registry changes. They are very powerful and useful. Additionally, having your directory and SSO in one spot is another thing that they provide in application management. Adding, removing, and updating applications are in one place for desktop administration."
"After deploying to the cloud, we had remote device management on all of our corporate laptops."
"We face no challenges in integrating the product with our legacy systems."
"Enabled MFA to access federated applications as well as increased user satisfaction through improved provisioning times and more reliable processes."
"Its simplicity and its integration with various vendor-agnostic platforms are the most valuable features."
"The solution so far has been very stable."
"This solution has a lot of capabilities and features."
"The most valuable features depend on a customer's needs. Our customers generally find multi-factor authentication very useful."
"First of all, the solution is very simple."
"Okta controls all the users. It has context-based access from the user and type of device. It identifies the risk and can do a step of authentication when that user is trying to access some sensitive application from an unknown device."
 

Cons

"Sometimes the agent stops working in iboss, and we have to reinstall the agent."
"Sometimes, obviously, there are bugs."
"Sometimes when you call in support, you get someone who is just following a sheet. It feels like a runaround. You feel that you are running into that support wall."
"File integrity monitoring would be very advantageous as an additional feature."
"The dashboards for local use could be better."
"For zero trust implementation, we encountered complexity issues, especially with a large infrastructure company ExxonMobil."
"I'd like to see them accelerate development on the security side, particularly around data loss prevention."
"Our biggest problem with their service was it did not recognize the device and filtering did not always work correctly."
"JumpCloud could improve by providing more features. They are only giving the three standard features, such as SSO radius. I would like there to be multi-tenant features. For example, my colleague is from a different organization, and he's using different applications and I'm using different applications, I wanted to access his applications and database with my JumpCloud credentials. However, since it is a multi-tenant instance. I would like it to be open-ended where we can gather all these multi-level organizations to put in a single domain to access one authentication for all the different applications."
"They need more straightening of the SSO capabilities."
"The product needs to create its own self-service feature which has been requested by all the admins in the community."
"It could dip into CI/CD tooling as well. That would be a very interesting part to see."
"The querying for users in Jumpcloud could be improved, it is sometimes difficult to use. When you're trying to query a user and you spell out their name, you don't receive that person. Sometimes you receive a list of people with the same first name or last name. This could be better."
"For improvement, the tool should introduce more customization options."
"JumpCloud can improve in its synchronization of identities. More specifically, groups with Office 365. They've been working on it, but it's not where I would necessarily like it to be."
"Support is not good enough."
"It can have more API integrations."
"There is no proper documentation on integrating test cases with Okta, and this issue is troubling whenever I try to implement it."
"Okta Workforce Identity could improve provisioning it can be made simpler."
"The only area of concern in the solution stems from the fact that my company needs some help regarding the setup phase from a partner."
"The solution lacks an on-premises deployment model so it can't offer a hybrid solution. It would be ideal if clients had options that weren't just cloud-based."
"The initial setup can be complex at first."
"You can't hide the device when you're checking logs."
"Areas for improvement with Okta Workforce Identity would be in the governance place; for me, it is light."
 

Pricing and Cost Advice

"It is expensive compared to one of its competitors."
"It is not expensive, and it is also not cheap. iboss is priced right in the sweet spot for the number of features it offers."
"The overall pricing for iboss is very competitive and transparent."
"We have not priced the solution recently, but they were competitive with other vendors in the past."
"We had the cost of purchasing a new appliance along with the implementation and licensing costs. However, the following year, the cost of just licensing was similar to what was paid the previous year for a new appliance along with the implementation and licensing costs."
"It is probably in line with other solutions, but I do not deal with the financial side."
"The cost of the solution is approximately $12 per user. However, the cost depends on what modules you're using. They have an all-in-one package and they do have tiers. For example, the more users you have, the cheaper it ends up being in the end too. I know they've done some changes to the pricing model and I haven't been involved in a lot of the licensing lately. I don't know the exact cost at this time."
"Licensing cost can be anywhere between $2 and $18 a month depending on what you want to do."
"I rate the product's pricing a five on a scale of one to ten, where one is cheap, and ten is expensive."
"The cost was around $5 per user per month."
"JumpCloud offers several subscription plans as a software-as-a-service (SaaS) provider. The pricing is based on the number of users and the services that are required, meaning that you only pay for what you consume and don't have to pay for services that you don't need. When compared to other solutions, JumpCloud can actually be more cost-effective, as it eliminates the need to hire a team, purchase hardware, pay for licenses and software, and worry about updates, security, and backups. Thus, it offers a more efficient and cost-effective solution for managing your needs."
"The pricing is all on the JumpCloud website. It's not hidden, you don't have to go through a show me a quote type procedure. The pricing is straightforward to understand."
"The pricing model changed about 18 months ago. It used to be that you got 10 users free, and then you paid for any user above 10 users. Now, when you go above 10 users, you pay for every user. It has become a bit more expensive, but it's such a good product. When you take into account Microsoft licenses, if you were to run Active Directory, you'd need a server to put it on, or you would need a couple of servers, backup, etc. It's a no-brainer. JumpCloud is so much easier to manage from my perspective, regardless of the cost increase. It's just brilliant."
"I am pretty sure that the cost to acquire JumpCloud is less. They have à la carte or per-user pricing. The pricing is there on their webpage. I am not sure if they have any enterprise pricing or discounts if you have more users. But the overall pricing is less than Okta."
"It is costly for large companies."
"This is an expensive solution but the security makes it worthwhile."
"License is around US$20,000 annually."
"The pricing for Okta Workforce Identity could still be improved or made cheaper. It costs from 50 to 100 euros a year per user. Okta Workforce Identity has different packages you can choose from, and my previous company had all of them, particularly the full Okta suite."
"The licensing model is fine for general service usage. However, the charges for API features and API tokens can be quite high."
"The pricing is reasonable."
"Price-wise, Okta Workforce Identity is a cheap solution. The overall cost depends on the license since you can negotiate with Okta or any of Okta's partners only if you opt for many licenses."
"The solution's pricing model could be better for SMBs."
report
Use our free recommendation engine to learn which Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions are best for your needs.
866,088 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
12%
Financial Services Firm
11%
Manufacturing Company
9%
Government
6%
Comms Service Provider
17%
Computer Software Company
14%
Financial Services Firm
7%
Manufacturing Company
6%
Computer Software Company
13%
Manufacturing Company
10%
Financial Services Firm
9%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise6
Large Enterprise5
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise2
Large Enterprise3
By reviewers
Company SizeCount
Small Business30
Midsize Enterprise16
Large Enterprise32
 

Questions from the Community

What needs improvement with iboss?
For zero trust implementation, we encountered complexity issues, especially with a large infrastructure company Exxon...
What is your primary use case for iboss?
Previously when I used iboss, we did the POC for iboss for ExxonMobil. Four or five people wanted to move from our ol...
What is your experience regarding pricing and costs for iboss?
Regarding pricing, setup costs, and licensing, iboss is not cheap, and that's my only concern. There are cheaper alte...
What do you like most about JumpCloud?
The product enables device management.
What is your experience regarding pricing and costs for JumpCloud?
AWS charges per user, which can be costly if I have more than ten users. Third-party platforms tend to be cheaper tha...
What needs improvement with JumpCloud?
I would like AWS to integrate more cloud platforms with JumpCloud, such as Alibaba or Oracle. This would be helpful, ...
What do you like most about Okta Workforce Identity?
Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on...
What is your experience regarding pricing and costs for Okta Workforce Identity?
Pricing for Okta is reasonably not that much, however, I don't have access to the commercial aspect.
What needs improvement with Okta Workforce Identity?
Areas for improvement with Okta Workforce Identity would be in the governance place; for me, it is light. Okta is mos...
 

Also Known As

iBoss Cloud Platform
Resmo
No data available
 

Overview

 

Sample Customers

More than 4,000 global enterprises trust the iboss Cloud Platform to support their modern workforces, including a large number of Fortune 50 companies.
Cars.com, GoFundMe, Grab, ClassPass, Uplight, Beyond Finance, Foursquare
FedEx, Zoom, Takeda, Lululemon Athletica, GrunHub, jetBlue, McKensson, Bain & Company, Engie, Peloton, Sonos, T-Mobile, Hewlett Packard, MGM Resorts, Ally Financial, Priceline, Albertsons, Itercom, Classy, FICO, Kensho, Live Nation, Drata, Rotary, and others.
Find out what your peers are saying about JumpCloud vs. Okta Workforce Identity and other solutions. Updated: August 2025.
866,088 professionals have used our research since 2012.