JumpCloud Reviews

We use the solution for centralized management of PCs and user accounts.

We tried other tools, but sometimes the user interfaces of other tools are a little bit difficult to understand.

The product enables device management. It is one of the reasons why we chose it. We can remotely help people. We can also do installation remotely. We needed LDAP and RADIUS server. The website is pretty straightforward. We have users, devices, and groups. It's easy to understand. It has a small learning curve. The product provides multi-factor authentication. We needed that.

We need more multi-factor authentication possibilities. I opened a ticket for it. However, it is not configurable in JumpCloud.

I have been using the solution for half a year.

I reported an issue. The support person contacted me. However, they didn’t come up with a solution yet. Support is not good enough.

We were using internal Linux tools before. They were pretty old. Now, we are migrating to JumpCloud.

The initial setup is straightforward. Many helpful tools are available on the web, and there is a lot of helpful documentation. We will need knowledge of Windows and Linux. The product can be deployed in half a year. Our plan is to deploy it completely by the end of the year.

The solution is pretty expensive. It costs us EUR 250 per user per month. It was a point of hesitation for us. We can get premium support, too.

We also considered Okta. It is more suitable for Windows. If someone wants a tool for Windows, then Okta is pretty good. However, we want a solution for Windows and Linux. We also wanted LDAP. JumpCloud stands out in those things. Okta can do it, but not in the way that we would like it to.

The tool can be improved. I will recommend the solution to others. Overall, I rate the product an eight out of ten.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

We implemented the solution using an in-house team.

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.

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.

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.

My customer base is primarily small businesses. I define "small business" as companies with fewer than 100 employees. However, that does not mean that JumpCloud is only applicable to that specific use case. It's just how we have been using it. It is a cloud-based directory that essentially allows you to replace completely on-premise Active Directory or other LDAP directories. All our customer identities originate from JumpCloud.

JumpCloud has simplified the way we create and manage users' accounts and privileges. If there's an employee separation, I need to be able to shut down access immediately. I don't want to have to go through 12 dashboards to do it. I can go into JumpCloud and I can hit one big switch and they're done. When a user is disabled in JumpCloud, all applications and services that have been integrated with JumpCloud automatically disable the user in question. (VPN, Wi-Fi, Microsoft 365, Netsuite, Box, Salesforce, other various cloud applications, security systems, file servers, local machine logins, etc.)

As a cloud-based directory, JumpCloud allows me to integrate nearly every system I have come across that supports SAML 2.0, a technology that allows different services to integrate for user authentication and identification purposes. With JumpCloud, each user has a single username and password that works for VPN, radius authentication for WiFi, logging into Microsoft 365 (email), and their individual computers. It's extensible via hundreds of premade application integrations. 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.

JumpCloud has made continuous, noticeable improvements in the feature set of the solution. Recent major improvements have focused on equipment inventory, mobile device management (MDM), and fleet reporting.

JumpCloud could improve its synchronization of groups with Microsoft 365. At this point, only mail-enabled security groups can be synced. 

This leaves plenty of situations where I still have to create groups in Office 365 because I can't make them in JumpCloud and have them synchronize. If this was possible, I wouldn't have to go into the Office 365 dashboard for user management as much as I do.

I would like to see the continued addition of premade integrations with various cloud applications and services. There are hundreds of them in the solution currently, but there could always be more.

I have been using JumpCloud for four years.

I have had no problems with the service in the two years I've used it, it is highly stable. I have heard that they have had some outages but they have not caused a problem with any of my environments.

The scalability of JumpCloud is great. I see no reason why this solution couldn't be used easily for up to 500 users or beyond that. I'm working with companies that are fewer than 100 and I have no problem thinking that this is scalable with where my customers are going in the next several years.

I have contacted the technical and integration teams from JumpCloud, and
both teams are top-notch. Any time that I have needed to have a general operation question answered or because something didn't seem to be working right, their technical support team has been great. Most of the time it is just a matter of confusion on my part rather than actually something not working. The integration team is the group you engage with a particular service or cloud application doesn't already have an integration written for it.

Positive

There are several services that do what JumpCloud does, but few that do it as well as them. I think that JumpCloud and Okta are easily the most mature solutions. We could see that on-premise LDAP/Active Directory was not where the future was headed, and chose JumpCloud after an extensive period of in-house testing and determining that the feature set was the most in line in our customers' needs. JumpCloud was the first and only cloud directory service we deployed. All our customers went directly from on-premise LDAP directories straight to JumpCloud.

JumpCloud has an incredible ability to allow users to start using the service in little to no time. It's a huge selling point. You can have JumpCloud up and running in under half an hour. It will adopt existing machines and identities. You can pull them in from Office 365 or from other LDAP sources. 

