JumpCloud Reviews

My main use case for JumpCloud is as an MDM tool. JumpCloud is essential for my team in mobile device management, and I also use it as an Active Directory solution. I use JumpCloud to provide admin access, enable specific application sideloading, manage all software, and handle inventory management. My primary use case for JumpCloud involves application management and Active Directory functionality. I use JumpCloud for monitoring devices and providing specific access controls, including administrative access and application-specific controls, as well as resource sharing. I can track or lock out systems in case of loss or other security concerns.

An excellent use case for JumpCloud is addressing the management of a remote or hybrid workforce. A unique use case involves rapidly deploying devices to new employees without requiring them to come into the office. My team leverages pre-configured policies and zero-touch deployment to ship devices directly to employees, already configured and secure. This eliminates geographical limitations and ensures compliance from day one.

In a day-to-day context, the best features JumpCloud offers for my organization are the unified directory and device management. The ability to consistently manage user access and security policies for a diverse fleet of devices from a single pane of glass is critical for daily operations. It simplifies routine tasks including onboarding and offboarding and significantly strengthens security.

Integration capabilities are a key component of JumpCloud. JumpCloud integrates seamlessly with many common cloud applications through SSO and SCIM provisioning, which streamlines access and enhances security. For reporting, JumpCloud provides detailed audit logs and reports on user activity, device status, and policy compliance, which is crucial for security and regulatory compliance.

A key positive impact JumpCloud has on my organization is significant time savings. By centralizing user and device management, IT teams can reduce the time spent on manual tasks, potentially freeing up 20 to 30 percent of their time. Security is also improved, with specific metrics showing a reduction in security incidents due to enforced MFA and conditional access. Employee productivity benefits through seamless SSO and faster onboarding.

JumpCloud can be improved in several areas. Some users feel the initial configuration can be complex, especially for larger organizations, and better guided onboarding could be helpful. Additionally, while its reporting and integrations are strong, more granular and customizable metrics and real-time alerts would be beneficial for advanced use cases.

From my team's perspective, there is often a desire for even more intuitive administrative controls, particularly when managing complex policy sets. Enhanced integrations with specific industry-specific applications could provide even greater efficiency. It is about refining the user experience and expanding compatibility.

Another area for potential enhancement could be customer support and resources. While generally good, faster response times and more comprehensive or specialized documentation could further improve the user experience, especially during complex deployments.

I have been using JumpCloud for one and a half years.

JumpCloud is considered to be quite stable, offering reliable performance and consistent uptime for identity and access management. Any occasional incidents are typically addressed promptly.

JumpCloud's scalability is quite robust, designed to easily accommodate growing organizations and fluctuating user counts. It allows for seamless expansion without major disruptions to management or security.

Customer support is generally responsive and helpful, with various channels available. However, faster response times and more comprehensive or specialized documentation would be beneficial, particularly for complex queries.

Positive

I previously used a combination of on-premises Active Directory and several disparate cloud tools. The switch to JumpCloud was primarily driven by the need for a unified management platform, improved security with zero-trust capabilities, and better scalability for a growing remote workforce.

I have seen a significant return on investment. Metrics show a reduction in identity and access management costs, potentially between 40 and 60 percent. Time saved on onboarding and offboarding users is also measurable, leading to improved employee productivity.

My experience with pricing, setup cost, and licensing indicates that pricing can be considered competitive with similar cloud platforms, though licensing can become complex with different tiers and add-ons for various features. Setup costs are mainly tied to the time and resources needed for the initial deployment and migration, which can vary depending on the organization's complexity.

Before choosing JumpCloud, I evaluated other options, such as Microsoft Azure Active Directory and Okta. JumpCloud was ultimately chosen due to its comprehensive cross-platform management capabilities and its native zero-trust approach.

JumpCloud is typically deployed as a pure cloud solution, functioning as a public cloud-based directory and management platform. It is designed to replace or complement legacy on-premises systems, facilitating a hybrid model during transition, but its core functionality is cloud-native.

JumpCloud operates on its own cloud infrastructure rather than being deployed directly on a specific AWS, Azure, or Google Cloud platform by the customer.

I rate JumpCloud an 8 out of 10 overall, balancing its strong unified management and security features with the potential for initial configuration complexity. I choose 8 out of 10 because this rating primarily reflects the areas for improvement, such as the initial complexity and the desire for more granular reporting and specific integrations. While it excels in its core functions, addressing those specific pain points would push it closer to a 9 or 10.

