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.

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.

The product was our main source of authentication and authorization.

We had various use cases. We used it as the LDAP source. We also used it as a single sign-on like SAML. We used it to enforce policies on various systems or even on employees' workstations, servers, and SSH control. We used it to execute on-demand jobs since it's supportive in scheduled jobs or on-demand scripts, and you can execute, for example, hundreds of servers at once. 

We were quite happy with it in terms of functionality and reliability.

The usual authentication and authorization, which were all controlled into one portal, are very convenient. 

You can script the deployment of the agent, which is very convenient as well. 

I like the fact that you can execute on-demand, you can schedule jobs, and execute scripts on demand on various systems, including Windows and Linux. That's a very powerful feature.

The product is stable.

Support is helpful.

It can scale well.

The pricing is reasonable.

Jump Cloud is more focused on the authentication and authorization part since it supports script deployments and stuff like that. It could dip into CI/CD tooling as well. That would be a very interesting part to see.

I worked with it for over two years in my previous job. The last time I used it was maybe eight months ago.

The stability is good. It was very rare when we had some kind of issues and mostly it didn't affect the authentication of the users. Portal features, for example, may not have been functioning well. However, it was very rare that anything would happen. They would schedule maintenance occasionally and warn you. 

I'd rate the stability eight out of ten.

It can expand. Obviously, the more you scale, the more cost you add. However, in terms of infrastructure on their side, I never had any issues with size. We were adding users or servers and had no issues.

I'd rate the scalability nine out of ten.

Support was okay. 

To set up the first time the LDAP and the SAML on certain applications, we asked their assistance. Sometimes, for example, if you have a Java application, you need to make sure that the Java Store certificates are updated as well with JumpCloud. Otherwise, they were quite responsive when we opened tickets with them. And even they jumped on calls with us and made support calls with us to assist us. They are very good.

Positive

I'm familiar with Active Directory.

Active Directory, obviously, is one of the top products. That said, you need to have a Windows infrastructure to deploy Active Directory. In my previous job and even our current present employment, we don't use Microsoft. You cannot use Active Directory without Microsoft. If you're an open-sourced company, for sure, you won't select Active Directly, even if it's one of the best.

If you are constrained with costs, obviously, you cannot go with a paid cloud solution, so you would go for an open source alternative. In terms of tech, we prefer convenience and stability in a product. 

JumpCloud supports Mac, Linux, and Windows, and it is more unified rather than Microsoft. 

Where I am now, we use Google Authentication like SAML and LDAP. However, we don't have features like JumpCloud where you have scheduled jobs and certain functionality. Although Google is stable and scalable, it costs money.

The initial setup has a medium amount of difficulty, especially if you want to make 2FA and stuff like that. Otherwise, they have good documentation on their sites, which is very convenient. Also, they provide the scripts to deploy the agent on Linux or PowerShell for Windows. You need to have a decently skilled team to deploy, implement, and maintain everything.

I'd rate the ease of deployment at a 7.5 out of ten. 

It depends on what are your requirements as well. If you want to enforce two-factor authentication that's where you have the complexity. If you want to get a bit fancy with the product, it might take a little bit more time. For example, for any authentication source, like Active Directory, you need to organize it well. Although the product might be good, you still need a good team to implement it, design it, and maintain it.

We had four people working on int at my previous company.

We used the enterprise version of the solution. 

The cost was around $15 per user per month. There were different brackets of pricing for the number of users on the solution. We were in the bracket that covered 300 to 500 users. 

The pricing is pretty competitive. 

For those considering the solution, the only concern is the cost. For example, let's say you are planning to scale to a thousand employees. It'll be very costly as a product. If you don't plan to go that much it's very feasible to use JumpCloud since, in terms of features, it offers everything.

Overall, I'd rate the product nine out of ten. I've been happy with its capabilities. 

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. 

It's a serverless environment. If you don't need Active Directory servers or print servers set up, you can use JumpCloud in lieu of having a server.

We use it for identity management and device management. It integrates with Office 365 and allows you to securely manage your devices, whether they are Windows, Mac, or Linux.

JumpCloud has allowed our organization to go completely serverless so that there is no need to be linked to a server in the office. This, along with Office 365, has allowed the organization to have staff who can work from anywhere, whether it's from home, a different state, or even a different country.

The interface is clean and user-friendly. Setting up new devices or setting up new users inside the system is easy.

Also, it integrates with Office 365, which is pretty much a must for our organization.

JumpCloud has a lot of functions and features that work for rolling out policies to different devices.

I would like to see some support for printers, especially network printers, through the application.  Active Directory allows for the adding and publishing of networked Printers through GPOs.  As far as I’m aware, JumpCloud only allows network printer adds through Powershell or command line scripting.   

