Learn about Kandji's Custom App Feature.
Kandji allows you to upload and deploy custom apps to your enrolled Mac devices. Add a Custom App to ensure all required applications are ready for your users.
Kandji supports several different installer types. Kandji's Maximum file upload size is 5 GB.
- .PKG: Package Installer File, Kandji additionally supports compressed PKG files.
- .MPKG: Meta Package Installer File
- .ZIP: When using a .zip file, Kandji will allow you to specify where the contents of the .zip should be decompressed to
- .DMG: When using a .dmg file, Kandji will attempt to extract the contents of the DMG to the /Applications folder, note that if your DMG contains a PKG, you should first extract the PKG and upload that to Kandji instead.
Depending on the App you wish to deploy, you can specify if Kandji will install it once, or continually monitor and ensure the custom app is installed.
- Install once per device: Kandji will install the App once. If the App is removed from the Mac, it will not be reinstalled automatically. A software patch, for example, shouldn't be run continuously.
- Audit and Enforce: Kandji will run the audit script and ensure the script passes (exits 0) at each check-in (including before the first install). Should the Audit Script exit anything other than 0, Kandji will reinstall the application automatically.
- Audit Script Considerations: Using an audit script gives you the control to determine what qualifies as a "Pass", should the app be in a certain location? Have a particular checksum? Be on a certain version? all of these checks can be done in an audit script.
- Example Audit Script: This audit script would check for the presence of an application, if the application is not present, it will prompt Kandji to reinstall the Custom App.
if [ -e "$APPPATH" ]; then
Pre & Post Install Scripts
Adding a pre or post-install script allows you to customize the install process for Custom Apps further. Add a pre-install script to perform an action, such as removing another app that is being replaced. Add a post-install script to, for instance, configure the Custom App that was just installed.
Some applications require a reboot after being installed before they will operate correctly. Allowing Kandji to trigger the restart ensures that the install restarts to ensure proper functionality. Check the "Restart after successful install" box to have Kandji restart any Mac devices after the Custom App is installed.
Users will be given a 30-minute countdown before the restart occurs.
Specify a version number to keep track of which apps are deployed to your fleet. You can even upload different versions of the same application.
The library section of Kandji is where you'll find all of the custom apps you've added. Navigate here to add, modify, or remove Custom Apps from your Kandji account. The main Library view also provides a status summary for each Custom App, allowing you to quickly identify how many Mac devices have the Custom App installed, if the install is still pending, or if a Mac has reported errors related to the install.
The status tab inside applications provides a bird's eye view on Custom Applications deployed to your feet. You can easily view which Mac devices are waiting to have the custom app installed, installed successfully, or Mac devices that are reporting installation errors.
To deploy your Custom App to Mac devices enrolled in Kandji, add it to a Blueprint. All Mac devices assigned to that Blueprint will receive the Custom App during their next check-in.
Use the following guides to learn how to use the Custom App feature inside Kandji.