Our main use case for JumpCloud is unified identity and device management. Since Mensa Brands continues to grow, we need one central platform to handle everyone's access and ensure all devices are secure across different brands.

A good example of how I use JumpCloud for unified identity and device management in my day-to-day work is during onboarding. When a new employee joins one of our brands, we can set them up with a single identity in JumpCloud, which automatically provisions their access to various apps and grants them the right permissions for their devices, streamlining that process significantly.

The best features that JumpCloud offers are Single Sign-On, which is probably the strongest feature as it lets everyone access all their apps with just one login, saving them considerable time and hassle, and conditional access, which is critical as it helps us ensure only trusted devices can connect.

Conditional access has helped our team by blocking a contractor who attempted to access sensitive data from an unmanaged personal device, eliminating that potential security risk before it could become a problem.

Patch management in JumpCloud has been quite helpful as it ensures everyone's systems are updated, providing another layer of security for Mensa Brands.

JumpCloud has positively impacted our organization by drastically improving our security posture with better control over access, and we are definitely saving considerable time with automated onboarding and device management, allowing us to focus more on strategic projects.

I think the reporting in JumpCloud could be improved as it takes a while to pull the exact data you need sometimes. I notice the Linux agent still has some quirks compared to the Mac and Windows ones.

More granular controls for specific policies and better third-party integrations with some of the niche tools we use would help to make my daily work even smoother.

I believe the mobile device management, the MDM side of JumpCloud, could be enhanced further for more complex scenarios, and a more intuitive user interface for certain administrative tasks would be beneficial.

I have been using JumpCloud for the last 1.5 years.

JumpCloud has been very stable in my experience. We have found it to be quite reliable with minimal interruptions, and any small issues are usually addressed quickly.

The scalability of JumpCloud is really good. We have grown quite a bit since we implemented it, and it has scaled with us without any major issues.

The customer support for JumpCloud is generally helpful. They have different channels and respond quickly when we need assistance.

Positive

We previously used a mix of on-premises Active Directory and some cloud tools. The switch to JumpCloud was mainly to achieve a unified platform for better security and scalability for our remote teams.

We have definitely seen a return on investment. The time saved on onboarding and device management is significant, probably a 75% reduction, and our security incidents have dropped close to zero, which is a huge positive.

My experience with pricing is that it is competitive, though licensing can get a little complex with different tiers and add-ons. Setup costs are mainly tied to the time and resources needed for the initial deployment.

Before choosing JumpCloud, we evaluated other options such as Microsoft Azure ID and Okta, but JumpCloud felt like the best fit for our specific cross-platform needs and zero-trust approach.

We have seen specific outcomes since implementing JumpCloud, cutting our onboarding time significantly, probably by about 75%, and security incidents related to unauthorized access have dropped close to zero.

More granular controls for specific policies and better third-party integrations with some of the niche tools we use would help to make my daily work even smoother.

My advice to others looking into using JumpCloud would be to clearly define your specific priorities, especially for cross-platform management and security, and ensure to thoroughly test the setup with your existing tools to ensure smooth integration. I would rate this product an 8 out of 10.

My main use case for JumpCloud arises from facing multiple challenges in controlling user access since 80% of our platform is Linux. I need solutions to control users and devices, and JumpCloud provides me with those solutions, making it very helpful for managing devices, users, groups, and resources.

I have been using JumpCloud for the last three years, having deployed it in my organizations for Windows, Linux, and macOS. I have the needed platform to support these three platforms, and I have more than Linux machines, so I needed directory services similar to Active Directory. Active Directory cannot support Linux machines, which is why I chose JumpCloud, and I have completely deployed JumpCloud in my organization.

The best features of JumpCloud include its support for Windows, Linux, and macOS, which is a standout feature for me. Additionally, deploying all policies through JumpCloud is straightforward, making it one of the best features for my needs.

The cross-platform support and easy policy deployment from JumpCloud have greatly assisted my team, especially since it is typically difficult to deploy services across various directory services on Linux. With JumpCloud, applying policies to my Linux agents or devices is easy, and I am happy with this capability.

When discussing additional features of JumpCloud, I can fetch inventory, check the history of machines, and capture details about the operating system, such as who is using it, its configurations, and installed software. These features are helpful for managing my inventory.

