Kandji Reviews

My main use case for Kandji is administering our iOS devices and Mac OS devices.

Kandji has positively impacted our organization by making it so we feel confident in our security structure, and we feel confident that we can pass SOC 2 every year because we know that Kandji is doing what it says it's doing. Kandji is so user-friendly that nobody at our company has had complaints about it. In contrast, when we used Intune, there were complaints all the time that certain apps weren't updating or it was locking people out of apps because they hadn't been updated, and since we were using Intune, they weren't allowed to update their own apps due to us implementing some other security configurations.

Kandji offers really easy-to-use features, including a user interface that stands out. I have used Intune in the past for Macs and iOS, and it is so difficult that I would never recommend using it again. The deployment of different applications to devices is really easy, and they actually came out with some updates over the past year and a half that made it even easier.

What makes the user interface of Kandji stand out compared to other solutions I have used is that the graphics are much easier to understand. I appreciate how when I'm creating a blueprint, the way I used to do it in the past had just a whole list of things that I could configure one way or another. However, the way they made it now is based on a graph that goes from left to right, indicating what devices will all get this, and then I can give it an and, if, or statement, and then add more parameters. Additionally, I really appreciate how it has features to help me configure things where it walks me through the process, and it is really easy to get help. If I am ever stuck, I can hit the contact support button, and somebody can see my entire Kandji platform as long as I give them the approval on our system, and they would walk me through everything, making me feel supported even in those times when I don't fully understand how to do something.

One area for improvement for Kandji would be having a bigger suite of applications. I noticed that some of the niche apps our data software firm needs were not in the regular library. We were able to use the custom app feature to create those apps ourselves, but I would love it if Kandji could expand the library. I also wish Kandji could lock down different ports on MacBooks based on which ones we wanted to shut down, and I hope there is an easier way to sandbox people's bring your own device devices because when we're doing SOC 2, it really wants us to sandbox things so that if someone were to take a device that is not ours, we could delete just our data off there and not theirs.

An improvement needed for Kandji would be the ability to remote into devices. I would appreciate something that is really reliable for that without having to buy third-party software.

I have been using Kandji for the last three years, two of those years actively.

Kandji is stable.

I'm not certain about Kandji's scalability since we have remained at about the same headcount the whole time I was at that company.

Kandji's customer support is really good. They got back to us really fast and were always able to help us with our issues.

Previously, we used Intune, and we switched because they do not want you to use Macs, making it user-unfriendly. Intune does not deliver on many features for Macs. For instance, if I import a Mac and push out a configuration file stating a pin needs to have certain characteristics, it would fail to execute that. There were always different errors when I tried pushing out an app library, and the scripting requirement complicated things for me, which led us to switch to Kandji.

My experience with Kandji's pricing, setup cost, and licensing was really good. Since we're a small startup, they offered us some really good pricing, likely because they think that when we become a big company, we will still be using them. The whole process was really easy, and the people were down to earth, which I enjoyed.

I have seen a return on investment with Kandji since we only need one person for IT support, whereas other companies need a whole fleet. For me, onboarding and offboarding people with their Macs, since we use mainly Macs across our organization and maybe a couple PCs, would require another person if I had to use Intune for all of these tasks. I handle laptop deployments within 20 minutes, and once a month I might spend an hour changing some configurations within Kandji. This definitely helps us to ensure that we only need one IT professional to manage all system administration and IT support, including using Kandji and managing it.

Before choosing Kandji, I evaluated other options, including Jamf.

Since switching to Kandji, I save at least three hours a week just for app updates compared to Intune. On Kandji, I can decide whether to automatically push updates for any particular app to all devices and select the date I want that to happen, and it does its thing. In Intune, I would have to go and update the applications, the version numbers, and sometimes delete the application and push a whole new application because I honestly think it's because Intune doesn't want you using Macs and prefers that you use PCs. They have no incentive to make Intune work well with Macs.

My advice to others looking into using Kandji is to definitely give it a try. See if you can get a free demo and maybe a free trial and experience it for yourself, and you won't have any regrets, especially if you're moving from Intune or anything else to Kandji. If you're considering Jamf, it is a lot more expensive, so unless you have very niche reasons needing Jamf over Kandji, I highly recommend saving a bit of money and opting for Kandji. I would rate my overall experience with Kandji a nine.

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, where I manage devices, deploy applications, and policies.

A specific example of how I use Kandji for device management is that I deploy applications for departments, such as specific libraries and apps for engineering, and I also monitor computer health using bash scripts. If the computer battery is dying, I am informed, and if storage space is running low, I am informed as well.

