What is our primary use case?
We have a few use cases for JumpCloud. One is SSL for some legacy applications, LDAP, user provisioning, MFA access into the AWS environments, and some third-party apps for monitoring. There are also things like Datadog and New Relic that can be added as use cases.
Another use case is for system access for our EC2 instances, you can SSH in those instances. It will install a Linux user ID and provide the public key that is assigned to that specific user.
I have also used it for some automated scripting, although there are a lot of tools in that space. JumpCloud has a lot of features. I use this tool to consider how this system is managed; if it uses our standard, and if it is a legacy system. I have used the JumpCloud agent to run scripts arbitrarily on systems to see if I will get back information.
Additional use cases include using it for audits, SOC 2 Type 2, and status scope for FedRAMP. I have used their API extensively to make web requests, get back JSON data, and turn that into Excel spreadsheets, etc. to show the auditors.
I have also used JumpCloud for event logs and for other similar activities to track our usage within the environment.
How has it helped my organization?
I have also used Okta quite a bit in recent roles but I think that JumpCloud is a very useful service, especially if you are just getting started. If you want to POC something, it is very useful and it is easy to set things up. I like that feature.
The issue of allowing SSH in the systems, managing users, their keys, etc. has been pretty useful to do with JumpCloud.
It is convenient to do the scripting part with JumpCloud though there are other tools that can do it too. They provide a lot of device profiling, etc. but I have not really explored those aspects extensively. It is a nice solution for both cloud access and system access.
What is most valuable?
The UI is intuitively easy to use. It is easy to set up a user. I have found the group management to be pretty simple. You can group users, then assign them to groups of systems, and that relationship allows us to ease the management burden. Instead of having to map a user to an individual system, you can consolidate and group them. I found that to be pretty useful.
What needs improvement?
There are a few aspects that could be improved. Their API was a little spotty when I last used it, and some of those use cases were around removing systems from our environment. We have ephemeral environments, so systems will come up and down and up and down and auto-scale. For each of those systems, the JumpCloud agent gets installed in the system and it gets registered to groups. We found that the systems would not get auto-removed, and so the agent would try to check in or the UI would show that the agent was not responding. We had to create a script to remove these systems from our environment, and that became a bit of a pain for us. I do not know if integration with AWS CloudTrail or something like that can help to know when a system is terminated or the lifecycle of that system, that would be pretty helpful to improve this process. We had to write our own script and sometimes that would not work.
There are two versions of the APIs. I have also seen some methods that were lacking in the API versus raw REST cURL requests. I have not double-checked this. I just went towards a path of not trusting the API at some point because it just was not consistent with what was in the raw cURL request. In that case, it was the user auditing and things like that which was getting the expected output back.
Lastly, for systems, user IDs are created on Linux systems. I don't know if this has changed, but at one point, we were running into a collision. A Linux system will assign a value to a user ID. For example, if 1000 is the user ID, JumpCloud will also assign a user ID. You can fix that number and it will increment based on a certain value, but we found that we have internal systems as well that will create users. In some cases, we would have user ID conflicts on the system and in JumpCloud. We have received prompts from JumpCloud that says, "Hey, there's a conflict and this user's using this ID number." That was for some of the use cases where we had to run scripts on the system. I would have to reassign the user ID and run the script to have consistent user IDs for that user across the board. Otherwise, the user would get added as the next user on the system. There was a little bit of complexity there and a little bit of pain. These are the improvements I would like to see in the tool.
I have heard that JumpCloud has made a lot of changes and I would like to see them. If it is not there now, it can generate an easy-to-use report for an audit and give me the relationships between user groups and systems. I am not sure if that exists. These were not there the last time I had run an audit on systems.
From my understanding of the solution, OpenID Connect is not supported, but it would be cool to see that feature involved in the service.
There has been a shift away from JumpCloud which is not because of technical reasons. The shift has been mainly because of the cost and compliance issues. I do not believe that they have FedRAMP compliance. It is a requirement for the organization to maintain FedRAMP compliance. The vendor's due diligence is an important aspect. Our vendors have to meet or we try to have them meet the same bar that we have for compliance. The shift is occurring not because of technical reasons but more on the basis of what services are offered. It would be nice to see JumpCloud as a FedRAMP or NIST 800-53 certified product.
Buyer's Guide
JumpCloud
April 2026
Learn what your peers think about JumpCloud. Get advice and tips from experienced pros sharing their opinions. Updated: April 2026.
893,164 professionals have used our research since 2012.
For how long have I used the solution?
I have been using JumpCloud since about 2018, so it's been a few years.
Since it is a SaaS product, there is no particular version as the tool gets updated regularly.
What do I think about the stability of the solution?
There have been a couple of outages. They are pretty good about updating their status page. I do not recall the outages persisting for an extended period of time. I am also not sure if the outages are related to the cloud provider, i.e. AWS or something like that. But usually, JumpCloud is fairly reliable.
What do I think about the scalability of the solution?
I think JumpCloud is fairly scalable. We do not have a huge user base, about hundreds of users. However, I believe that they have some fairly large enterprises as customers and, based on my conversations with them, they use AWS as the backbone. That might have changed, but they use a cloud provider to provide those services, which allows a lot of scalability and capacity.
How are customer service and support?
I have worked with the support team and they are usually pretty easy to work with. I spoke to the CEO of the company, but I do not have a direct line to him. The CEO was the founder of another company that I worked for at some point in time, so I got to meet him in person. We started collaborating and they did add a lot of features. Features like the device management and directory insights were pretty cool to see. They do take feedback pretty well.
I always approach the support when I have an issue. The issue that I have faced with the support is when we start to dig into a technical issue. The support team is willing to get feedback from their product teams. I have also spoken to their product managers to hopefully get some of the features that are on the roadmap.
Which solution did I use previously and why did I switch?
I have previously used Okta. I think there are a lot of differences based on the cost aspect. It differs on the basis of how you would manage a system. Though Okta has similar services with respect to their SSO functionality, the system access provided by Okta is costly or cost-prohibitive. They charge per system, and I think it is around $15 a month. I think the basic JumpCloud pricing model is $10 a month. I have heard that they have increased the prices a bit.
How was the initial setup?
The initial setup is really straightforward. I like their documentation. It is basically point-and-click. It is pretty straightforward. Since it is a SaaS solution, it is deployed over the internet. To deploy the solution, you need to provide your email address. I think they will look for an MFA token. You can start with 10 free users, so it is nice to sandbox.
What about the implementation team?
We implemented the solution using an in-house team.
What was our ROI?
I think that there is ROI with JumpCloud. It eases a lot of burden. It facilitates the central management of user identity. Though there are some improvements to be made, I really do like the system access that they provide.
What's my experience with pricing, setup cost, and licensing?
I am pretty sure that the cost to acquire JumpCloud is less than Okta. They have “à la carte” or per-user pricing. The pricing is 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.
The different pricing plans have different features. It starts from $2 a month for "à la carte" features and you can pick and choose. JumpCloud mentions the best value as $15 a month, zero trust platform plus $18, which is the highest cost per month per user, and then they also have a core package at $11 per month per user.
What other advice do I have?
I would rate JumpCloud an eight out of ten.
I would recommend trying out JumpCloud. Users can look into how they would register their systems into JumpCloud, de-provision them, and do the same for user management and user life cycling. I would also recommend exploring the API if you intend to build out any automation. You need to check out if that is your use case. I would probably start small. You will also have to see what the process is to set up SSO, check out their documentation on how to set up LDAP or SSO and look into a cloud provider. I would recommend experimenting a little bit. You get a free tier for 10 users which looks like 10 users and 10 devices which makes it fairly useful to explore.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.