JumpCloud has positively impacted my organization by greatly enhancing my control over security, especially for Linux, Windows, and macOS devices after its implementation. I now have more secure control over my devices and organizational data.

The improvements in security after implementing JumpCloud have made my stakeholders very happy regarding my data security, as I could not secure my data before. Now, I can monitor user activities and implement policies to control resources better, which has been very useful for me.

If JumpCloud could add network-level security, such as blocking unauthorized websites, it could be very helpful for me.

I chose to give it a nine out of ten because I see the need for improved security levels in JumpCloud, including more security features. However, JumpCloud has many great features that support all operating system platforms, making it a nice tool.

I have been working in my current field for 16 years.

JumpCloud is stable.

The customer support provided by JumpCloud is fantastic, as they respond properly and provide solutions when required. Communication is great, and they can also respond over email, which enhances the support experience.

Positive

Before JumpCloud, I did not use any directory-based services. After implementing JumpCloud, it has been incredibly helpful for controlling users and resources while enhancing security, making me very happy.

I have seen a return on investment with JumpCloud, as the money saved is significant. If I had planned to deploy an entire machine on Windows, it would have been very costly. After implementing JumpCloud, I found I do not require Windows installations, which is very helpful and cost-effective, while also maintaining effective security levels.

My experience with the pricing, setup cost, and licensing of JumpCloud has been positive, as I am happy with the support provided, and this setup cost is effective. This is a major point of concern for management regarding costs and implementation, but from my technical perspective, it is very helpful.

Prior to choosing JumpCloud, I evaluated other options like Windows Directory Services for Windows and LDAP services for Linux. If JumpCloud were not available, those were the solutions I would have turned to. However, after implementing JumpCloud, I found it very manageable with a console that provides role-based access to users, which has been very helpful for my needs.

My main use case for JumpCloud arises from facing multiple challenges in controlling user access since 80% of my platform is Linux. I need solutions to control users and devices, and JumpCloud provides me with those solutions, making it very helpful for managing devices, users, groups, and resources. I give this product a rating of nine out of ten.

JumpCloud serves as my master Active Directory. I manage all user accounts and assets via JumpCloud, and we have access controls built into JumpCloud for managing cloud applications, using a single sign-on for many of our SaaS applications.

My main use case also includes using SSO with SCIM for integration, and we are using JumpCloud password management solution.

JumpCloud has positively impacted our organization by serving as our main Active Directory service, tying a lot of application access to JumpCloud, meaning users have to log in to JumpCloud to access those applications. If JumpCloud is down, many SaaS applications won't be accessible, and many users cannot log in.

In my experience, the best features JumpCloud offers are simple directory integration and good insights about our audit-related data for user login, which are available in the directory logs. We don't need to struggle to get those logs the way we do with Microsoft Active Directory, and we can use many filters in the dashboard to get those log details easily, along with a straightforward SSO setup that can be completed in just a few steps for many applications.

Whenever we are onboarding new SaaS applications or any new application our company is going to use, we simply set up the SSO. It's not a day-to-day setup, but when a new application comes, there is some work involved. The directory service logs are very useful for compliance audit purposes, and we use those on a monthly and weekly basis to fetch the reports, but not on a daily basis.

We started using JumpCloud Password Manager more than a year ago, and I feel some improvements are needed on this password management solution compared to other solutions, as we previously used LastPass. It feels JumpCloud needs improvement, especially since the browser extension does not always work properly and sometimes takes more time.

I have been using JumpCloud for four years.

JumpCloud is very stable. I don't have any issues with JumpCloud's stability or scalability; it scales very quickly.

JumpCloud scales very fast, and we have not seen downtime.

Customer support from JumpCloud is very quick. Since adopting JumpCloud, I have noticed specific outcomes including very fast support; we get immediate support if something is not working properly, and it has minimal downtime. I have never faced significant downtime on JumpCloud, although I think I've faced a couple of instances, but they were resolved very quickly, so there is no problem with downtime.

I previously used Microsoft Active Directory for a while, but it does not act as a cloud directory. Microsoft Active Directory is a directory service, and it lacks other features such as SSO, JumpCloud Password Manager, and access controls.

JumpCloud saves us money in some features, such as the password manager, as we can keep everything in one place, which definitely saves money for our company.

My experience with pricing, setup cost, and licensing for JumpCloud has been positive; we got a good deal for the setup, and I feel it was a good value.