The best features Kandji offers are easy management and support, as my organization has more than 300 devices, and while competitors like Jamf are far more complicated, Kandji does everything we need out of the box. This allows us to focus on providing quality of life services to our internal customers, then figuring out how to manage the platform.

The features of management and support stand out for me compared to other platforms primarily due to ease of usage. You do not have to be a fully technical expert on Kandji to use it, but if you are a skilled technician or engineer, you can accomplish a lot without much work, only with a few clicks.

Kandji has positively impacted my organization by increasing our security, reducing our resolution times, and ensuring that all employees who work from home have their computers working from day one. Kandji has zero-touch deployment, which makes our work significantly easier.

The resolution times have reduced significantly. Before Kandji, while using InTune, which was our previous management system, we took about 30 minutes for troubleshooting. Now, since everything is standardized in an easy way, in 5 minutes or less, we have all the information about the computer, whether we need to change it or if we should wipe it.

I think Kandji can be improved by having some kind of internal AI that allows us to build policies. I know they have an AI, but an AI with this feature would be amazing.

I have been using Kandji for four years.

Kandji is stable.

Kandji's scalability is perfect, as my organization grew from 180 to almost 300 devices with no bottlenecks.

The customer support for Kandji is perfect. I had multiple questions regarding application deployment, SAML deployment, and other kinds of deployments, and their support was very smooth, both human and AI. I would rate the customer support a 10 on a scale of 1 to 10.

Before Kandji, I used InTune. The main factors for switching were pricing and zero-touch deployment.

I have seen a return on investment, with relevant metrics showing that we saved significant time. We went from one hour for resolution time per device to 15 minutes, allowing us to save more than 50 hours of support time in a year.

My experience with pricing, setup cost, and licensing was very smooth. The pricing was cheaper than Jamf and matched other competitors, so we are satisfied. The setup was very easy, and licensing is very simple, fitting our organization's needs.

Before choosing Kandji, I evaluated other options, including Jamf and InTune, and looked into the most popular options in the market.

My advice to others looking into using Kandji is to try it out and see if it will fit your organization, because usually it will. This way, you can focus on more important projects that bring more value to the organization, knowing that your computers will be safely handled. I would rate this product a 10 out of 10.

Kandji is used in our organization to manage all of our Mac devices.

Kandji is an MDM tool which we use to manage our devices. For example, we set up our devices and directly enroll them in Kandji from the AVN, and then we can manage them from there. We can check the users' applications, redeploy applications on the user's MacBook, reset passwords, lock the MacBook, check disk encryptions, see all of our deployed applications, and deploy any policy or script we can run from a remote device.

When I see Kandji for the first time and encounter an issue with a user's MacBook, I first go on Kandji to see all applications they have, how their disk encryptions appear, and which OS they are running. I check everything from there, and I also send OS updates from Kandji. If I go deeper into anything, creating a script to run on a device is very easy. The policies we have set up differ for US devices and new devices, as well as VPN connections. We have different teams where specific applications are sent, and this setup is very friendly and easy to use for us, making our work easier.

We use Kandji in our organization as a public cloud solution.

Kandji's user-friendly interface is a valuable feature. In our terms, we can see that you can easily learn how to use Kandji. If you see it on the first day, you can use it fast with very correct results. If I run any script, it shows me the correct process, and then I can also check on the user if it has been successful. These are good features, and we can also monitor all of our devices, including MacBooks.

Kandji has positively impacted our organization by making it easy to manage all of our MacBook devices and applications. We find it easy to set up devices in about ten minutes. If I need to provide a new MacBook to any user, it is set up in just five to ten minutes, which makes our work easy, and there are no issues with Kandji when we use the device.

In Kandji, I see a drawback related to the remote wipe function. When we need to wipe a MacBook, sometimes the remote wipe command works, and sometimes it does not. This is a drawback because when we remote wipe a device, it should work immediately. However, it often takes more than thirty minutes to execute the command, and sometimes it fails.

The only improvement needed in Kandji is related to the remote wipe issue.

In this organization, we have been using Kandji for more than three years.

Kandji is very stable.

Kandji's scalability is very good in our organization. It is very easy to use, and I have great appreciation for Kandji.

Customer support is very easy. You just go to the help section and can chat directly to get instant support. You can share screenshots of the problems you are facing.

Before Kandji, we used ManageEngine and JumpCloud.

Before using Kandji, it took longer with other tools for Mac such as JumpCloud, where we faced many issues. We had conducted the POC, and it was not easy to use. We needed around forty-five minutes to an hour to set up a new device. With Kandji, we are able to do it in just five to ten minutes, where we only change the name and set it up while Kandji installs all of the necessary applications.

