When I use Kandji to erase laptops, I open the browser for Kandji, log in with my account, and figure out the name of the laptop in the Mac browser. I find the Mac and ensure it is connected to the internet. When it is connected to the internet, I click on erase the MacBook, and it performs the task automatically without requiring any additional actions from me.

When I check the specific applications installed on the MacBooks, it does not help me with anything beyond verification. We do not have control or a way to stop things from being installed on laptops, so we simply check when needed. We do not check day by day; we only check if we open a laptop and see something unusual.

Kandji offers excellent features, including the ability to erase devices remotely without needing to be in front of the laptop. I also appreciate the ability to check the specific applications installed on the MacBooks.

Kandji has positively impacted my organization because we are a large company with many people around the world. The remote capability is particularly valuable; for example, someone from Boston and I living in Portugal can complete erase jobs remotely. This capability has created a significant impact for our organization.

Currently, I cannot recall anything specific that needs improvement. However, I rated Kandji an eight because the laptop needs to be connected to Wi-Fi to erase it. If it did not require a Wi-Fi connection, I would rate it a ten.

My main use case for Kandji has been for approximately one year and a half.

Kandji is stable at the moment.

Kandji's scalability is good.

The remote capability of Kandji has saved my team time and helps us considerably, though I do not have specific numbers to share.

If you have a large company with many Mac users, Kandji is a good tool to help manage your devices. I would rate this product an eight.

My main use case for Kandji is device enrollment, and in my previous organization, I used Kandji as an MDM solution for managing and securing user devices.

A quick example of how I used Kandji for device management is by creating security policies, password policies, and managing FileVault encryption for device security.

In my experience, one of the best features Kandji offers is remote control assist, allowing me to take control of a user's device without needing any third-party software.

I value the remote control assist feature because it makes troubleshooting very easy; if a user is working remotely, it helps me to take control and perform troubleshooting.

Kandji has positively impacted my organization because it is very user-friendly, and among the multiple MDM solutions I have used, such as JumpCloud and Intune, Kandji stands out as one of the best for Mac devices.

Kandji stands out as one of the best MDM tools for Mac devices primarily because of its user experience, which is more user-friendly compared to JumpCloud and Intune.

I do not think Kandji needs any improvements; everything is very good, and as I mentioned earlier, I have used multiple MDM tools, with Kandji being one of the best.

I have around one year's experience using Kandji, focusing on managing users and creating policies.

Kandji is very stable, and I would rate its stability a 10 out of 10.

Kandji has very good scalability.

I have not had the chance to interact with customer support to raise a ticket, but I believe it is all great.

I did not previously use a different solution before Kandji; my previous organization was already using Kandji for Mac devices and Workspace ONE for Windows devices.

I have seen a return on investment from using Kandji because it saves time.

The time saved includes processes such as software installation, as previously we needed to take a user device remotely, but with Kandji, we can initiate software installation from the back end, which is a significant time saver.

Regarding pricing, I did not manage the licensing part because I primarily handled the admin console, so I am not aware of the costs associated with it.

My advice for others looking into using Kandji is that it is the best tool for securing Mac devices, creating policies, and managing devices; you can also manage your assets effectively in terms of quantity. I would rate this product a 10 out of 10.

My main use case for Kandji is securing and controlling the endpoints. A specific example of how I use Kandji for securing and controlling endpoints is that we are trying to be compliant with NIS 2, so we are controlling the endpoints with endpoint security and controlling security. We know what apps we have and possess total control over the devices.

The best features Kandji offers are evident when compared to my long-time experience with Jamf. Jamf is really complicated and brilliant, but Kandji covers 90% of what Jamf does in a much simpler way. You don't need to be a big IT operation to handle Kandji. It has ease of use and more automated functionality.

The factors that make Kandji easier and more automated compared to Jamf include the Auto Apps function, which is brilliant. It takes 20 seconds to push out a new app, and it automatically updates. This function really saves time. The pre-configured blueprints grant you the security level you need and are really automated to the sharpest form.

The features are constantly changing and they are working hard to bring in new things in Kandji, which is really appreciated. Kandji has positively impacted my organization because it saves us time. The support is really good. I would say that we maybe would have to hire one more person in the organization if we hadn't had Kandji. I think it saves at least an hour a day.

Kandji can be improved by constantly bringing new features. The Windows part needs a lot of work. I am pretty sure they are working hard to get that up and running, but we are very pleased that we have one system for both device platforms like Windows and Mac. In Windows, there are a lot of features we need because they have just started with Windows. It works and fulfills the base setup, but there is a lot that I think will come in time.

I have been working in the IT field as a manager for about 20 to 25 years.

Kandji is very stable.

Kandji's scalability is good. It is really good because it is important to have a system that you can grow in. I think Kandji is a perfect choice for growing small companies that become medium-sized or even bigger. I think it is really good.

The customer support is the best I have ever seen.

I have used most of them, including Jamf, which is too complex for SMB companies and has a really steep learning curve. In my position, I don't want to do everything hands-on. I need other people in my group to be able to do things, and Jamf has a really steep learning curve. I have used InTune too, and that has the same issue with a really steep learning curve and it is really bad.