Before choosing JumpCloud, I evaluated Microsoft as an option.

My advice for others looking into using JumpCloud is that if a person is looking for a directory solution that combines single sign-on identity and password management, this will be the best option. I would rate my overall experience with JumpCloud a 10.

My main use case for JumpCloud is managing a fleet of Windows and Mac devices. I manage the complete life cycle of the device from imaging to offboarding using JumpCloud, so when a new employee joins the company, the device gets enrolled with JumpCloud, any apps that the user may need are automatically installed via JumpCloud, and then the device is shipped out.

Because we're in healthcare, we're all about security, and JumpCloud gives us the ability to lock down the device and make sure only approved apps are installed, which is beneficial.

Recently, JumpCloud rolled out the ability to host apps in their repo, so I no longer have to host them myself for install. I just upload them to JumpCloud and push and they're good to go. I also appreciate that JumpCloud has a remote desktop included, which makes life very easy.

I'm in a company that's fully remote, and because we have no on-site location, having a remote desktop was important to me so I can provide remote support when needed or troubleshoot when needed. Having that built-in has been very nice and made supporting my end users significantly easier.

JumpCloud has given us a much more secure environment, and as we move toward a SOC 2 Type 2, having JumpCloud in place made it very easy to gather the evidence we needed to prove that we were doing what we should be doing.

We needed fewer employees, and by adding JumpCloud, we were able to remove the need for at least one employee because we had less hands-on device imaging.

Better management for iOS devices would be wonderful, so I could ditch a secondary MDM I use for my iOS devices that I manage. If I could bring everything to one pane, I think that would be a real improvement for me.

JumpCloud does what it does and does it very well, and there's always room for improvement. As I stated about iOS, giving them a nine is probably the best they could achieve.

I started using JumpCloud about three to three and a half years ago.

I experienced some bugginess getting joined. It did not initially recognize my microphone, and I had to reload the page a few times because it kept saying it was failing.

JumpCloud has scaled up and down with the ebb and flow of our business very well, and I have no complaints on its ability to scale or downsize as needed.

Customer service is fairly good, and sometimes it takes a little time to hear back. Service was better in the beginning, but as JumpCloud has grown, they have not leaned into their support quite as much as I hope they would. However, they do get back to you within a reasonable amount of time.

When I was onboarded, we moved from an MSP to an internal team, and the MSP was using a different MDM for each device type, whether that was iOS, Mac, or Windows. We tried to move to something that would be unified, and then eventually move to using the IDP portion of JumpCloud as well.

JumpCloud was purchased before I onboarded, so I did not handle the initial licensing. As they've rolled out new features, I have been in on the conversations on which ones to purchase and whether we needed to stick with the Platinum bundle that we were getting or if we could drop down. My manager made the purchasing decision on JumpCloud about two weeks before I joined the organization.

I did not use an implementation team.

JumpCloud delivered very strong ROI.

The biggest advice I would give to others looking into using JumpCloud is to test, because the biggest thing you can do to make sure it's going to work for your environment is to sign up for the free demo and test JumpCloud as much as possible to make sure it suits your use case. JumpCloud is a good product and it marks all the boxes that I needed it to. I would rate this review a nine out of ten.

My main use case for JumpCloud is being an implementer, which means that the user wants to migrate from an on-premise server to a cloud, so they use JumpCloud.

A quick, specific example of how I use JumpCloud for a migration project is that the user has a backend Windows Active Directory, and they want to control all the users that use company devices, such as a laptop or cell phone, and have them be managed. So, I suggest they use JumpCloud. They migrate from Windows Active Directory to JumpCloud, and I help them with the process, such as integration and how to bind the user to the endpoint and the device, such as a cell phone.

If there is any new user onboarding, I made a script to automate that. If the new user comes, it should be automated to sync to JumpCloud from the Windows Active Directory.

Based on my experience, the best features JumpCloud offers include support for most operating systems for devices and handhelds, such as iPhone or Android. The feature that I use most is that the user has only one portal to access the applications, such as SSO applications like Google Workspace and the web applications that support SAML or OpenID.

I find myself using the single SSO for all the applications the most because it is much easier for me to log in to one user portal, and then I can have access to all applications.

JumpCloud has positively impacted my organization because we can work more efficiently by focusing on the one user portal to use the applications.

I think JumpCloud can be improved by enhancing their support because it takes so long to get feedback from them if I have a problem with a client to solve their problem.