The pricing, setup cost, and licensing experience are good. It is cheap, and we do not encounter any hassle during setup. They help us initially, and after that, we make improvements one by one until we become Kandji experts.

We have seen a return on investment in terms of money saved, time saved, and the other benefits of it being very easy to use.

The pricing, setup cost, and licensing experience are good. It is cheap, and we do not encounter any hassle during setup. They help us initially, and after that, we make improvements one by one until we become Kandji experts.

We evaluated all of our MDM solutions including ManageEngine and JumpCloud, and then we switched to Kandji.

I will advise others looking into using Kandji that it is very easy and good for you. Once you use it, you will feel the difference. I would rate this product nine out of ten.

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.

Our main use case for Kandji is to manage macOS devices in a large fleet and to handle endpoint management for Macintosh devices.

A quick specific example of how we used Kandji to manage our macOS devices involves reviewing the check-in policies of the devices active on our infrastructure, along with the need to patch certain applications on a time-to-time basis, and managing the macOS upgradation process as well. We have used Kandji for application deployment and macOS upgrade.

In addition to our main use case, we have also been leveraging Kandji features such as Zero-touch deployment and custom enrollment for our Macintosh devices, which have been crucial in setting up new Mac infrastructure and the enrollment methods.

When discussing the best features Kandji offers, we find that automated compliance through Blueprints is a key advantage, as we have been using Blueprints to enforce policies automatically, ensuring devices stay compliant with security standards and providing real-time remediation. Besides that, we have been utilizing inbuilt security monitoring for macOS which is really helping us detect malware and suspicious activity, combining both MDM and security in one platform. Overall, security templates, CIS benchmark compliance, and real-time device insight are incredibly useful for us in managing our Macintosh devices in a real fleet.

Kandji has positively impacted our organization by ensuring that we are always up to date with the latest standards of allowed operating systems for security and compliance. The user interface that Kandji provides for macOS admins is also straightforward and neat, making it much more flexible, customizable, and enterprise-friendly.

I believe Kandji can be improved by integrating certain AI that assists in navigating troubleshooting for instances where there are management issues or communication gaps between API and the device in Jamf and Kandji. This integration would be extremely helpful, and with the latest DDM approach, we could also set up more profiles in Kandji using the DDM explorer. Overall, I think Kandji is a very helpful tool and any improvements would focus on adding AI as well as enhancing the UI for more granularity in function and payloads.

I have actually used Kandji for close to a year and a half since we have done the POC.

Kandji is stable.

I think Kandji's scalability is good, with no complaints since our automated device enrollment structure remains the same, making its scalability comparable to any leading MDM on the market.

Our experience with customer support has been very positive; they have provided us with great service.

We previously used Microsoft Intune before switching to Kandji.

We switched from Microsoft Intune to Kandji because we noticed Kandji gives us more granular control over devices, particularly in terms of UI and management capabilities, allowing us to receive faster logs and outcomes for deployed policies and configuration profiles.

After switching to Kandji, we have seen a return on investment, specifically in human resource savings. Previously, managing close to 5,000 macOS devices with Microsoft Intune required a team of six people, but with Kandji, we now need only three employees, significantly reducing our workforce. Moreover, we have saved money on human resources, leveraging features such as Zero-touch deployment and Blueprints that save us time and support efforts, resulting in fewer human hours required.

In my experience, the pricing for Kandji is very competitive, with a setup cost that is not too high compared to other MDM solutions. While it might be on the expensive side compared to Jamf Pro, it is closer in pricing to other MDMs such as Microsoft Intune, which comes with the EMS E3 license, making it potentially pricey for startups, yet a good cost for established enterprises.

Before choosing Kandji, we evaluated other options including Scalefusion MDM and Jamf Pro.

After using Kandji, I have noticed improved compliance rates and time savings, particularly with features like Gatekeeper and FileVault that need to be checked and compliant, and with Bootstrap Token assisting during OS upgrades. This has saved us a lot of time compared to other MDM solutions.

If I were advising others looking into using Kandji, I would recommend starting with a strong Blueprint strategy and avoiding the creation of a single giant blueprint for everything. It is always better to segment it by department, device type, and risk level. Additionally, I should prioritize compliance first and not configuration, focusing on maintaining the ideal state for devices over just the initial setup. I also suggest utilizing Kandji's auto-remediation instead of manual fixes, aligning policies with our organization's baseline based on CIS, and employing Auto Apps wherever possible.