My organization has been using JumpCloud for about two years.

Stability wise, I have not experienced any downtime with the system. It has been 100% reliable so far.

I believe JumpCloud could scale up pretty high, but I've only had experience scaling down. I started up with about 40-45 users on the system, and I have scaled down to about 10-15 right now.

I'm not sure how high it can scale up, but I could easily see 100-500 users through the system. I'm not sure if it goes higher than that, but it does not seem like it would be a problem at all.

Active Directory on a Microsoft server was previously utilized.

We switched because of the flexibility provided by JumpCloud with regard to where staff could work from. We did not have to be tied down to a server in the office. 

Also, the age of the server in the office was another reason. It was either time to upgrade the server or to move to something new.

It is pretty easy and simple to set up, so I would rate it at four on a scale from one to five. They have excellent documentation and plenty of how-to videos on YouTube.

I rolled out to about 40 devices over a period of a week on my own, working around staff schedules. However, you could roll it out sooner if you had the manpower. Usually, though, it takes a few days.

Maintenance is minimal. You set your policies for updates, and JumpCloud takes care of it. I've had zero issues with keeping up with patching.

Licensing cost can be anywhere between $2 and $18 a month depending on what you want to do.

Do your research on the product and figure out if it's going to be a solution that your organization is going to utilize, and make sure it's right for your company.

You can try JumpCloud for free. You can try it on one device or up to 10 devices for free without signing up.

I would rate JumpCloud at ten on a scale from one to ten because of the price, ease of implementation, availability of information regarding implementation, such as videos and articles, and scalability. It's easy to go up or down as per the needs of the organization.

Jumpcloud is used for single sign-on (SSO), cloud directory, authentication radius, which I use in multiple places in multiple cases, VPN radius, and network radius. The largest portion would be the directory, it is substituting the need to use the Microsoft typical environment or the Linux environment for the directory. It used to be the only two directory providers available, the Linux side or Microsoft Active Directory(AD). Now there are OneLogin, Okta, and JumpCloud competing with them and they are all cloud-based.

Jumpcloud has benefited our organization by showing us we don't have to have a Microsoft environment. If you're a Google shop, you can receive similar security that you would have in an Active Directory environment and more, because you have that radius built-in, you don't have to create other servers. You have the convenience of the day-to-day management of endpoints and users, which is all in one place because it does keep track of your devices and your users. Jumpcloud is a little bit more simple than using Microsoft, the simplicity of using it is a large benefit.

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. 

There are some key features that aren't there that would be possible with an RMM solution, but Jumpcloud is not meant to be an RMM, it's more centered around the directory, radius, and SSO. There are other features available, such as the integration with dual security which is really good. It produces a lot of functions, there are multiple functions and modules that you're using. There are plenty of features that are beneficial, such as insight reporting.

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. 

We had a feature board at one time for requests for features to Jumpcloud. I know Jumpcloud is not an RMM tool, but I think it's very close. It's close to being your whole IT department's one-stop shop. The only thing they're missing is a remote connection tool to its endpoints, alert, and monitoring. 

I want to be able to build my own package deployments and then run them for updates and some other operations. They have good capabilities, but you can't host your files. I would like them to either drop the file limitation or increase it to larger file sizes. This would allow us to be able to host and build out strictly from JumpCloud because right now you have to have an S3 bucket or some other place to load the file data from to do it. Whenever you're scripting, it can be a headache to have to deal with. It would be a large benefit if they allowed us to host our files on their system for deployment.

I have been using JumpCloud for approximately three years.

They went through a tough year this year with infrastructure and having some large outages. For any SaaS company, stability is the most important aspect of the business, they are a stable solution, but they should be more stable. A couple of years ago Microsoft had a bad infrastructure year and we had a lot of outages. In that year, Google had none. It can start to weigh down the company, I had to make a choice, do I choose Google because I have fewer infrastructure issues and have more stability or something else. Whenever you're faced with this type of issue, you have to make decisions and this is a priority for most users. Do are less concerned about new features, we want a solution that is very stable that we can count on. We know that most of the vendors have outages, but if you asked customers if they would rather have 10 new features or more stability, they would choose stability.

Stability is the most important aspect for anybody in the cloud right now. For us to keep pushing SaaS solutions, and sell SaaS them. Vendor stability is important and what do they deliver to customers as SLA for uptime matters.

