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 Field Operations Lead
Leads operations at a facility services company with 600 cleaners and technicians across North Rhine-Westphalia, who share rugged Android handsets and tablets per shift. Needs devices locked to the time-recording and work-order apps, zero-touch enrolment with Knox or Android Enterprise, apps updated overnight, a dropped device replaced in a day without IT on site, and remote view when a foreman calls in because a screen shows something nobody understands.
Iru (formerly Kandji)
Jamf
This judge calls it a tie.
Criterion by criterion
Enrolment & platform coverage
Iru (formerly Kandji)
The Apple side is strong — Automated Device Enrollment with supervision, automatic re-enrollment after loss or erase, BYOD manual enrolment, and an automated migration tool off a legacy MDM — and Windows gets zero-touch too. For my shift fleet the Android story is manual work-profile enrolment with managed Google Play, and we found no public information on Android zero-touch, Samsung Knox Mobile Enrollment, QR or email enrolment, or shared and rugged device modes, which is exactly what a per-shift handset fleet runs on.
Jamf
Zero-touch enrolment through Apple Business Manager and Apple School Manager is documented down to token renewal, with account-driven user enrolment for BYOD and supervision that stops users removing the management profile — but that depth is Apple-only. Android appears as a supported platform in the mobile bundle and a remark about securing BYOD Android devices, and I found no public information on Android zero-touch, Samsung Knox Mobile Enrollment, shared or rugged device modes, or a migration path from another MDM. For my 600 shift-shared Android handsets that is a non-starter, whatever the Apple fleet runs on.
Configuration, apps & updates
Iru (formerly Kandji)
App patching runs with severity-based timeframes across Mac and Windows (the captured pages give different figures for catalogue size, 250-plus to 550-plus), OS updates can be deferred and enforced with deadlines, custom scripts run on conditional triggers, and there is a self-service portal plus configuration-as-code with versioning and rollback. We found no public information on kiosk or single-app mode, remote view or remote control for support, or certificate enrolment through SCEP or ACME — so a foreman calling about a screen nobody understands stays a truck roll, and a shift-locked device stays manual.
Jamf
Blueprints, custom profiles, scripts, volume-purchased app distribution, patch policies with update deadlines in days plus a grace period, a self-service catalogue and same-day support for new Apple OS releases are all documented. But the captured pages are silent on the three things my handsets live or die by: I found no public information on kiosk or single-app mode, on remote view or remote control for support, or on managed Google Play app distribution.
Device security & compliance
Iru (formerly Kandji)
Passcode policies with erase on brute-force attempts, remote lock and wipe for Android, FileVault and BitLocker key rotation, one-click CIS templates for Mac, plus EDR and severity-ranked vulnerability handling with automated Mac patch remediation give me most of anchor-5 with real automation, and Entra ID SAML with device-bound identity covers conditional app access. We found no public information on lost mode, jailbreak or root detection, location-tracking controls, or what an admin can see on a personal device, and the captured pages state automated remediation for Windows apps is coming soon.
Jamf
Compliance is the strongest story here: automated benchmarks aligned to CIS, NIST and DISA STIG with monitor-and-enforce modes and auditable rule reports, FileVault with escrowed recovery keys, conditional access with Microsoft and Google named, and mobile threat defence through Jamf Protect. Passcode enforcement and remote lock are documented, but I found no public information on remote wipe, lost mode, or location tracking that can be switched off per policy — the things that make a handset dropped in a depot harmless.
Directory, API & administration
Iru (formerly Kandji)
A documented REST API returning JSON with a 10,000-requests-per-hour limit covers devices, blueprints, library items, device actions, users and the audit log, SSO works with Microsoft Entra ID (SAML) and Google Workspace, activity logs export to Amazon S3 and Datadog, and a Managed Service Provider Master Agreement exists. We found no public information on SCIM provisioning, LDAP or Active Directory sync, granular roles per site or department, webhooks, or a partner console with sub-accounts.
Jamf
Entra ID with directory group scoping, Google Workspace, Okta and single sign-on via OIDC for Okta, Entra, Google, OneLogin, PingOne and JumpCloud are documented, plus a platform API with a single gateway, infrastructure-as-code, a Sentinel feed for the SIEM and a marketplace of 150-plus integrations. Beyond the two administrator roles named, I found no public information on granular per-site permissions, SCIM provisioning, webhooks, 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 24-hour notice of maintenance on a public status page, 24/7 support through in-app chat and email, ISO 27001 and SOC 2 Type II (reports on request under NDA), third-party penetration tests at least twice a year and a vulnerability disclosure programme — decent audit footing. We found no public information on an on-premise edition, release notes or same-day OS support records, SLA credits, or hosting regions named by country beyond an EU API endpoint, which for my German works council is thin.
Jamf
A public status page with per-service 90-day uptime and incident history, named hosting locations including Germany, Ireland and Belgium with a closest-to-customer default rule, an SLA committing to 99.9% uptime with a credit process, SOC 2, ISO 27001 and StateRAMP named, and a vulnerability disclosure programme give me real assurance material. I found no public information on certification scope and audit dates, penetration testing, or a self-hosted edition beyond a FAQ mention of on-premises customers.
European sovereignty
Iru (formerly Kandji)
The contracting entity is Iru, Inc. in the United States, which states it imports data into the US under European Commission standard contract clauses; a data processing addendum and a sub-processor list are published and ISO 27001 is stated, which lifts it above the bare-minimum anchor. EU hosting or an EU contracting entity is not evidenced anywhere I read — only an EU API endpoint — and an AI acceptable-use policy plus generative AI processing of customer feedback are on the pages, so for a North Rhine-Westphalia works council the chain is only partly visible.
Jamf
Jamf Cloud runs in named German, Irish and Belgian locations with a default-to-nearest rule, and the trust centre points to security, compliance, privacy and legal documents. But the contracting entity is Jamf Software, LLC of Minneapolis, and I found no public information on a subprocessor list, a published data processing agreement, or an EU representative — for a works council in North Rhine-Westphalia that chain is unproven.
Pricing transparency
Iru (formerly Kandji)
The pricing page names the basis — the solutions needed plus the number of users and devices — but every actual figure sits behind Request a quote. We found no public price per device or per user, no plan contents, no minimum counts, billing terms or onboarding fees, so I cannot budget 600 handsets from these pages alone.
Jamf
Per-device prices are public and exact — $12.50 per macOS device and $5.75 per mobile device per month, billed annually with a 25-device minimum, Jamf Now starting at $4 per device per month, plus education pricing and a free three-device tier — and the bundles list what each includes. The pricing FAQ raises on-premises purchases, Premium Cloud, Elevate and AI Governance licensing, but I found no public figures for those or for onboarding fees, VAT treatment and MSP pricing, so a full annual cost is not computable from the captured 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.