I have covered all my experiences with Kandji. Overall, it is a really great tool with excellent scalability and granularity options. It serves as a strong choice for any enterprise looking to integrate Kandji into their operations. I would rate this review an eight out of ten.

My main use case for Kandji is to manage Mac operating system laptops and desktops. For managing my devices, I create a Blueprint, connect the machine with any Blueprint, and manage all the configurations through the libraries and parameters.

I consider Kandji to be a centralized tool to manage MDM, which stands for mobile device management. We use it to manage desktops and laptops, and it is also working as an asset inventory. The best features Kandji offers are Blueprint, libraries, parameters, and custom scripts.

I find myself using all of Blueprint, libraries, parameters, and custom scripts, but I use the custom scripts mostly. The custom scripts stand out for me because they help with installation tasks, uninstallation tasks, and configuration settings for very customized applications. We use custom scripts for password resets, password changes, and tasks to keep or remove files.

With a Blueprint, we have a set of libraries and parameters that can be used to manage the laptop or desktop. For anything not covered by the Blueprint, we can use custom scripts. Recently, we used custom scripts to configure and install CrowdStrike, which is a firewall tool. There are many useful things available through custom scripts.

Kandji has positively impacted my organization because many things happen through Kandji, especially on the laptops and desktops at the infrastructure workspace level. It saves time to improve security, and for example, vulnerability management was recently added, which saved time in figuring out the vulnerabilities.

One way Kandji can be improved is through pricing, as other market providers comparatively have a lower price. Kandji needs to work on its pricing.

The major issue is that our environment is for high trading frequency, and we cannot shut down the system during daytime or business hours, while Kandji updates the system OS during daytime. We do not have a schedule for operating system updates feature in Kandji, which could be added.

I have been using Kandji for nearly five years.

Kandji is stable.

Kandji's scalability is good, and there are no issues with that.

The customer support only supports through chat, so if they set up calls or more ticketing facilities, that would be helpful.

My experience with pricing, setup cost, and licensing is that we are using nearly 100 machines in Kandji, which comes to around more than 10,000 dollars. I do not remember exactly, but it comes to around nearly 10 dollars per server, even more than that. Sometimes, we can check with other vendors who are providing it for less, so pricing could be less.

Regarding return on investment with Kandji, it is acceptable for now, but I do not have any metrics to share exactly.

My experience with pricing, setup cost, and licensing is that we are using nearly 100 machines in Kandji, which comes to around more than 10,000 dollars. I do not remember exactly, but it comes to around nearly 10 dollars per server, even more than that. Sometimes, we can check with other vendors who are providing it for less, so pricing could be less.

My advice for others looking into using Kandji is that if you are looking for a stable environment management tool, Kandji is good. I would rate this review an 8 out of 10.

My main use case for Kandji is that within my organization, I have a Mac as my work laptop, and Kandji is used for self-service platforms so that we can download tools, as well as secondly, automated updates of tools such as the browser or the macOS version, so it is a security platform that is used for Mac administration, of which I am an end user of it.

A specific example of how I use Kandji in my day-to-day work is that rather than having to watch for updates to Google Chrome, the browser I use, or updates to the OS, Kandji notifies me of that, and then it comes with an automated pop-up so that I can upgrade to the latest version, allowing me to quickly update instead of needing to check for updates myself or potentially vet them from a security standpoint.

In my opinion, the best features Kandji offers are its UI, which is very clean and clear to use, not overly cluttered, allowing me to see the icon of all the different apps that I can install, and when I click on the little icon in my toolbar, it shows me any updates which I am able to install, making it very easy to use.

The clean UI and ease of use definitely save me time, probably cutting the time in half for trying to figure out when to install updates myself, because the notifications are pushed to me, which is good since I want to keep my system up to date without interfering with my workflow.

Kandji has impacted my organization positively by definitely increasing security because it notifies you when an update is ready to be installed, and if you do not install it within a reasonable time frame, it would automatically install it, which is good, and it probably has saved at least 30% of my time from manually having to look for updates since it just notifies me when the update is ready.

Kandji's automatic installation feature ensures our team's compliance or security posture, as it makes sure we are up to date and all on the same version of a particular tool, which is very important for a technical IT team to avoid differences that might affect functionality.

I have not been involved in the purchase process of Kandji, but I understand it is very Apple-centric and they have very recently come out with support for Windows or Android, although I do not believe the features are still on par with their features for Apple.

I have been using Kandji for two years.

Kandji is highly stable, and I have never had an issue with reliability in the last few years of using it.