My first rollout of this solution was in the spring of 2020 and as anxious as I was going through the process in a production environment, it was simple. I did not have a single problem.

I did the implementation of the solution.

There is no maintenance required. You set up the solution and go. There's no updating or patching. It's all automatically done for you behind the scenes. I'm a managed service provider -- I want to set up a solution and forget about it. I want it to always work.

The amount of work that JumpCloud saves pays for the solution easily.

The cost of the solution depends on two things -- (1) whether you're going a la carte or buying the "JumpCloud Platform", and (2) whether you're paying a year in advance, or paying monthly. However, in most cases (even the smallest companies), the Platform option is the right way to go, and costs between $17 per user, per month. It's worth every penny. The price of the solution has increased over the last four years but is still reasonable. You can pay extra for upgraded technical support resources.

JumpCloud's pricing is right on their website. You don't have to go through an "email me a quote" type procedure. The pricing is straightforward to understand.

I rate the price of JumpCloud a four out of five.

Back in 2019, we looked into Okta. JumpCloud was a better fit then, primarily because of the JumpCloud agent for Mac and Windows.

My advice to others is not to be afraid and try the solution out. It is worth it.

I rate JumpCloud a nine out of ten.

There's always room for improvement, regardless of how good the solution is.

My company's clients use JumpCloud to manage devices from Apple.

The most valuable feature of the solution is Windows Out of Box Experience (OOBE). The application management capabilities of the solution also work well.

For improvement, the tool should introduce more customization options.

I have been using JumpCloud for three years. My company operates as a service provider and integrator of solutions, and for JumpCloud, my company functions as its reseller. I don't know the exact version of JumpCloud I use.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a ten out of ten.

Around 5000 users in my company use the solution.

I rate the technical support a nine out of ten.

Positive

I rate the initial setup a nine on a scale of one to ten, where one is difficult and ten is easy.

The initial setup was straightforward.

JumpCloud is a SaaS solution, so it is deployed on a public cloud by AWS.

Considering from an end-to-end perspective, the deployment project takes around a month.

I rate the product's pricing a five on a scale of one to ten, where one is cheap, and ten is expensive.

There are no costs in addition to standard licensing fees.

I would tell those planning to use the solution that they get in touch with a good partner for implementation.

I rate the overall solution a nine out of ten.

We needed to provide centralized authentication access management to all of our company devices, mainly our laptops. That's our main use case. 

After deploying to the cloud, we had remote device management on all of our corporate laptops. We were essentially able to protect our informational assets in the event of someone trying to leave under unfortunate circumstances and take the company laptop with them, which actually happened to us before we deployed this product. They were able to protect our information and give us control over those devices to be able to turn them off. It also helped us to get to the level that we needed to get to for our HIPAA compliance.

The central authentication is great. We like that we can provide single sign-on across all of the critical applications so that we can control access management in that regard.

The pricing is reasonable.

The solution is mostly stable.

It can scale.

Support is helpful and responsive. 

They were working on means of delivering a more holistic view of patch management across all of the devices. We didn't get to test out some of their newer features. That was something that we needed. We didn't necessarily have, so we had to go with a different product, and then we never had an opportunity to sort of bring it back into jump cloud versus using that separate product.

They need more straightening of the SSO capabilities. For example, with some companies, you can configure just in time, so you don't have to manually go out to that system, and create the user and remove the user, and all of that. They need to automate that process more.

I started using the solution for about three years. 

I'd rate the stability eight out of ten. We had a few outages, although not very often. It was pretty reliable. 

I'd rate the scalability nine out of ten. 

Our company is in the process of closing down. We are not increasing usage. However, at one time, we had over 100 users. 

Technical support has been helpful and responsive. They were great. 

Positive

The initial setup was very straightforward. The transformation went very well, even with a hesitant workforce. 

We did see an ROI in the ability to track and protect our data. It helped ensure we were HIPAA compliant. 

The pricing was fair when I made a comparison with other solutions. It offered the best price for both operating systems (Windows and Mac). 

We looked at Microsoft Active Directory and Okta, among other solutions. 

I'm not sure which version of the solution I'm using. I'm on the cloud deployment. 

I'd recommend the solution to others. I'd advise new companies to leverage their support team when getting started. They are very helpful. 

I'd rate the solution nine out of ten. 

I use JumpCloud across a whole bunch of different clients to manage their devices, to manage their users, and to manage their third-party applications through single sign-on.

It's a SaaS product.

In a remote world, it has made my life a lot easier. When people were in the office, you could use Active Directory, but we moved to JumpCloud just before COVID kicked in. It gave us the capability to continue managing machines without them having to check into the office.

