As of 6 Nov 2026, the panel rates Iru (formerly Kandji) 3/5 and Jamf 3/5 in Mobile Device Management (MDM/UEM). Weighted by what each judge cares about, 3 of the 6 judges pick Iru (formerly Kandji) and 1 picks Jamf, 2 call it a tie. Iru (formerly Kandji) scores higher on 2 of 6 criteria (Enrolment & platform coverage and Configuration, apps & updates). Jamf scores higher on 2 of 6 criteria (Hosting options, reliability & assurance and Device security & compliance). Provenance — Iru (formerly Kandji): Rest of world; Jamf: Rest of world. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
Iru (formerly Kandji) and Jamf split by criterion, not by product. Iru leads enrollment and platforms, 6.3 to 5.2, with five leans and one tie, and configuration and apps, 6.8 to 6.5, with two leans. Jamf leads security and compliance, 6.8 to 6.3, with two leans; operations and assurance, 6.8 to 6.0, with five leans; and pricing transparency, 5.5 to 1.2 — Jamf publishes exact per-device prices with 25-device minimums, while Iru is quote-only, with pricing unweighted in its verdicts. Identity and admin ties at 6.2, one lean apiece; sovereignty ties at 4.0. Iru's verdict records a data processing addendum and sub-processor list, importing data into the United States under European Commission standard contract clauses; Jamf's verdict names Frankfurt and London as Jamf Pro regions, but we found no public information on subprocessors or a data processing agreement. Three judges score Iru higher, one Jamf, two tie.
Choose Iru (formerly Kandji) if
You manage Apple, Windows and Android in one fleet: enrollment and platforms runs 6.3 to 5.2, with five judges leaning Iru and one tie, and Jamf's verdict records its widest spread there, 4 to 6, with judges running mixed Windows or Android fleets scoring lower.
Your team wants configuration as code with versioning and rollback, macOS updates through Apple's Declarative Device Management, staged rollouts and a self-service portal: configuration and apps runs 6.8 to 6.5, with two judges leaning Iru.
Your procurement needs the paperwork up front: Iru's verdict records a published data processing addendum and sub-processor list plus an EU API endpoint, while the bench found no public information on Jamf subprocessors or a data processing agreement.
Your reviewer sits closest to the security-officer judge: Iru's weighted total there is 6.1 to Jamf's 5.9.
Your team profiles like the generalist or the skeptic judge: Iru's weighted totals there are 5.8 to 5.6 and 5.7 to 5.3.
Choose Jamf if
You answer to CIS, NIST 800-53, NIST 800-171 or DISA STIG audits and want Monitor Only and Monitor and Enforce modes: security and compliance runs 6.8 to 6.3, with two judges leaning Jamf and four ties.
You need visible operational proof: a public status page with 90-day uptime, a 99.9% uptime commitment, and SOC 2, ISO 27001 and StateRAMP. Operations and assurance runs 6.8 to 6.0, five judges leaning Jamf and one tie; Iru's verdict documents a 99.9 percent availability commitment that excludes maintenance.
You need published prices before procurement: Jamf posts exact per-device prices with 25-device minimums, and pricing transparency runs 5.5 to 1.2 with six judges leaning Jamf; Iru is quote-only, and the panel does not weigh that against it.
You must name EU hosting regions in contracts: Jamf's verdict names Frankfurt and London as Jamf Pro regions, while Iru's verdict records an EU API endpoint and we found no public information on where its device inventory is hosted.
Your bench match is the Apple administrator: Jamf's weighted total there is 6.6 to Iru's 6.4.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Information Security Officer
Information security officer of a municipal utility that counts as critical infrastructure, with staff who want their own phones for mail and the on-call app. Needs encryption and compliance proven per device for the auditor, BYOD with a work profile the works council can sign off because the admin cannot see private apps or the location, a data processing agreement and subprocessor list, and an on-premise or German-hosted option if the cloud one stores the inventory abroad.
Iru (formerly Kandji)
This judge's pick
Jamf
Criterion by criterion
Enrolment & platform coverage
Iru (formerly Kandji)
Apple Automated Device Enrollment with supervision and automatic re-enrollment is documented, BYOD runs through manual enrollment on Apple with work profiles and work/personal separation described for Android, zero-touch deployment covers Apple and Windows, and an automated migration tool off legacy MDM providers exists. What holds me below the top band: we found no public information on Android zero-touch, Samsung Knox Mobile Enrollment, Windows Autopilot by name, shared or rugged device modes, and Linux appears only as an entry in the supported-devices list without stated depth.
Jamf
Apple platforms are covered in depth — macOS, iOS, iPadOS, watchOS, visionOS and tvOS — with zero-touch through Apple Business Manager and Apple School Manager, account-driven User Enrolment for BYOD, and a documented migration of personal-device profiles to Apple's User Enrolment. Android appears only as a BYOD-securing side note with a hosted manager, and we found no public information on Windows, ChromeOS or Linux management, Android zero-touch, Knox or shared-device modes. That Apple-first shape leaves a mixed fleet like ours without one console.
Configuration, apps & updates
Iru (formerly Kandji)
Configuration runs deep for a fleet: version-controlled configuration as code with pull-request review and rollback, custom scripts with conditional triggers, Apple Declarative Device Management driving the macOS update cycle, deferral periods and enforcement deadlines, staged test-group rollouts, and a maintained third-party patch catalogue — though the captured pages give different figures for the Auto Apps catalogue size (250+ and 550+). For my audit file I note we found no public information on certificates through SCEP or ACME, kiosk or single-app mode, or remote screen view for support.
Jamf
App lifecycle is strong: volume-purchased App Store and third-party apps auto-packaged and patched, update deadlines with grace periods scoped to computer groups, custom profiles, policies and scripts, blueprints, self-service and smart groups, and same-day support for new Apple OS releases. We found no public information on certificates through SCEP or ACME, remote control or screen view, kiosk mode, or managed Google Play for the Android side.
Device security & compliance
Iru (formerly Kandji)
This is the strong suit: drive encryption with FileVault and BitLocker key rotation, passcode and brute-force-erase policies, one-click CIS Level 1 and 2 benchmarks for Mac plus SOC 2 and ISO 27001 hardening templates, EDR and vulnerability management with autonomous remediation, and Android work profiles where corporate data is locked without a full device wipe. What my works council and auditor would ask next: we found no public information on what the administrator can see on a personal device, on location tracking that can be switched off per policy, or on jailbreak and root detection.
Jamf
What the auditor needs is there in outline: FileVault with the recovery key escrowed and shown on the device dashboard, CIS, NIST 800-53/171 and DISA STIG benchmarks with Monitor and Enforce modes, rule reporting that generates auditing documents, conditional access with Microsoft and Google, and mobile threat defence through Jamf Protect. BYOD separation is stated as separate personal and corporate volumes that preserve employee privacy, but we found no public information on remote wipe, jailbreak or root detection, or a switch for location tracking — the last being what my works council would ask first.
Directory, API & administration
Iru (formerly Kandji)
A documented REST API with broad modules — devices, blueprints, library items, device actions, audit log, users, threats, vulnerabilities — plus code examples, JSON responses and a 10,000 requests-per-hour limit, SAML SSO with Microsoft Entra ID and Google Workspace, audit logs exportable to Amazon S3 or Datadog, and an integration partner program with a managed-service-provider master agreement. We found no public information on SCIM provisioning, webhooks, or granular admin roles per site or department, which is what I would need for segregation of duties.
Jamf
Entra ID, Google and Okta integration with SSO for admins through any OIDC provider, named Organization Administrator and Administrator roles, directory-group scoping, and a documented platform API gateway with infrastructure-as-code support and Sentinel SIEM export cover the middle ground well. We found no public information on SCIM provisioning, webhooks, granular per-site roles, multi-tenancy for service providers or admin audit logs.
Hosting options, reliability & assurance
Iru (formerly Kandji)
There is a 99.9 percent availability commitment with named exclusions, a public status page, 24/7 in-app chat and email support, ISO 27001 and SOC 2 Type II (both released only under NDA), third-party penetration tests at least twice a year, monthly third-party and daily internal vulnerability scans, SAST and DAST in the build pipeline, and a vulnerability disclosure program. For a critical-infrastructure buyer the gaps matter: we found no public information on an on-premise or self-hosted edition, on data-centre regions named by country (an EU API endpoint exists), on SLA credits, or on the certifications' scope and audit dates.
Jamf
Assurance is unusually visible: a public status page with per-component 90-day uptime between 99.83% and 100% and a real incident history, a 99.9% SLA with a credit-request process and 30-day change notice, SOC 2, ISO 27001 and StateRAMP named, a vulnerability disclosure programme, and hosting regions including Frankfurt, London and Germany West Central. We found no public information on certification scope and audit dates, penetration testing, or the differences of an on-premises edition, which a pricing FAQ only implies exists.
European sovereignty
Iru (formerly Kandji)
The contracting entity is Iru, Inc. of Miami and the privacy policy states that data is imported into the United States under European Commission standard contract clauses; a Data Processing Addendum and a sub-processor list are published, and an EU API endpoint exists, which is more than the bare-minimum posture. But we found no public information on where the device inventory and location data are actually hosted, on a German-hosted or EU-region option, or on an on-premise edition — and generative AI is used to process customer feedback with no provider named.
Jamf
EU hosting is concretely documented — Frankfurt and London for Jamf Pro, Germany West Central on Azure, Germany for Protect, Ireland for the security cloud, Belgium for Android management, with instances defaulted to the location closest to the customer's business address — so the inventory could stay in Germany. But the contracting entity is the US company Jamf Software, LLC of Minneapolis, and we found no public information on a data processing agreement, a subprocessor list with locations, an EU representative, or where the AI Assistant processes its data. Without those documents I could not sign this off for critical infrastructure.
Pricing transparency
Iru (formerly Kandji)
The pricing page names the basis — the solutions chosen plus the number of users and devices — but every figure sits behind 'Request a quote'. We found no public information on per-device or per-user prices, what each plan includes, add-on costs, minimum counts, billing terms, or on-premise licensing, so I cannot compute an annual cost from public pages.
Jamf
The main plans are public with per-device prices, minimums and inclusions: $12.50 per macOS device and $5.75 per mobile device per month billed annually with a 25-device minimum, Jamf Now from $4 per device per month, and up to three devices for free. We found no public information on what the Protect or AI Governance add-ons cost, on-premises licence prices, MSP terms, onboarding fees or VAT treatment, so the real annual cost is not computable from these pages alone.
Sovereignty, side by side
Dimension
Iru (formerly Kandji)
Jamf
Legal entity
Not determined
Not determined
Hosting location
Not determined
Not determined
Hosting options
Not determined
EU region selectable
Open source
Not determined
Not determined
Data processing agreement
Published, self-serve
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
As of 6 Nov 2026, the panel rates both 3/5. Weighted by what each judge cares about, 3 of the 6 judges pick Iru (formerly Kandji) and 1 picks Jamf, 2 call it a tie. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is Iru (formerly Kandji) or Jamf European?
Iru (formerly Kandji) is not European by provenance (Rest of world). Jamf is not European by provenance (Rest of world). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Do Iru (formerly Kandji) and Jamf have a free plan?
As of 6 Nov 2026, Jamf’s own pages state a free plan; Iru (formerly Kandji)’s pages as captured do not. Each product page links the pricing page it was read from.