Though I cannot give you any facts from memory, I have saved money in time. As I said before, there is approximately an hour a day in work hours savings.

My experience with pricing, setup cost, and licensing is that it is always hard to get budget for these things because management does not always see the upside of an MDM system. I think you have to package it with the security and compliance aspect, then it is easier. However, the price could be cheaper, not much, but somewhat cheaper.

Before choosing Kandji, I evaluated both Jamf again and looked at Mosyle. The conclusion was that we wanted one system for all devices, and that is why we chose Kandji, and for their support.

My advice for others looking into using Kandji is to do a demo. Ask Kandji to do a demo for a couple of weeks, try it out, and compare it with the others. That is enough. I think Kandji has found a spot where you can do 90 to 92% of what is possible in an automated way and made it easy. I think that is the bottom line of what Kandji does. I didn't find Kandji; they found me, and I think that was good. I would rate this review a 9 out of 10.

My main use case for Kandji is device management, providing end-to-end device management from the moment we receive the device to the moment it is in a user's hands and after, for managing updates, deploying apps, and more.

A specific example of how I used Kandji for device management involves multiple blueprints of devices: we had engineering spec devices, sales devices, and IT devices. Having a different blueprint for teams that needed their own customized available apps for them to download and install or for security management made it very easy to deploy the right tools, software, and permissions to the right devices. For example, engineers would have admin permissions and able to script the blueprint such that engineers got admin permissions, but nobody else did, made the deployment seamless. We deployed many scripts, and Kandji support was always amazing. They have been far and away the best to deal with, head and shoulders above all the companies that I have worked with to submit support tickets. Posting in chat or requesting a chat results in talking to an engineer within minutes; you cannot beat that.

In my opinion, the best feature Kandji offers is reliability. When we were acquired by Blackhawk, they used Jamf, so working in the same environment, I got to work with devices on both Kandji and Jamf. Now at my current company, we primarily use Jamf, and I must say, the simplicity and ease of management with Kandji cannot be overstated. It is reliable, a modern approach to managing Apple devices, and with features in blueprints, smart apps, and consistently reliable performance, I do not think Jamf really comes close.

While I do not have anything specific to add about the features, I do think there is a lack of flexibility in Kandji. However, that same rigidity is also what contributes to its consistent reliability and performance. It is much simpler to manage, and if a company were trying to manage devices with a smaller team, Kandji would absolutely be my choice over Jamf.

Kandji has positively impacted my organization by allowing a small team, of which I was actually the only member handling device management, to manage three hundred to four hundred devices efficiently. Automatic updates, patching, and easily deploying scripts to fix issues have empowered me and significantly reduced the complexity of managing all those devices by myself.

I see room for improvement in Kandji by adding more flexibility. By the time I stopped using it, they were starting to implement smart groups for app deployments, which seems like a step towards offering more flexibility, similar to Jamf. The simplicity and straightforwardness are its strongest attributes. Additionally, I think expanding the catalog of Kandji Auto Apps would be beneficial; they significantly reduced the complexity of managing the applications we pushed to devices. The fewer custom apps we have to upload, the more time we can focus on critical tasks in issue resolution or setting up the right policies upfront.

I have been using Kandji for approximately three years while I was at Tango and Blackhawk Network in my previous job.

Kandji is stable and performs reliably.

Kandji's scalability is quite good, though I do see a concern once organizations start getting really large and need more flexibility. The blueprint scheme works well in smaller to medium-sized companies but might present challenges in larger organizations.

The customer support at Kandji is phenomenal and is the best I have experienced from any vendor. The instant chat with engineers is an amazing feature. I rate the customer support a ten.

Kandji was the first endpoint management solution I worked with. We switched to Jamf eventually because we were purchased by a company that used Jamf.

Kandji definitely saved time, though I do not have specific metrics to share. I was managing over four hundred devices solo, and it made the task very easy to handle. My experience with Jamf showed that managing the same number of devices would be far more difficult. Thus, we definitely needed fewer employees, saved time due to the automations in Kandji, and avoided the need for additional endpoint management staff.

I did not deal with the pricing negotiations, so I am not super familiar with the costs directly. My IT director managed those conversations, but from what I understood, it was a bit more than Jamf, particularly at renewal time, but it was money well spent.

My advice for others considering Kandji is to embrace the blueprint model to the best of your ability. The more you stay within blueprints, the more reliable your experience and the less complexity you introduce into your organization, making management easier with a smaller team. While smart groups exist for when customization is necessary, blueprints are the easiest way to manage a fleet of devices. I rate this product a ten.

I use Kandji to support Mac devices by configuring them, deploying them, resetting remote support, app deployment, and security patch deployment.

Quick sync support stands out for me because it saves time with the user. Unlike other support tools, it is very fast and I can provide proper support.

Kandji has positively impacted my organization by providing remote and quick support.

This quick support has changed my team's workflow and efficiency because our company is a remote-first organization, so Kandji gave us a great and efficient way of supporting users across the world.