I would like to add more about the needed improvements, perhaps a tutorial on how to use some new features, such as RADIUS, or use cases that show the best practice on how to solve some cases.

Customer support should be enhanced, especially the response time which should be much faster than it is now. I think it is slow.

I have been working in my current field for about three years now.

JumpCloud is stable.

The scalability of JumpCloud is good because the JumpCloud backend is supported by AWS, which is around the world.

I think JumpCloud can be improved by enhancing their support because it takes so long to get feedback from them if I have a problem with a client to solve their problem.

I would appreciate more content about the needed improvements, perhaps a tutorial on how to use some new features, such as RADIUS, or use cases that show the best practice on how to solve some cases.

Customer support should be enhanced, especially the response time which should be much faster than it is now. I think it is slow.

I did not previously use a different solution before JumpCloud; from the beginning, I used JumpCloud.

I have not seen a return on investment, and I cannot share relevant metrics because I am just an engineer.

My experience with pricing, setup cost, and licensing is that JumpCloud licensing is based on how many users they register in JumpCloud, and each user can have multiple devices, up to three devices.

I did not evaluate other options before choosing JumpCloud; there is no other option.

JumpCloud is deployed in my organization as a public cloud.

I use Google Cloud as my cloud provider.

I would advise those looking into using JumpCloud that it can give you more visibility about your device, inventory, control of your application, and so on. I think it is many things in one platform. I rate this product an 8 out of 10.

I primarily use JumpCloud for managing multiple cloud platforms with a single set of credentials. It is utilized by my clients who work on platforms like AWS, Azure, and GCP, and who need seamless access across these. 

It helps avoid the need to manage multiple credentials by using unified credentials for various cloud accounts.

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.

I would like AWS to integrate more cloud platforms with JumpCloud, such as Alibaba or Oracle. This would be helpful, especially for AWS users, by providing broader support for different cloud platforms and private cloud environments.

I have been working with JumpCloud for almost five years.

I rate the stability of JumpCloud ten out of ten. The stability has been very valuable for my customers, especially in scenarios where they are using more than one account. I often recommend AWS SSO or open-source JumpCloud for clients needing a stable solution.

The scalability of JumpCloud depends on the platform. With AWS SSO, it is ten out of ten; however, its scalability may vary with third-party tools based on subscription type, number of accounts, and users.

I have not needed to contact JumpCloud's technical support since the setup and usage are quite straightforward and well-documented.

Neutral

The initial setup of JumpCloud is very easy. I need to download SAML configuration and integrate it with the JumpCloud platform. It's a simple process, especially with AWS providing guidance through documentation and videos.

AWS charges per user, which can be costly if I have more than ten users. Third-party platforms tend to be cheaper than AWS. However, it depends on the features I receive for the price.

For users with fewer than three accounts, you may use AWS's switch role feature instead of JumpCloud or SSO. However, for multiple cloud platforms or users, JumpCloud or SSO is advisable for managing accounts seamlessly. 

I rate JumpCloud eight out of ten based on the pricing.

I have been managing all the users across the organization with JumpCloud, where I have been accessing their devices and their access to different portals like AWS and other applications as well.

I had a lot of users, and for the laptops, some users were using Mac and some users were using Windows machines, so I was able to assign that there itself.

With the Terraform provider and some automations, I was able to put every user directly into JumpCloud itself.

In terms of managing JumpCloud or users, I was able to manage 300 people with just two people.

The good thing about JumpCloud is having something where in a single tool, I can manage everything: users, groups, their permissions, their different applications, integrations, and the devices.

I think JumpCloud positively impacts the organization because all employees just need to remember one credential, not more than that.

For user positivity, I noticed that the users don't need to log in to all different tools.

There is always room for improvements.

I have used JumpCloud for more than a year.

The user interface was good.

Customer support was good; I was able to get prompt responses from them.

Scalability was good; I never found an issue in terms of scalability.

Customer support was good; I was able to get prompt responses from them.

Before JumpCloud, I checked Okta, AWS single sign-on and other tools as well.

It was a direct purchase.

It was managed directly with JumpCloud itself, so it was all being managed with JumpCloud.

If you are using JumpCloud, then do not use any other tool.

I think I have covered everything and I am all covered. I think this was the first one I used directly. I would rate this review an 8.

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.

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.

Neutral

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.