What is our primary use case?
We are using JumpCloud to provide services, such as identity, access management, access control to customers.
We can import the other users from directories, such as G Suite and Microsoft Azure, or we can do the entry of the users normally. We can control them by giving pseudo access or normal access. For example, how we manage the users from the Azure Active Directory.
If I compare our JumpCloud to Amazon AWS, we can have 20 percent of the services that we are using on the JumpCloud.
We can bind our G Suite directory and we can import any users whenever we want. The license depends on the number of users that we onboarded to JumpCloud or imported to JumpCloud. The user group benefits from applying the policies based on the user group. We have a JumpCloud package where we install it to the end-users system to see the logs of the system, to control if the machine's system has been lost by the user.
What is most valuable?
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.
Policies are created, we can apply them, and the agent acts as a domain. These are all the easiest aspects that we can do from JumpCloud. We can log in from an email for our devices, and we can have no restrictions. JumpCloud is highly secure.
I found the most valuable feature in JumpCloud to be Radius because most of the use cases, such as Amazon AWS, and if I compare this to JumpCloud, the only feature that stands out the most for authentication is Radius. When we use Azure, if we try to log in more than three times, we will be logged out and it will cache the IP address and the passwords, but JumpCloud will not do it. If we try a number of wrong attempts, it allows us to use other devices while logging the devices. Radius authentication means we use the same password to log in to the WiFi network. It is very easy to configure JumpCloud features in our firewall.
What needs improvement?
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.
There needs to be better device control. When it comes to a Mac device, it's very secure unless we add the agent on full then we cannot control it. When we do the scripts or automation from our side with the end-user system, I want to control everything from the JumpCloud, such as logs, because I wanted to know what is happening in the user's system to see if something is lost.
JumpCloud should improve the amount of storage offered. We should have cloud storage of at least 5 GB or 10 GB because, in our public IDs, such as GCP or in our public ID manager S3 bucket, they're giving us 10 GB of cloud.
For how long have I used the solution?
I have been using JIRA Service Management for approximately two years.
Buyer's Guide
JumpCloud
December 2024
Learn what your peers think about JumpCloud. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
What do I think about the stability of the solution?
If we deploy JumpCloud based on a complete stable plan we are pine to deploy. But when it comes to the performance, Of course. So if we keep achieving Our daily targeted plans, week targeted, or month targeted plans, be achieving, stable-wise. The performance will be stable.
What do I think about the scalability of the solution?
We have more than 8,000 employees that we are migrating to JumpCloud. We have onboarded 2,000 clients. We have API holdings where we are controlling six different levels of organizations with more than 11,000 employees.
JumpCloud is a scalable solution. Where we can provision or deprovision the solution it is scalable and easy to do.
We are using JumpCloud every hour and every minute because JumpCloud senior executives are in my current organization. I will be responsible for every user and every G Suite activation sync. In case we delete any one single ID that will be suspended on the G Suite, or Azure, or any other territories that we included. all the applications that are constantly suspended. I'm the person who's taking care of the complete strength of the users, as I am observing on my own browser who are logged out and who have reset their password. I can see the logs of complete users on every system that are logged in the JumpCloud console. In case they're not able to log in, I'll directly call them, then they forward the password and we do the reset. We're just trying to help them but the maintenance is not needed, based on the notification that we have configured, we will be receiving a notification, such as this user is logged out, they need a rest, or is not able to log in to this system.
How was the initial setup?
The procedure we follow to implement this solution in the scenario of one organization ff half a thousand plus employees. I am going to meet all HR staff, and whatever other departments they have. Based on the department and head of the departments, I will collect all the details, such as what are the stages of the application. That is the first step because we have to give an authentication on the first basis, based on the applications and we speak to the network team, about whether we can integrate the Radius.
We will start the system then onboard the teams one by one. We first test the busiest team and we end with the HR or administration teams last. Based on the onboard of all the users stored in the cloud, we can now have control. We have to create the SOPs, and demo sessions to share with the users. This implementation makes identification easier.
What about the implementation team?
The number of people used to implement the solution depends on the strengths of the people that we have in the organization.
If there are 500 users and under, I can control it on my own, but if it is more than 500 I need a team. I have to build a team to do it which will be of two to three people.
For the complete implementation, we may need at least six months but it depends on the user's strength, and how they react with their department heads.
When I'm doing an implementation, I'll explain everything to the end-user. "This is what I'm doing, and this is how it works, and this is how it helps you." users will understand in case any issues come, they will reach out to us, we will help them.
What was our ROI?
I have not seen a return on investment from JumpCloud.
What's my experience with pricing, setup cost, and licensing?
We are using an enterprise license for JumpCloud. We have purchased a license for approximately $3,000 a year, but we are charged more than $135,000 annually.
There are no additional costs but we have to pay per ID we have.
What other advice do I have?
I am a senior executive, and I manage the complete identity of users. I am providing the access to all the users and I control the devices and URLs.
When it comes to cloud maintenance, we are not maintaining anything related to the server, cloud-related, or network-related This is because the JumpCloud is hosted on the Amazon AWS. When it comes to JumpCloud, there is no maintenance needed. Everything will be a notification if a user logged out and their password is expired. We have a policy for everyone to follow and it is complex and strict. The users have to follow it. Before implementing anything, we will be informing the users they have policies on their system to follow.
I would recommend JumpCloud to others if they have Microsoft Azure already with a subscription or if you have an Amazon AWS, then you do not need JumpCloud. However, when we are looking for an easy level of identity management, I can suggest that, using JumpCloud. In JumpCloud we should see the end number of users, how many strengths we have first. For users over 500, we cannot use JumpCloud, we can use the G Suite only. When it comes to more than a thousand then we can use JumpCloud. Additionally, if they're using many applications JumpCloud is suitable.
Instead of providing the G Suite, we can provide it with JumpCloud. The organization, which has more applications, or more networks. For example, when it comes to branches if I own an organization and I have branches in a different city and I have branches in 100 cities. I will be using different locations, and IP addresses, we cannot use radius. When it comes to single organizations, such as a Google company that is sitting in a single place, in those places we can use a JumpCloud for a radius. In case we have automation, we can use JumpCloud. It can be very useful.
I would recommend this solution.
I rate JumpCloud an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.