TL;DR

In October 2025, Kandji rebranded as Iru. In May 2026, Iru launched an MSP channel program with partner incentives and an “Apple + Windows in one solution” pitch. The go-to-market motion is real and well-funded. The MSP-specific product capabilities — particularly native multi-tenancy and single-pane-of-glass — appear to still be under active development. Four questions to ask before switching your Apple practice: does cross-platform actually simplify your stack, is multi-tenancy production-ready, what’s the post-incentive margin math, and are you trading specialist depth for breadth? Addigy has been built for MSPs managing Apple devices since 2014.

In October 2025, Kandji rebranded as Iru and expanded beyond Apple-only MDM. In May 2026, Iru went a step further — formally entering the MSP market with a channel program, partner incentives, and an “all-in-one across Apple and Windows” sales motion.

If your MSP built its Apple practice on Kandji, you now have a real evaluation to make: what’s actually different, what’s marketing, and what should you look for before signing into a new partner agreement.

Here’s our practical read.

What Iru Actually Announced

Two things happened several months apart, and they should be evaluated separately.

The October 2025 rebrand. Kandji became Iru. The product expanded into Windows and Android device management. Endpoint Detection & Response, Vulnerability Management, Workforce Identity, and Compliance Automation were repositioned as separately-licensed modules under one console.

The May 2026 MSP launch. Iru announced a formal MSP channel program with partner incentives, infrastructure investment in MSP workflows, and messaging centered on “one solution across Apple and Windows, simplified for partners.”

The MSP program is real. The partner incentives are real. What’s less clear from public information is the depth of Iru’s MSP-specific product capabilities — particularly native multi-tenancy and the single-pane-of-glass experience MSPs need at scale. Those capabilities appear to still be under active development.

Confirmed market entrance, uncertain product maturity. That’s the distinction MSP buyers should focus on.

Four Questions Worth Asking Before You Switch

1. Does “Apple and Windows in one solution” actually simplify your stack?

Iru’s clearest narrative is consolidation: “Why manage multiple tools when you can manage everything in one solution?” 

Test it against your actual stack. If your MSP already runs ConnectWise, NinjaOne, Datto, Kaseya, or Autotask for Windows, a cross-platform MDM doesn’t reduce the tools you operate — it duplicates the layer you already have. The consolidation story is built for direct-buyer IT teams replacing their entire stack. For an MSP whose RMM already handles Windows, the math is different.

Addigy is built to work with the RMM/PSA you already run, not replace it.

2. Multi-tenancy: ship date or production reality?

True multi-tenancy is the structural difference between an MDM built for direct sale and one built for MSPs. It’s the difference between logging into separate tenants per client and managing every client from one console.

Today, public information about Iru’s multi-tenant depth is limited. Their MSP motion is new, and the supporting architecture appears to still be evolving. 

Addigy’s multi-tenant architecture has been in production for over a decade. It is the core of how the product is built, not a feature added in response to a new channel motion. For MSPs already managing 10+ Apple-active clients, that production maturity matters operationally — every day, not just at signing.

3. Channel incentives: what’s the actual margin math?

Iru’s program includes partner incentives. You’ve seen the playbook – that’s how every new channel entrant builds a partner base. The real question isn’t whether the incentives are real; it’s whether the first-year economics survive into year two.

Real switching costs for an Apple-managed book of business include re-enrollment, SOP rewrites, policy mapping, technician retraining, and client documentation updates. For a 100-client base, that operational cost typically exceeds first-year incentive value — and incentive structures rarely persist past year one.

The harder question: when the incentives end, are you locked into pricing and contract terms that protect your margins for the next five years — or was the discount the only reason the economics worked?

4. Apple specialist depth: are you trading focus for breadth?

The premium tier of most MSP Apple practices is specialist depth — being the team that demonstrably knows Apple management better than a generalist competitor. That premium exists because most MSPs can’t deliver it.

A cross-platform MDM has to allocate engineering effort across Apple, Windows, and Android. By Iru’s own communication, the team has doubled to maintain focus across both platforms — real investment, but also confirmation that focus is now spread.

Addigy’s engineering attention sits entirely on Apple. Mac, iPhone, iPad, Apple TV, every OS release, every new compliance framework Apple introduces. For an MSP whose service margin depends on Apple expertise as a differentiator, that focus shows up in the depth of the product over time.

Snapshot: Iru vs. Addigy for MSPs (as of May 2026)

Why MSPs Continue to Choose Addigy

Addigy was built for MSPs managing Apple devices — not repurposed for them. Multi-tenant by default. Real-time control through a live agent and remote terminal, not check-in-based enforcement. Pre-built CIS, NIST, CMMC, and DISA STIG frameworks for continuous compliance — toggle them on per client and Addigy enforces them automatically. Native integration with the RMM/PSA you already run. Transparent pricing that lets you build service margins without quote-only surprises.

The customers who switched from Kandji describe the migration in clear terms:

See the difference for yourself. 

Or schedule a personal demo

Related: 

Addigy vs. Iru — Full Comparison for 2026