Kandji handles growth easily for our organization as it allows purchasing additional licenses for further users, so I have seen no scalability issues.

I have never interacted with Kandji's customer support, which reflects the tool's high reliability and the lack of need to do so.

Negative

I previously used Jamf Pro in another organization and believe my organization currently uses Kandji because our fleet is on macOS and Kandji is optimized for Mac.

I have seen a return on investment with Kandji, estimating that time saved is at least 20 to 30%, as individuals do not have to figure out which security updates to carry out themselves since the notification is pushed for them to review and install.

My experience with pricing, setup cost, and licensing is that their pricing structure is bucket-based, requiring licenses to be bought in large groups, which is not an issue for my organization due to a large employee count, but could be a concern for smaller organizations, and the pricing is not published publicly, requiring interaction with sales representatives for details.

I highly recommend Kandji to others looking into using it since I have not seen any game-breaking issues; it is highly reliable, scalable, improves security, and reduces the time individuals need to spend on system configuration for security updates. I would rate this product a 9 out of 10.

My main use case for Kandji is MDM management, so managing our Macs and iOS devices in a corporate enterprise environment.

I can give you a quick, specific example of how I use Kandji for MDM management in my organization: we use it for zero-touch deployment. The idea is that a user is able to be sent a computer, and they're able to open it up and get started on day zero or day one for core access. Kandji allows us to enable that clean install method, a nice user experience, and allows us to onboard the user smoothly.

Kandji has positively impacted my organization by allowing us to better assist and it allows for a better user experience, a better kind of fleet management. This includes better core access, better day one management, better user experience, and collecting and recollecting or deploying and recollecting the resources makes it easier too because it's an inventory tracker.

I can tell you more about how it improved day one management or user experience. It took a lot of work to get there, but the Blueprints on Kandji's side essentially allows for us to configure various bundles or various software that an engineer or a salesperson would get because something an engineer would get is definitely different than what a salesperson would get. As long as the correct data is coming from a source of truth like an HRIS system and being passed down to an SSO system like Okta and then into something like Kandji, it allows us to better map the user experience and allow us to use Blueprints for those core groups for core applications. This allows for us to have a better user experience at the end of the day because a new hire comes on board, they open their laptop, they are logging in with their login, and they have all the software that they need already installed and configured. It will give them a splash page and run through the installation, but once they're let into the homepage desktop, they're able to then do what they need to: log in and start the day. The company branded background is a nice touch.

The best features Kandji offers are the UI, the ease of use, and the ease of deployment.

What stands out to me the most is that the UI is very user-intuitive, so it's easy for the user to pick up, whereas something equivalent is a bit more convoluted and buried where you need to get to the items you need. Kandji allows for someone with very limited IT knowledge to be able to go in and manage fleets, which I appreciate because it gives everyone a chance to learn.

Kandji can definitely be improved by the complexity. I feel we cannot necessarily tweak the Blueprints in the ways that we need to or there are just complex one-off situations where we need more customization and more ability to run custom scripts. Although there are ways to do that with Kandji, I feel it could just be improved.

I have used Kandji on and off for about one to two years.

I would give others looking into using Kandji the advice to fully vet your solutions and also be able to understand that situations that you may not have or see now will come up in the future. This is kind of preparing for a worst-case scenario and seeing what software is going to help you out when things are necessary or dire. For example, a CEO gets locked out of his laptop or a CEO loses his laptop. You need to be able to remediate situations immediately. We need a software that is not going to sit on a fifteen-second server timer to wait to fire off commands. We need something that we can action now. I would say be prepared for all situations. Be considerate of your future growth too. It is not just current status, but where the company is going to be in five to ten years. Also, you need to find an MDM solution that is going to be working alongside you, not against you during that time.

I think Kandji is a great software. I think it is very beneficial in the field and I feel it is a great competitor because of the UI, the ease of use, and the ease of deployment. However, I feel it can be more complex, it can be more robust. Kandji can build more with the APIs and they can allow for further customization for end users. I would rate this review as a seven overall.

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.

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.

I think Kandji could be improved with a better UI.

I have been using Kandji for about seven months.

Kandji is stable.

Kandji's scalability is really good.

Kandji's customer support is really good. I would rate the customer support a 10.

I did not previously use a different solution.

I have seen a return on investment with Kandji, as I save time. Kandji has saved our team about 10 hours a week.

My experience with pricing, setup cost, and licensing has been normal.

Before choosing Kandji, I did not evaluate other options.

My advice for others looking into using Kandji is to read through their documentation. I would rate this review a 10.