The stability ofJumpcloud has become better. We still get notifications when there are issues, but every SaaS company has issues. Jumpcloud has taken this into consideration. We have a direct relationship with the CEO and some of the people that are right below him. I had a direct relationship with him from my business, and from knowing that they took our one-on-ones very seriously is a good thing. They will jump on a call with us even though we are a small client,  and it does not matter the size of our business or what we're contributing to in the world they will take their time to jump on a call and listen to our worries or concerns. They're very personal with their customers. It doesn't matter what level they are in the business, they will engage with you to make things better. When it came to stability, when we voiced our concerns, they listened. The stability has drastically improved.

The scalability of Jumpcloud is amazing. You could have a small business, such as I have, and you could grow over 500 people overnight, and it operates perfectly.

I've had businesses use this solution that was well into the enterprise level, which is usually considered a thousand or more users, and it works just as well as if there are 200.

The technical support from Jumpcloud is great. Everyone that I worked with walked me through whatever issues I had or found a root cause with me to be able to remediate. I've always had a good experience with them and they are fairly fast with their response. The support was good when I was on a free tier when my business first started to get off the ground. I would say that they were very responsive, even though I wasn't on a paid support tier. That shows a lot from their company that they do care about customers, even if they're only recently breaking into the industry. 

When I started my business, I did was using purely Google for a while. I have sold and administrated Microsoft for three years prior. I have used OES, OneLogin, and Okta. I've used a lot of different systems that do a lot of the same thing. 

I ended up settling with JumpCloud because of their ease of use and simple management. I could have 10 clients in my MTP, the place I go for management looks the same, everything I do is easily navigatable because everybody's console looks the same. Ease of management and ease of learning are two of the most valuable selling points. You don't have to have a Bachelor's IT degree to be able to use and learn Jumpcloud. They have a university and very good documentation, they've documented their system very well. They have videos for training out there which makes everything simple. If you're looking at an OES, Microsoft, or any other environment, you have to dig into the documentation, you have to do an intensive search for the answers. The age of those older environments is almost going to be gone soon with SaaS. Services, such as JumpCloud, Okta, or OneLogin are making everything more simple.

Jumpcloud is one of the easiest management tools for an environment to set up. However, any SSO is not easy. The APIs and the different portions of SSO authentication and what you need can be a challenge, but it's 10 times easier to implement than having to set up a Microsoft environment. 

If you are a new business it is the easiest tool to get your company going. If you're a small to medium-size business, if you start configuring it while you're a small business, it grows with the business well.

You can usually have a complete environment set up in a day's work easily. However, it can depend on many factors. For example, if you are using all the modules or the base modules, such as directory, users, and SSO. The environment that which it is implemented matters a lot. Many aspects can increase the difficulty level, such as the number of users, and how many desktops. I set up my business in less than two days or a day and a half.

Jumpcloud takes care of most of the maintenance on their end. I do environmental maintenance, such as patching all of the desktop systems. Jumpcloud has the capability to do patching, it does it for you. As far as updates,  the only thing you have to keep track of is your certs. For example, if you have certs with your SSO information or your radius that you're receiving notifications on, you're remediating and updating those as often as they come through. They are either yearly or bi-yearly. The overall maintenance for Jumpcloud is similar to a typical IT functional system where there is upkeep and you have to make sure you clean up old users that have been removed or lost access.  

There's a little maintenance, but I wouldn't say it's heavy. A Microsoft environment is a lot harder to keep track of and maintain than Jumpcloud. I'm not trying to pick on Microsoft, it's the only thing to compare it to. Nobody's using OES anymore on the Linux side. The next biggest competitor is probably Okta, and they have a  different landscape from Okta. Okta and JumpCloud are both awesome. They both have their plus and minuses.

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.

My advice to others wanting to implement Jumpcloud would be for them to be involved with their representative. All of the people have been very helpful at JumpCloud, and they'll usually help you find the answers you're looking for, such as use case scenarios. They have a JumpCloud lounge, Slack channel and it has been one of the best resources because you have manyJumpCloud administrators that are doing the same thing you do daily. If you can't find an answer, you have peers that have experienced it that can help. 

When Jumpcloud has an outage or when they have system issues, in the JumpCloud lounge, information is reported very fast and their status page is updated quickly. The whole environment that they have there, is very humble and they're customer service based on helping people out as much as possible. It is important to stay involved with the community, stay involved with your representative and enjoy the solution. It is an awesome software to use.

I rate Jumpcloud a ten out of ten.

I'm not married to any software. There are many different options out there, you have to find what's best for your scenario. This solution is great, the ease of management and all the opportunity of administration that it has in it, it is one of the best solutions out there, next to Okta.

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.

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.

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.

I have been using JIRA Service Management for approximately two years.

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.

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. 

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.

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.

I have not seen a return on investment from JumpCloud.

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.

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.