I can set a machine up easily. I can send someone a new machine, and they boot it up. I give them a couple of instructions, and then it hands the machine over to me. I can configure the machine remotely by using policies and commands through JumpCloud.

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 single sign-on capabilities are very helpful. If someone leaves the business, at the click of a button, you can literally disable their account for everything.

The capability to get alerts would be great when CPU or RAM is high on an endpoint, or when a disk is failing. It would be great to get an alert rather than having to go looking for it.

It would be handy to have an MDM for Windows devices. It seems to be on their roadmap. They support Windows devices on the platform, but we should be able to wipe the machine and do other similar things through MDM.

I've been using JumpCloud for about eight years. I use it every day.

It has been rock solid for what I need it for. They had a few outages late last year, but they didn't affect my clients or me. So, as far as I'm concerned, it has been rock solid.

It is easy to scale. You just enroll more machines and more users. You get billed monthly on a high point of the number of users that you've got. So, it's fairly flexible.

It is used by small, medium, and large companies. It is suitable for all of them.

It has always been brilliant. Whenever I've had to contact JumpCloud for any reason, they've come back to me straight away. In six years, I've had to contact them three or four times, and each time, the issue was resolved relatively quickly and easily. There has not been too much difficulty with it.

Positive

It depends on what you're using at the moment. From my point of view, when I deployed JumpCloud for one of my clients, it was a case of getting the users into the JumpCloud platform and then enrolling their machines and tying the two together. So, it was relatively straightforward, but I understand that some deployments can be more complicated, such as if you're using Azure AD, etc. They're not impossible, but they just need a bit more planning than if you're using standalone machines.

The number of people required for deployment depends on how many end users you're deploying it to. I've deployed it for a bunch of different companies. Some of the companies had 70 people, and I did it on my own.

It generally takes half an hour per machine. The duration depends on how many machines you've got, what state the machines are in, and whether the machines need updating or anything like that.

It's a SaaS product. It doesn't require any specific maintenance. The agent updates itself on all the machines, and it just keeps everything up to date on its own.

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.

There are different tiers of this product, but the base product, called JumpCloud Core, is what I use with most of my clients. It suits us down to the ground.

When we first started looking at JumpCloud, we took a demo on Okta. At the time, JumpCloud did a lot more than Okta did, which was why we went with JumpCloud.

Device management was one of the reasons for going for JumpCloud. Okta was very much for the cloud and single sign-on, and you couldn't manage the devices, whereas JumpCloud actually managed the end-user devices. You could enforce encryption and other similar things, which Okta didn't let you do at the time. It probably does that now because we're six years on, but back then, it didn't.

Don't hesitate. Just do it. It is just fantastic.

I would rate it a nine out of 10. It does everything I need it to. It is a great product. It is not missing too much.

The tool is more like a Mobile Device Management solution that helps to manage devices. 

I am impressed with the product's remote access which allows admins to control endpoints which is a timesaver. 

The product needs to create its own self-service feature which has been requested by all the admins in the community. 

I have been using the solution for one year. 

The product is almost stable and recovery from outages takes around one to two hours maximum. 

I would rate the solution's scalability a six point five out of ten. We have around 250-300 users for the product. 

I have reached out to the support more than once. 

The product's setup is easy. The device enrollment can be completed in five to ten minutes. However, deployment involved configuring profiles by following documentation, which can take up to a day. 

The solution's deployment was done in-house. 

I would rate the product an eight out of ten. You can use the solution if admins are looking for one MDM for all endpoints, be it Linux, Windows, Mac, etc. The tool is nice in terms of pricing as well. 

JumpCloud enables different kinds of connections and enables employees or subcontractors not within the company to connect to our network securely.

A nice feature called patch management with different kinds of licensing is not included in JumpCloud. I'm also interested in sharing experiences with people in the local market, like engineers.

I have been using JumpCloud for one year.

I rate JumpCloud a nine out of ten for stability.

I'm working with smaller companies with around 28 or 50 users using JumpCloud.

We had contacted JumpCloud's technical support once because of a security issue and on another occasion because of a bug in the system. JumpCloud's technical support was very responsive.

Positive

There were some difficulties in installing JumpCloud. It took several weeks or months for us to deploy the solution.

We implemented the solution in-house.

We have seen an ROI with JumpCloud.

JumpCloud's monthly license costs around $25 for the complete solution. However, the lower versions' costs start from four dollars onwards based on the kind of functionality you choose. I rate JumpCloud a seven out of ten for pricing.

Before choosing JumpCloud, we evaluated the product Slack.

I am using the latest version of JumpCloud. One or two engineers are needed to do the maintenance for JumpCloud. I would recommend JumpCloud to other users.

Overall, I rate JumpCloud an eight out of ten.