Kandji
KandjiExternal reviews
External reviews are not included in the AWS star rating for the product.
Centralized endpoint policies have improved security and ensure compliant access control
What is our primary use case?
What is most valuable?
Kandji's best features are customer support, good blueprinting, and easy setup. The blueprint feature makes it easy to see everything from an at-a-glance view, and it makes sense when I'm looking at items one by one to see how they fall in the map.
Kandji has positively impacted my organization because it helps us be more secure and enforce compliance. It improves compliance by helping us remove admin accounts on local users.
What needs improvement?
I do not have information about how Kandji can be improved or any small changes that could make my experience even better.
For how long have I used the solution?
I have been using Kandji for seven months.
What do I think about the stability of the solution?
Kandji is stable.
What do I think about the scalability of the solution?
Kandji's scalability is good and it deploys fine across multiple devices.
How are customer service and support?
Kandji's customer support is really great, and they are nice people. I rate the customer support a 10.
What was our ROI?
I have seen a return on investment because it saves time managing endpoints.
Centralized device policies have saved our team time and control app access effectively
What is our primary use case?
My main use case for Kandji is that it is an MDM platform, so I mainly use it for MDM, controlling all of our company organization's devices, ensuring that the proper device gets the proper policy.
A really quick example of how I use Kandji for device management or policy enforcement in my daily work would be that I don't want certain people to have the ability to download Chrome extensions, so I just create a policy that blocks them from having to do so.
Another example is that we look through all the apps that people are supposed to have, and then the ones that we want them to have, we just deploy it on Kandji.
What is most valuable?
Probably the best feature of Kandji is their customer support; that's their best feature.
My experience with Kandji's customer support has been that it's really easy to get to a human, and they're really knowledgeable, usually just giving you the answer straight up. If I'm looking to do something that they can't do, then they just say it, and if they can, they'll find a way to get it to work for us.
Kandji has impacted my organization positively.
What needs improvement?
I think Kandji could be improved with a better UI.
For how long have I used the solution?
I have been using Kandji for about seven months.
What do I think about the stability of the solution?
Kandji is stable.
What do I think about the scalability of the solution?
Kandji's scalability is really good.
How are customer service and support?
Kandji's customer support is really good. I would rate the customer support a 10.
Which solution did I use previously and why did I switch?
I did not previously use a different solution.
What was our ROI?
I have seen a return on investment with Kandji, as I save time. Kandji has saved our team about 10 hours a week.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing has been normal.
Which other solutions did I evaluate?
Before choosing Kandji, I did not evaluate other options.
What other advice do I have?
My advice for others looking into using Kandji is to read through their documentation. I would rate this review a 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Clean, High-Performance Platform with Fair Pricing and Strong Support
You can integrate your SSO solution so saving stress with user names and passwords, and the performance of the system is really good. We've never had an issue with platform performance.
The pricing is fair and for us, the increased compliance for our security standards is excellent. They have implemented an AI system for support and some other bits. It's good so far.
Centralized security policies have streamlined remote troubleshooting and device management
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have around one year's experience using Kandji, focusing on managing users and creating policies.
What do I think about the stability of the solution?
Kandji is very stable, and I would rate its stability a 10 out of 10.
What do I think about the scalability of the solution?
Kandji has very good scalability.
How are customer service and support?
I have not had the chance to interact with customer support to raise a ticket, but I believe it is all great.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Blueprint-based management has enabled one admin to manage hundreds of devices efficiently
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Kandji for approximately three years while I was at Tango and Blackhawk Network in my previous job.
What do I think about the stability of the solution?
Kandji is stable and performs reliably.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.