Skip to main content

Appaloosa Battlecards

How Appaloosa compares to the main MDM/MAM competitors. Sales-ready material for partners and internal teams.

Appaloosa
Appaloosa
VS
TinyMDM
TinyMDM

TinyMDM is a French-headquartered Android-only MDM, ISO 27001 certified, hosted on AWS Europe. Strong fit for SMB Android-only fleets.

Key differentiators

Sovereignty
Appaloosa is SecNumCloud + ISO 27001, hosted in France. TinyMDM is ISO 27001 but hosted on AWS Europe, subject to the US Cloud Act.
Unified cross-platform
Appaloosa covers iOS, Android, macOS, Windows in a single console. TinyMDM is Android only.
Support
Appaloosa: French support < 5 min (internal commitment, demo it live). TinyMDM: self-service / partners, no public support SLA.

Profile

Parent company
Ars Nova Systems (FR)
Platforms
Android only
Hosting
AWS Europe
Certifications
ISO 27001:2022 (June 2025)
Public pricing
~€2/device/month
Target
SMB, schools, kiosks
Model
Self-service + partners
Android Enterprise
Silver Partner

Comparison matrix

Supported platforms
Appaloosa
Appaloosa
iOS, iPadOS, macOS, Windows, Android
TinyMDM
Android only
Sovereignty / hosting
Appaloosa
Appaloosa
SecNumCloud (France) + ISO 27001
TinyMDM
AWS Europe + ISO 27001:2022
Cloud Act / FISA compliance
Appaloosa
Appaloosa
Outside US jurisdiction
TinyMDM
Subject (vendor on AWS, US-controlled)
Android depth (Work Profile, Kiosk, COPE, Managed, Zero Touch)
Context-dependent
Appaloosa
Work Profile, Fully Managed (COBO), COPE, Kiosk (COSU), Zero Touch
TinyMDM
Work Profile, Fully Managed (COBO), WPCO/COPE, Kiosk (COSU), Zero Touch
iOS depth (BYOD, Managed, Kiosk, ADE)
Appaloosa
Appaloosa
Supervised, Kiosk Single/Multi-App, ADE via ABM, simplified MAM profile for BYOD
TinyMDM
Not supported
Mac depth
Appaloosa
Appaloosa
Advanced: ABM, DEP, Configuration Profiles
TinyMDM
Not supported
Windows depth
Appaloosa
Appaloosa
Basic: enrollment + app deployment
TinyMDM
Not supported
Private store (private + public apps, App Config, Managed Config)
Appaloosa
Appaloosa
Private + public apps, App Config (Android), Managed App Config (iOS)
TinyMDM
APK + public apps + Android App Config
Remote Support
Context-dependent
Appaloosa
Natively integrated
TinyMDM
Native remote control (Android)
File deployment
Context-dependent
Appaloosa
Supported
TinyMDM
Documents and apps
Contact sync
Context-dependent
Appaloosa
Supported
TinyMDM
Contact sync supported
Onboarding
Appaloosa
Appaloosa
Self-serve + dedicated CSM, FR support < 5 min
TinyMDM
Self-service or partner-led
Target & complexity
Appaloosa
Appaloosa
SMB, mid-market, enterprise mixed fleets
TinyMDM
SMB 20-500, schools, kiosks (Android-only)
Integrations
Appaloosa
Appaloosa
SAMLv2, Okta, M365, Google Workspace
TinyMDM
Standard MDM, Samsung Knox partner
Pricing
Appaloosa
From €3.49/device/month
TinyMDM
€2/device/month, transparent

Where Appaloosa wins

  • SecNumCloud-qualified sovereignty
    Decisive in public sector, OIV/OSE, banking, healthcare, defense. TinyMDM = AWS Europe, exposed to the Cloud Act.
  • One console for 5 OSes
    iOS, iPadOS, macOS, Windows, Android. One product to operate, one user onboarding, one policy framework.
  • Mature MAM: private + public apps, App Config, Managed App Config
    Pre-configured corporate apps (URL, auth, feature flags) on iOS and Android, alongside public apps via managed Google Play and Apple VPP. TinyMDM stays at APK distribution.
  • FR support < 5 min (internal commitment)
    Differentiates against a self-service vendor. Demonstrate it live: open a ticket during the demo.
  • Scale & governance
    Audit logs, fine-grained RBAC, SAMLv2 SSO, Okta/M365/Workspace integrations. Built for structured IT teams.

Where the competitor wins

  • Transparent entry pricing
    ~€2/device/month publicly listed, no tiers. Hard to beat on a pure-price SMB RFP.
  • Pure Android depth
    Silver Android Enterprise Partner: kiosk, COBO, COPE, BYOD. If the fleet is 100% Android, the feature gap is small.
  • Distribution partner network
    Strong presence with Android hardware resellers and SMB / education integrators.
  • Onboarding simplicity
    Free trial, clean UI, no friction. First device managed in minutes.

Talk tracks

If TinyMDM is mentioned early in discovery

"TinyMDM is a good Android product and we know them well. Two questions to help you frame this: (1) will your fleet stay 100% Android over the next 24 months, or will Macs, iPhones, Windows arrive as you grow? (2) is your DPO or CISO asking you for SecNumCloud qualification, or is ISO 27001 enough? Depending on the answers, the choice becomes obvious one way or the other."

If the prospect already runs TinyMDM (displacement)

"You already have an MDM doing its job on Android. The question isn't 'TinyMDM vs Appaloosa', it's 'what's changed for you since the original decision?'. Three typical triggers: • iPhones or Macs joining the fleet (sales, executives), • a sovereignty / Cloud Act requirement that wasn't on the table before, • a need for a private internal app store. We don't move for the sake of moving; we look at whether one of these three applies to you."

If TinyMDM is added late by the partner / IT

"TinyMDM often comes up when you want the cheapest option for pure Android. That's a rational short-term calculation. Over 36 months, look at three lines that the €2 price doesn't cover: (1) a second MDM for iOS / Mac / Windows, (2) internal hours to align two consoles, (3) Cloud Act exposure if your sector tightens its requirements. By then, the TCO flips."

Objections

True on Android face price. Reframe on total cost: a unified MDM avoids a second tool for iOS/Mac/Windows; <5 min support cuts internal IT time; SecNumCloud qualification avoids costly audits in 12 months. On a mixed perimeter, Appaloosa often comes out cheaper on 24-month TCO.

Yes, Ars Nova Systems is French and obtained ISO 27001:2022 in June 2025, that's good. But their servers are on Amazon AWS Europe, therefore subject to the Cloud Act and FISA. Sovereignty ≠ French headquarters. Sovereignty = data outside US jurisdiction. That's exactly what Appaloosa's SecNumCloud qualification guarantees, an ANSSI framework, not a generic quality audit.

Maybe today. Honest question: over the past 24 months, how many iPhones or Macs landed in the company for sales, executives, marketing, designers? General market trend: 60% of '100% Android' fleets become mixed within 3 years. The cost of switching is higher later, better to choose now a tool that covers what's coming.

True for simple deployments, <50 devices, few apps, no IDP. Appaloosa adds upfront time because we configure SAML, RBAC, audit, private store, that's what a mature IT team expects. Comparing the simplicity of an SMB tool to an enterprise tool is misleading: the governance expectations are different.

Questions to ask the prospect

Open-ended questions that expose competitor weaknesses without naming them.

  1. 1
    Has your CISO ever discussed the Cloud Act or SecNumCloud qualification with you?
    If yes, sovereignty is on the table, TinyMDM's AWS becomes a topic. If no, plant the seed for their next audit.
  2. 2
    Beyond Android, which OSes do you expect to manage in 18 months?
    Forces the prospect to project Mac / iOS / Windows. TinyMDM covers nothing other than Android.
  3. 3
    How do you push a pre-configured corporate app (server URL, SSO, feature flags) to a targeted user group today?
    Tests App Configuration / Managed App Configuration support. Pure MDMs fall back to plain APK distribution.
  4. 4
    If a device is compromised on a Saturday night, how fast do you get a human response?
    Self-service / partner = no answer at H+0. Appaloosa FR support < 5 min, demonstrate it live.
  5. 5
    How many hours per week does your IT team spend on device management today, excluding incidents?
    Opens the TCO conversation. Per-device price doesn't capture operational cost.
Appaloosa
Appaloosa
VS
Microsoft Intune
Microsoft Intune

Microsoft's enterprise MDM/UEM, included in Microsoft 365 E3+ / Business Premium. Strong Windows + M365 integration, but US-headquartered, Cloud Act exposure even with Azure EU regions.

Key differentiators

Sovereignty
Appaloosa is SecNumCloud + ISO 27001, hosted in France. Intune runs on Azure, Microsoft is US-headquartered, so data is subject to the Cloud Act regardless of region selected.
Lighter app distribution workflow
Functional parity with Intune on App Config, VPP and managed Google Play. The difference is operational: Appaloosa publishes a private Android APK in 3-4 clicks; Intune walks through Apps, Create, Managed Google Play, Private apps, Upload, Sync, Assign. Same outcome, fewer steps.
Independence & speed
No Entra/Azure AD lock-in, connects to any IDP via SAMLv2. Days to deploy vs weeks-to-months on Intune enterprise rollouts. FR support < 5 min.

Profile

Parent company
Microsoft (US)
Platforms
iOS · iPadOS · Android · Windows · macOS · Linux (limited)
Hosting
Azure (US-controlled, EU regions available)
Certifications
FedRAMP High, ISO 27001, HIPAA, PCI DSS
Public pricing
$8/user/mo (Plan 1) + $4 (Plan 2) + $10 (Suite)
Target
Mid-market & enterprise on Microsoft stack
Bundling
Included in M365 E3+ / Business Premium
Cloud Act exposure
Yes (US parent company)

Comparison matrix

Supported platforms
Context-dependent
Appaloosa
iOS, iPadOS, macOS, Windows, Android
Microsoft Intune
iOS, iPadOS, Android, Windows, macOS, Linux (limited)
Sovereignty / hosting
Appaloosa
Appaloosa
SecNumCloud (France) + ISO 27001
Microsoft Intune
Azure (US-controlled, EU regions available)
Cloud Act / FISA compliance
Appaloosa
Appaloosa
Outside US jurisdiction
Microsoft Intune
Subject (US parent, applies regardless of region)
Android depth (Work Profile, Kiosk, COPE, Managed, Zero Touch)
Context-dependent
Appaloosa
Work Profile, Fully Managed (COBO), COPE, Kiosk (COSU), Zero Touch
Microsoft Intune
Work Profile, Fully Managed, COPE, Kiosk, Zero Touch (full)
iOS depth (BYOD, Managed, Kiosk, ADE)
Competitor
Appaloosa
Supervised, Kiosk Single/Multi-App, ADE via ABM, simplified MAM profile for BYOD
Microsoft Intune
User Enrollment, Supervised, Kiosk, ADE (full Apple)
Mac depth
Context-dependent
Appaloosa
Advanced: ABM, DEP, Configuration Profiles
Microsoft Intune
ABM, DEP, Configuration Profiles, native macOS management
Windows depth
Competitor
Appaloosa
Basic: enrollment + app deployment
Microsoft Intune
Native, Win32 + Modern Mgmt + Autopilot (deepest on market)
Private store (private + public apps, App Config, Managed Config)
Context-dependent
Appaloosa
Private + public apps, App Config (Android), Managed App Config (iOS)
Microsoft Intune
App Config Policies (iOS, Android, Edge on Windows), VPP, Managed Google Play
Remote Support
Context-dependent
Appaloosa
Natively integrated
Microsoft Intune
Intune Remote Help (paid add-on, Intune Suite)
File deployment
Appaloosa
Appaloosa
Supported
Microsoft Intune
Limited (no native MDM file push)
Contact sync
Appaloosa
Appaloosa
Supported
Microsoft Intune
Via Outlook/Exchange, not MDM-specific
Onboarding
Appaloosa
Appaloosa
Self-serve + dedicated CSM, FR support < 5 min
Microsoft Intune
Complex, partner-led, weeks to months
Target & complexity
Context-dependent
Appaloosa
SMB, mid-market, enterprise mixed fleets
Microsoft Intune
Mid-market & enterprise on Microsoft stack
Integrations
Competitor
Appaloosa
SAMLv2, Okta, M365, Google Workspace
Microsoft Intune
Native M365 / Entra (deep but lock-in)
Pricing
Appaloosa
From €3.49/device/month
Microsoft Intune
$8/user/mo (Plan 1) + $4 (P2) + $10 (Suite)

Where Appaloosa wins

  • Sovereignty (Cloud Act / FISA)
    Decisive in public sector, OIV/OSE, banking, healthcare, defense. Even Azure EU regions don't escape US jurisdiction, Microsoft has acknowledged this in EU hearings.
  • Operationally simpler MAM workflow
    Functional parity with Intune (App Config, Managed App Config, VPP, managed Google Play). What differs: the admin journey. Pushing a private Android APK on Intune is documented as Apps, Create, Managed Google Play app, Private apps, Upload APK, Sync, Assign to groups, with package-name uniqueness constraints. Appaloosa folds this into a lean publish flow built for non-IT-specialist teams.
  • Independence from Microsoft stack
    No Entra ID required, no Azure tenant, no migration lock-in. Connects to any IDP via SAMLv2.
  • Speed of deployment
    Days vs weeks-to-months on Intune enterprise rollouts. Useful when business needs to move now.
  • Native Remote Support
    Remote Support is included natively in Appaloosa. Intune Remote Help is a paid add-on (Intune Suite).

Where the competitor wins

  • Bundled with M365 E3+ / Business Premium
    Already paid for if the customer is on these plans. Pure-price comparison loses by definition.
  • Windows depth
    Native Win32 app management, Intune Suite advanced features (Endpoint Privilege Management, Remote Help…). Hard to match for pure-Windows shops.
  • Conditional Access via Entra
    Industry-leading policy engine when combined with Entra ID. Decisive for security-sensitive enterprises.
  • FedRAMP High for US public sector
    Required for US federal contracts. Appaloosa doesn't compete here.

Talk tracks

If Intune is mentioned because the prospect is on M365

"Intune is included in your E3, that's a real argument. Two questions: (1) does your CISO require SecNumCloud, or is ISO 27001 + Azure EU enough? (2) do you publish pre-configured corporate apps to targeted user groups (App Config, branded private store), and how long does each release take? On the first, Intune fails sovereignty by design. On the second, the Company Portal isn't built for app distribution beyond deployment. If both matter to you, the conversation is about more than price."

If the prospect already runs Intune (displacement)

"You don't need to rip out Intune. Many of our customers keep Intune for Windows policy and Conditional Access via Entra, and use Appaloosa for the mobile + Mac + private app store layer. They are complementary: Intune for endpoint compliance, Appaloosa for app distribution + sovereignty for data that can't sit on US infrastructure."

If the prospect is on Business Premium (SMB)

"For sub-300-employee fleets, Business Premium is often over-licensed for what you actually use Intune for. Two checks: which Intune features are you using today? And what's missing on the mobile side (private store, App Config, FR support)? If you're paying for Intune mostly for mobile push, downgrading to Standard + Appaloosa is often cheaper and lands a better mobile experience plus FR sovereignty."

Objections

Bundled, not free. Three cost lines the bundle hides: (1) integration time, Intune deployments commonly run weeks-to-months for a clean rollout vs days on Appaloosa; (2) Cloud Act exposure on sensitive data; (3) mobile experience gap, no real private app store, no native Remote Support without the paid Intune Suite add-on. Bundled doesn't always mean cheaper, especially on the mobile side.

Azure EU regions limit data residency, not jurisdiction. Microsoft is a US company, so the Cloud Act and FISA apply regardless of where the bytes sit. Microsoft's own legal team has acknowledged this in EU parliamentary hearings. SecNumCloud (ANSSI's qualification) was designed precisely to close this gap, that's why Appaloosa is qualified and Azure isn't.

Fair. Many of our customers do keep Intune for Windows + Conditional Access. The question isn't replacement, it's coverage. Intune does endpoint compliance well. Where it falls short is mobile experience (real private app store, App Config / Managed App Config publishing, native Remote Support) and sovereignty. Appaloosa fills exactly those gaps without touching your Windows setup.

Global presence ≠ best fit per geography. For your French / European subsidiaries handling regulated data, Appaloosa adds the sovereignty layer Microsoft can't legally provide. We see this combo (Intune for global IT compliance + Appaloosa for FR/EU regulated workflows) at several mid-cap groups, it's not 'either/or'.

Questions to ask the prospect

Open-ended questions that expose competitor weaknesses without naming them.

  1. 1
    Do you store regulated personal data (HR, health, citizen data) on devices managed by Intune?
    If yes, the conversation moves from 'comfortable Microsoft default' to 'compliance audit risk'.
  2. 2
    How long was your last Intune rollout from kick-off to first-device-managed?
    Intune projects routinely run 6-12+ weeks. Appaloosa runs days. Surfaces hidden time cost.
  3. 3
    What's your current process to publish a pre-configured corporate app (App Config / Managed App Config) to a targeted group on Intune, and how long does it take?
    Surfaces the gap between Intune deployment workflow and a real branded private store with native targeted publishing.
  4. 4
    If the US passed an executive order targeting your industry tomorrow, where would your data physically and legally sit?
    Direct sovereignty test. Echoes the 2025 ICC / Karim Khan precedent (Microsoft cut services on US sanctions).
Appaloosa
Appaloosa
VS
Samsung Knox
Samsung Knox

Samsung's defense-grade Android security platform. Knox Manage = MDM bundled in Knox Suite. Excellent on Samsung hardware, weak on non-Samsung Android, near-zero on iOS/Mac/Windows. Korean parent company, non-EU jurisdiction.

Key differentiators

Cross-OS coverage
Appaloosa is truly multi-OS (iOS, iPadOS, macOS, Windows, Android). Knox Manage is Android-first, iOS/Mac/Windows support exists but is shallow.
EU sovereignty
Appaloosa = SecNumCloud, France-hosted. Samsung is Korean, outside EU jurisdiction; data residency commitments are GDPR-level only, not ANSSI.
MAM beyond Samsung hardware
Appaloosa MAM (private store, App Config / Managed App Config, targeted publishing) works the same on any vendor's Android, on iOS, on Mac. Knox's strength is tied to Samsung devices.

Profile

Parent company
Samsung Electronics (KR)
Platforms
Android (best on Samsung), Chrome OS
Hosting
Samsung cloud (multi-region, GDPR-aligned)
Certifications
SOC 2, Common Criteria, FIPS 140-2, NIAP, DISA, NCSC UK
Public pricing
$24/seat/year (Knox Manage)
Bundling
Knox Suite (Mobile Enrollment + E-FOTA + Asset Intelligence)
Target
Defense, government, regulated industries on Samsung fleets
Hardware tie-in
Hardware-rooted security on Samsung devices

Comparison matrix

Supported platforms
Appaloosa
Appaloosa
iOS, iPadOS, macOS, Windows, Android
Samsung Knox
Android (best on Samsung) + Chrome OS, limited iOS/Mac/Windows
Sovereignty / hosting
Appaloosa
Appaloosa
SecNumCloud (France) + ISO 27001
Samsung Knox
Samsung cloud, KR jurisdiction, GDPR-aligned
Cloud Act / FISA compliance
Appaloosa
Appaloosa
Outside US jurisdiction
Samsung Knox
Outside US, but no SecNumCloud / ANSSI listing
Android depth (Work Profile, Kiosk, COPE, Managed, Zero Touch)
Competitor
Appaloosa
Work Profile, Fully Managed (COBO), COPE, Kiosk (COSU), Zero Touch
Samsung Knox
Full Android Enterprise + Knox extensions on Samsung, Knox Mobile Enrollment
iOS depth (BYOD, Managed, Kiosk, ADE)
Appaloosa
Appaloosa
Supervised, Kiosk Single/Multi-App, ADE via ABM, simplified MAM profile for BYOD
Samsung Knox
Limited (ADE, VPP, internal apps)
Mac depth
Appaloosa
Appaloosa
Advanced: ABM, DEP, Configuration Profiles
Samsung Knox
Internal app deployment, limited config
Windows depth
Appaloosa
Appaloosa
Basic: enrollment + app deployment
Samsung Knox
Internal app deployment, limited config
Private store (private + public apps, App Config, Managed Config)
Context-dependent
Appaloosa
Private + public apps, App Config (Android), Managed App Config (iOS)
Samsung Knox
Internal apps for Android, iOS, macOS, Windows
Remote Support
Context-dependent
Appaloosa
Natively integrated
Samsung Knox
Knox Remote Support (native, log/image/video transfer)
File deployment
Appaloosa
Appaloosa
Supported
Samsung Knox
Log/image/video file transfer (limited scope)
Contact sync
Appaloosa
Appaloosa
Supported
Samsung Knox
Not documented publicly
Onboarding
Context-dependent
Appaloosa
Self-serve + dedicated CSM, FR support < 5 min
Samsung Knox
Knox Mobile Enrollment ZTE (best on Samsung hardware)
Target & complexity
Appaloosa
Appaloosa
SMB, mid-market, enterprise mixed fleets
Samsung Knox
Defense, government, Samsung-heavy fleets
Integrations
Context-dependent
Appaloosa
SAMLv2, Okta, M365, Google Workspace
Samsung Knox
SAML, AD, Knox SDK
Pricing
Appaloosa
From €3.49/device/month
Samsung Knox
$24/seat/year (Knox Manage)

Where Appaloosa wins

  • Mixed fleets and BYOD
    When the fleet has iPhones, Macs, Windows laptops, mixed-vendor Androids, Knox can't cover everything. Appaloosa does, in one console.
  • EU sovereignty
    SecNumCloud is required for OIV/OSE projects in France. Samsung's Korean jurisdiction is excluded by some sovereignty doctrines.
  • MAM beyond app deployment
    Branded private app store, App Config (Android) and Managed App Config (iOS) for pre-configured corporate apps, targeted publishing. Knox stays at app push.
  • Vendor-neutral
    No tie-in to a single hardware OEM. The customer keeps procurement freedom for the next refresh cycle.

Where the competitor wins

  • Pure-Samsung fleets in defense / regulated
    Knox + Samsung hardware = unmatched depth. Common Criteria + FIPS 140-2 + DISA approval = fortress for US/UK government use cases.
  • Hardware-rooted Knox chip
    Real TEE on the silicon, attestation, secure boot. Software-only MDMs (Appaloosa included) can't reach this layer.
  • Knox Mobile Enrollment (KME)
    Best zero-touch enrollment on Samsung devices. If the fleet is 100% Samsung, KME is hard to beat for scale rollouts.

Talk tracks

If Knox is bundled with new Samsung hardware purchase

"Knox is excellent on Samsung, no debate. The question is: how Samsung is your roadmap? If 100% Samsung locked-in for 5 years, Knox is the right call. If iPhones, Macs, Windows, or non-Samsung Androids will land in the fleet, you'll either run two MDMs (Knox + something else) or migrate. We help avoid that fork."

If the prospect has compliance / sovereignty requirements (FR public sector, OIV)

"On the security side, Knox has a stack of military certifications, that's real. On the sovereignty side, it's a different conversation: Samsung is Korean, not subject to US Cloud Act but also not under ANSSI's SecNumCloud framework. For projects that explicitly require SecNumCloud, Appaloosa fits the spec; Knox doesn't."

If real app distribution (private store, App Config) is a need

"Knox does device management well. App distribution is a different discipline: a branded private store, public apps via managed Google Play and Apple VPP, App Config / Managed App Configuration to push pre-configured corporate apps to targeted groups. Knox stays at app push, that's it. If you have internal corporate apps to publish with policies, you'll bolt something on top of Knox."

Objections

Knox Platform for Enterprise is free; Knox Manage (the MDM console) is paid at $24/seat/year. And 'free' covers Samsung Android only, every iPhone, Mac, Windows laptop, or non-Samsung Android in your fleet needs a different solution. The total bill, on a mixed fleet, isn't lower than Appaloosa.

True for the hardware-rooted certifications (Common Criteria, FIPS 140-2, DISA). Those matter for US/UK military use cases. For French public sector and OIV/OSE, the question is different: do you have SecNumCloud? Appaloosa does. Samsung doesn't. Different geographies, different doctrines.

If that's a 5-year lock-in, fair point. But 'we'll always be Samsung' rarely holds: executives ask for iPhones, finance gets a Mac, IT puts Windows laptops on the road. The day the first non-Samsung device shows up, Knox stops being one console. Worth pricing the alternative now.

Questions to ask the prospect

Open-ended questions that expose competitor weaknesses without naming them.

  1. 1
    What share of your fleet is non-Samsung Android, iOS, Mac, or Windows today, and how will it look in 24 months?
    If non-zero or growing, Knox alone won't cover it. Surfaces the mixed-fleet problem.
  2. 2
    Does your CISO require SecNumCloud or only ISO 27001?
    Knox doesn't have SecNumCloud. If required, conversation is over.
  3. 3
    How do you publish a pre-configured corporate app (App Config) to a targeted group on Knox today?
    Knox stays at basic app push, no branded private store with App Config publishing. Surfaces the MAM gap.
  4. 4
    Who handles support when a Knox issue happens at 11pm, Samsung directly or your reseller?
    Knox support runs partner-led for most EU mid-market. Surfaces the support latency angle.
Appaloosa
Appaloosa
VS
NinjaOne
NinjaOne

US-based RMM/IT-management platform that has added MDM in recent years. Strong Windows/Mac/Linux endpoint depth, fast pricing on volume. Mobile MDM is recent and basic. AWS-hosted, US parent, Cloud Act exposure.

Key differentiators

Sovereignty
Appaloosa is SecNumCloud + FR-hosted. NinjaOne is on AWS regions of your choice, but the US parent company is subject to the Cloud Act regardless of region.
Mobile-first MDM
Appaloosa was born MDM/MAM. NinjaOne started as RMM and added MDM later, mobile features are shallower and less mature than the endpoint side.
MAM depth
Branded private app store, App Config / Managed App Config, targeted publishing are core Appaloosa. NinjaOne MDM does basic app push only.

Profile

Parent company
NinjaOne, Inc. (US, Texas)
Platforms
Windows · Mac · Linux · Android · iOS · iPadOS
Hosting
AWS, customer-selected region
Certifications
SOC 2 Type 2, SOC 3, ISO 27001, FedRAMP Moderate, GovRAMP, NIS2 aligned
Public pricing
$1.50-$3.75/endpoint/mo (volume tiers)
Origin
RMM-first, MDM added later
Target
MSPs, IT teams managing mixed endpoints
Cloud Act exposure
Yes (US parent + AWS)

Comparison matrix

Supported platforms
Context-dependent
Appaloosa
iOS, iPadOS, macOS, Windows, Android
NinjaOne
Windows, Mac, Linux, Android (8+), iOS (10+)
Sovereignty / hosting
Appaloosa
Appaloosa
SecNumCloud (France) + ISO 27001
NinjaOne
AWS, customer-selected region, US parent
Cloud Act / FISA compliance
Appaloosa
Appaloosa
Outside US jurisdiction
NinjaOne
Subject (US parent + AWS)
Android depth (Work Profile, Kiosk, COPE, Managed, Zero Touch)
Appaloosa
Appaloosa
Work Profile, Fully Managed (COBO), COPE, Kiosk (COSU), Zero Touch
NinjaOne
Basic Android Enterprise (work profile, kiosk), recent addition
iOS depth (BYOD, Managed, Kiosk, ADE)
Appaloosa
Appaloosa
Supervised, Kiosk Single/Multi-App, ADE via ABM, simplified MAM profile for BYOD
NinjaOne
ADE via ABM, VPP, MDM policies, basic
Mac depth
Context-dependent
Appaloosa
Advanced: ABM, DEP, Configuration Profiles
NinjaOne
Apple MDM via ABM, configuration profiles
Windows depth
Competitor
Appaloosa
Basic: enrollment + app deployment
NinjaOne
Mature RMM (patching, scripting), MDM modern less developed
Private store (private + public apps, App Config, Managed Config)
Appaloosa
Appaloosa
Private + public apps, App Config (Android), Managed App Config (iOS)
NinjaOne
App available/deny/force install, VPP via Apps and Books
Remote Support
Context-dependent
Appaloosa
Natively integrated
NinjaOne
NinjaOne Remote (RMM endpoint feature, Windows-strong)
File deployment
Context-dependent
Appaloosa
Supported
NinjaOne
RMM-style: scripting, software push (endpoint-focused)
Contact sync
Appaloosa
Appaloosa
Supported
NinjaOne
Not documented publicly
Onboarding
Appaloosa
Appaloosa
Self-serve + dedicated CSM, FR support < 5 min
NinjaOne
Self-service or MSP-led, English-first
Target & complexity
Context-dependent
Appaloosa
SMB, mid-market, enterprise mixed fleets
NinjaOne
MSPs, multi-tenant IT, mixed endpoints
Integrations
Context-dependent
Appaloosa
SAMLv2, Okta, M365, Google Workspace
NinjaOne
RMM stack, FedRAMP / GovRAMP, SOC 2
Pricing
Appaloosa
From €3.49/device/month
NinjaOne
$1.50-3.75/endpoint/mo (volume tiers)

Where Appaloosa wins

  • Sovereignty for FR / EU regulated workloads
    NinjaOne is US-headquartered + AWS-hosted = Cloud Act applies. SecNumCloud excludes them by definition. Appaloosa fits the spec.
  • Real MDM/MAM heritage
    Mobile is our origin, not an add-on. Branded private store, App Config (Android) and Managed App Config (iOS), targeted publishing are mature on Appaloosa, basic on NinjaOne MDM.
  • FR support speed
    FR support < 5 min is concrete. NinjaOne support is English-first, with partner overlay for EU mid-market.
  • Simpler scope = clearer adoption
    Sales/marketing teams adopt Appaloosa faster than a full RMM/MDM stack. Less training, less change management.

Where the competitor wins

  • Unified RMM + MDM for MSPs
    If the customer is an MSP managing 1000s of endpoints across many tenants, NinjaOne's multi-tenant + RMM + MDM stack is the right tool. Appaloosa is single-tenant focus.
  • Volume pricing
    $1.50/endpoint/mo at 10k+ devices is hard to beat for an IT-ops perspective. Pure-price RFPs at scale go to NinjaOne.
  • Endpoint depth (patching, scripting, automation)
    Native scripting, patch management, remote control. Appaloosa doesn't compete on this layer.
  • FedRAMP / GovRAMP for US public
    Required for US federal contracts. Appaloosa doesn't compete in that geography.

Talk tracks

If NinjaOne is on the shortlist for a mixed-endpoint RFP

"NinjaOne is solid for IT ops. Two questions to scope: (1) is your priority endpoint compliance + patching, or app distribution + sovereignty? (2) who handles the mobile side, IT ops or product/marketing teams? If priority is app lifecycle for mobile and FR sovereignty, NinjaOne isn't built for that. We are."

If the prospect is using NinjaOne for endpoints and considering it for mobile too

"Keep NinjaOne for what it does best, Windows/Mac patching, scripting, RMM. The mobile MDM module they ship is recent. Pair it with Appaloosa for the mobile + Mac layer: branded private store, App Config / Managed App Config for pre-configured corporate apps, targeted publishing. Many of our customers run exactly this combo."

If sovereignty is on the radar (FR public, regulated industries)

"NinjaOne is fine for non-regulated workloads. The moment your project specs SecNumCloud or excludes US-jurisdictioned providers, NinjaOne is out, US parent + AWS hosting. Appaloosa was built specifically for that spec."

Objections

'All-in-one' is great when each module is best-in-class. NinjaOne's RMM is. Their MDM module is recent: basic app push (available / deny / force install), VPP, but no branded private app store, limited App Config workflows, English-first support. If your mobile use case is more than 'lock + wipe + push an APK', NinjaOne MDM will frustrate you. Appaloosa beside NinjaOne RMM is a known pattern.

Region choice limits residency, not jurisdiction. NinjaOne is a US company on AWS, both fall under the Cloud Act. SecNumCloud was created precisely to close that gap. If your CISO or DPO has flagged the Cloud Act, region selection on NinjaOne doesn't solve it.

Per-endpoint, yes. The right comparison is feature parity on what you actually need: if you need RMM + basic MDM, NinjaOne wins on price. If you need a branded private app store with App Config / Managed App Config publishing + FR sovereignty + native Remote Support, NinjaOne doesn't ship those at any price. Cheap on a feature you don't have isn't a saving.

Questions to ask the prospect

Open-ended questions that expose competitor weaknesses without naming them.

  1. 1
    Are you primarily an MSP managing many tenants, or an in-house IT team for a single company?
    If MSP, NinjaOne shines. If in-house single-tenant, NinjaOne advantage shrinks.
  2. 2
    How do you publish a pre-configured corporate app (App Config / Managed App Config) to a targeted group via NinjaOne today?
    NinjaOne MDM stays at install/deny/force; surfaces the lack of branded private store with native App Config publishing.
  3. 3
    Has your CISO or DPO formally flagged the Cloud Act as a risk?
    If yes, NinjaOne is excluded by their own internal policy.
  4. 4
    Who answers when a mobile incident happens at 11pm in Paris, NinjaOne directly in English or your reseller?
    Surfaces FR support latency vs Appaloosa < 5 min.
Appaloosa
Appaloosa
VS
PushManager (IBELEM)
PushManager (IBELEM)

French Android-only MDM published by IBELEM, a French ESN. Strong field/kiosk fit, integrator-led delivery. Sovereignty argument is similar to Appaloosa, differentiation moves to MAM, cross-OS, and product depth.

Key differentiators

Cross-platform reach
Appaloosa covers iOS, iPadOS, macOS, Windows, Android. PushManager is Android only, same single-OS limit as TinyMDM.
MAM-first product
Appaloosa branded private store, App Config / Managed App Config, targeted publishing are core product. PushManager focuses on device control + app push.
Product vs services model
Appaloosa is a self-serve product with FR support < 5 min. PushManager often comes via IBELEM project services, integrator-led delivery, longer cycles.

Profile

Editor
IBELEM (FR ESN)
Platforms
Android only
Hosting
France (to confirm with IBELEM)
Certifications
Public certifs not documented in our research, to verify
Pricing
Not public, quote-based via IBELEM
Delivery model
Integrator-led (IBELEM services)
Target
Field, retail, kiosks, FR mid-market
Sovereignty stance
FR-rooted, similar to Appaloosa

Comparison matrix

Supported platforms
Appaloosa
Appaloosa
iOS, iPadOS, macOS, Windows, Android
PushManager (IBELEM)
Android only
Sovereignty / hosting
Context-dependent
Appaloosa
SecNumCloud (France) + ISO 27001
PushManager (IBELEM)
France (IBELEM, FR ESN)
Cloud Act / FISA compliance
Context-dependent
Appaloosa
Outside US jurisdiction
PushManager (IBELEM)
Outside US (FR vendor)
Android depth (Work Profile, Kiosk, COPE, Managed, Zero Touch)
Context-dependent
Appaloosa
Work Profile, Fully Managed (COBO), COPE, Kiosk (COSU), Zero Touch
PushManager (IBELEM)
Android Enterprise (kiosk-strong, dedicated devices, COPE)
iOS depth (BYOD, Managed, Kiosk, ADE)
Appaloosa
Appaloosa
Supervised, Kiosk Single/Multi-App, ADE via ABM, simplified MAM profile for BYOD
PushManager (IBELEM)
Not supported
Mac depth
Appaloosa
Appaloosa
Advanced: ABM, DEP, Configuration Profiles
PushManager (IBELEM)
Not supported
Windows depth
Appaloosa
Appaloosa
Basic: enrollment + app deployment
PushManager (IBELEM)
Not supported
Private store (private + public apps, App Config, Managed Config)
Appaloosa
Appaloosa
Private + public apps, App Config (Android), Managed App Config (iOS)
PushManager (IBELEM)
Authorized apps for kiosk + APK distribution
Remote Support
Context-dependent
Appaloosa
Natively integrated
PushManager (IBELEM)
Remote management (specifics not public)
File deployment
Appaloosa
Appaloosa
Supported
PushManager (IBELEM)
Not documented publicly
Contact sync
Appaloosa
Appaloosa
Supported
PushManager (IBELEM)
Not documented publicly
Onboarding
Appaloosa
Appaloosa
Self-serve + dedicated CSM, FR support < 5 min
PushManager (IBELEM)
Integrator-led (IBELEM project services)
Target & complexity
Appaloosa
Appaloosa
SMB, mid-market, enterprise mixed fleets
PushManager (IBELEM)
Field, retail, kiosks, Android-only fleets
Integrations
Appaloosa
Appaloosa
SAMLv2, Okta, M365, Google Workspace
PushManager (IBELEM)
Via IBELEM services, public list not documented
Pricing
Appaloosa
From €3.49/device/month
PushManager (IBELEM)
Quote-based via IBELEM

Where Appaloosa wins

  • Cross-OS by design
    PushManager is Android-only. Any iPhone, Mac, Windows machine in the fleet needs a separate tool, total cost of ownership inflates fast.
  • MAM heritage
    Branded private app store, App Config / Managed App Config for pre-configured corporate apps, public apps via managed Google Play and Apple VPP. PushManager focuses on device control + app push.
  • Product self-serve, no integrator dependency
    Customer onboards on Appaloosa in days, FR support < 5 min. PushManager often runs through IBELEM project services with longer cycles.
  • Verified SecNumCloud
    Both editors are French, but only Appaloosa is publicly listed as SecNumCloud + ISO 27001. PushManager certifications were not found in our public research.

Where the competitor wins

  • Pure Android field/kiosk depth
    If the fleet is 100% Android in the field (retail, logistics, manufacturing, kiosks), PushManager has a strong heritage in that vertical.
  • Integrator-led delivery for risk-averse buyers
    Some customers want a single contract with an ESN for the project. IBELEM's services + PushManager bundle covers that.
  • FR-anchored, similar sovereignty story
    Both editors are French, the 'choose French' argument doesn't differentiate as much vs PushManager. Need to lean on product depth.

Talk tracks

If PushManager is on the table because of a French sovereignty preference

"Both Appaloosa and PushManager are French, that's a tie on origin. The conversation moves to two questions: (1) is the fleet 100% Android forever, or will iPhones, Macs, Windows arrive? (2) do you need a branded private app store with App Config / Managed App Configuration to publish pre-configured corporate apps to targeted groups? On (1), Appaloosa is the only FR option that covers all OSes. On (2), Appaloosa was built MAM-first."

If IBELEM is suggesting PushManager bundled with services

"IBELEM's services-led model fits some customers very well. Question to ask honestly: do you want a vendor or a project? Appaloosa is a self-serve product with FR support < 5 min, your IT team owns it. PushManager + IBELEM is a project, IBELEM owns it. Both are valid; they're answering different needs."

If field/retail/kiosk Android is the main use case

"PushManager has heritage in Android field deployments, that's real. We have customers running the same use case on Appaloosa. The question is what's around the kiosk: do head office tablets, store managers' iPhones, head-quarter Macs need to be in the same console? If yes, Appaloosa is the right call; if it's truly only kiosks forever, PushManager is competitive."

Objections

French headquarters is a starting point, not a destination. The actual sovereignty test is the certification: Appaloosa is publicly listed as SecNumCloud + ISO 27001. PushManager's certifications weren't found in our public research, worth asking IBELEM for an explicit list. If they don't have SecNumCloud, your project specs may exclude them.

Convenience matters. Two checks: (1) is the bundle pricing actually competitive once you isolate the product line vs services line? (2) what happens when you want to switch integrator in 3 years, are you locked into IBELEM, or can you take the product elsewhere? Appaloosa as a self-serve product avoids both questions.

Honest question on the time horizon: in 24 months, do you expect zero iPhones in the executive team, zero Macs in design or marketing, zero Windows laptops in finance? In our experience, 'pure Android' rarely stays pure. The cost of switching to a multi-OS MDM later is higher than choosing one now.

Questions to ask the prospect

Open-ended questions that expose competitor weaknesses without naming them.

  1. 1
    Does IBELEM include explicit SecNumCloud or ANSSI certification language in the proposal?
    If 'French' is asserted but the certifications aren't listed, the gap appears.
  2. 2
    What's your projected mix of Android / iOS / Mac / Windows in 24 months?
    Surfaces multi-OS need against PushManager's Android-only.
  3. 3
    How do you publish a pre-configured corporate app (App Config) to a targeted group on PushManager today?
    Tests App Configuration / Managed App Configuration support and branded private store. PushManager focuses on kiosk and device control.
  4. 4
    If you wanted to switch integrator from IBELEM, can you keep PushManager?
    Tests vendor lock-in around the services bundle.
Appaloosa
Appaloosa
VS
iDruide
iDruide

French multi-OS MDM with strong specialization in education (schools, lycées, public sector). FR-hosted, GDPR + Carmo + Carine compliant. Limited fit for general enterprise / agile BYOD use cases.

Key differentiators

Vertical fit
Appaloosa serves enterprise / mid-market across industries. iDruide is education-first, strong on schools, weaker on agile mobile teams, BYOD enterprise, app lifecycle.
MAM maturity
Appaloosa branded private store, App Config / Managed App Config, targeted publishing are core. iDruide is built for distributing curriculum apps in classrooms, different use case.
FR sovereignty parity
Both are French and FR-hosted. The differentiation isn't 'choose French', it's 'choose enterprise-grade vs education-grade' for the specific use case.

Profile

Editor
iDruide (FR)
Platforms
Android · iOS · Windows · ChromeOS
Hosting
France
Compliance
GDPR, Carmo, Carine (education frameworks)
Pricing
~€2/device (per Notion card, not public)
Target
Education (schools, lycées, public sector)
Trial
Demo before trial, no free trial
Specialty
Web Secure (internet filter) + classroom management

Comparison matrix

Supported platforms
Context-dependent
Appaloosa
iOS, iPadOS, macOS, Windows, Android
iDruide
Android, iOS, Windows, macOS, ChromeOS
Sovereignty / hosting
Context-dependent
Appaloosa
SecNumCloud (France) + ISO 27001
iDruide
France-hosted, GDPR + Carmo + Carine
Cloud Act / FISA compliance
Context-dependent
Appaloosa
Outside US jurisdiction
iDruide
Outside US (FR editor)
Android depth (Work Profile, Kiosk, COPE, Managed, Zero Touch)
Context-dependent
Appaloosa
Work Profile, Fully Managed (COBO), COPE, Kiosk (COSU), Zero Touch
iDruide
Zero Touch, PED, Autopilot, QR Code, DPC ID, education focus
iOS depth (BYOD, Managed, Kiosk, ADE)
Appaloosa
Appaloosa
Supervised, Kiosk Single/Multi-App, ADE via ABM, simplified MAM profile for BYOD
iDruide
Apple supported, education-oriented (less depth than Appaloosa)
Mac depth
Appaloosa
Appaloosa
Advanced: ABM, DEP, Configuration Profiles
iDruide
Apple supported but secondary to Android/Chromebook
Windows depth
Context-dependent
Appaloosa
Basic: enrollment + app deployment
iDruide
Windows + Autopilot enrollment
Private store (private + public apps, App Config, Managed Config)
Appaloosa
Appaloosa
Private + public apps, App Config (Android), Managed App Config (iOS)
iDruide
MAM + MIM, education-app distribution
Remote Support
Context-dependent
Appaloosa
Natively integrated
iDruide
Remote management (orders, reports, configs)
File deployment
Context-dependent
Appaloosa
Supported
iDruide
MIM (Mobile Information Mgmt) supported
Contact sync
Appaloosa
Appaloosa
Supported
iDruide
Not documented publicly
Onboarding
Appaloosa
Appaloosa
Self-serve + dedicated CSM, FR support < 5 min
iDruide
Demo before trial, partner-led
Target & complexity
Appaloosa
Appaloosa
SMB, mid-market, enterprise mixed fleets
iDruide
Education (schools, lycées, public sector)
Integrations
Appaloosa
Appaloosa
SAMLv2, Okta, M365, Google Workspace
iDruide
Carmo, Carine (education frameworks)
Pricing
Appaloosa
From €3.49/device/month
iDruide
Quote-based (~€2/device per Notion)

Where Appaloosa wins

  • Enterprise / mid-market fit
    Appaloosa is built for cross-industry corporate use, sales, finance, manufacturing, healthcare. iDruide is built for schools.
  • Mature MAM for corporate apps
    Branded private store, App Config (Android) / Managed App Config (iOS), public apps via managed Google Play and Apple VPP, targeted publishing. iDruide focuses on classroom-app distribution.
  • Non-intrusive BYOD
    Internal Notion notes flag iDruide BYOD limitations, rigidity, state-loss after inactivity. Appaloosa was built BYOD-agile from day one.
  • Pre-configuration of corporate apps
    Outlook, internal CRM, M365 apps with pre-set policies, supported on Appaloosa, gap on iDruide per internal sources.

Where the competitor wins

  • Schools and lycées
    Carmo, Carine alignment, Web Secure internet filter, classroom management. iDruide owns this vertical in France.
  • ChromeOS / Chromebook fleets
    'Chromebook à la française' positioning, strong fit for education ChromeOS deployments.
  • FR + education public sector knowledge
    Long-running relationships with French Ministry of Education / régions. We don't have the same depth.

Talk tracks

If iDruide is on the table for a non-education use case

"iDruide is a serious vendor for schools. For your use case (enterprise / mid-market / BYOD / app lifecycle), it's the wrong fit, they admit it themselves by positioning education-first. Appaloosa is built for what you're describing: corporate apps, cross-OS, non-intrusive BYOD, mature MAM."

If iDruide is on a hybrid education+admin RFP (lycée + collectivité)

"For the school side, iDruide makes sense, Carmo, Carine, Web Secure. For the administrative side (mayor's office, technical staff iPhones, Macs of department heads), iDruide isn't the right tool. Some of our customers run iDruide for classrooms and Appaloosa for staff. They are complementary."

If sovereignty / FR is the primary criterion

"Both Appaloosa and iDruide are French and FR-hosted, sovereignty isn't the differentiator. The real question: what does the fleet need to do? If it's classroom learning, iDruide. If it's enterprise app distribution + cross-OS BYOD, Appaloosa."

Objections

Right. Sovereignty is a tie. The conversation moves to product fit: does iDruide cover non-education use cases (corporate BYOD, app lifecycle, cross-OS Mac/iPhone executives)? Per our research and internal feedback, it doesn't. Appaloosa does.

iDruide can cover both technically, but the admin side is not where they invest. Internal feedback flags BYOD rigidity and missing pre-configuration of corporate apps like Outlook. For the school side they're the right call; for the admin side, look at Appaloosa or run both in parallel.

On the school price band, possibly. The right comparison is feature parity for your actual use case: if you need a branded private store with App Config / Managed App Config publishing, non-intrusive BYOD, pre-configured corporate apps like Outlook, iDruide doesn't ship those at the corporate-grade level. Cheap on a feature you can't use isn't a saving.

Questions to ask the prospect

Open-ended questions that expose competitor weaknesses without naming them.

  1. 1
    Is your primary use case classroom-based education or general corporate device management?
    Self-disqualifies iDruide outside education.
  2. 2
    Do you need to pre-configure Outlook, M365, or internal corporate apps with policies?
    iDruide has reported gap here per internal sources.
  3. 3
    Do users keep devices for weeks without active use, then come back? Does the device need to keep its policies?
    iDruide reportedly loses state after long inactivity.
  4. 4
    Will the perimeter include iPhones for staff, Macs for executives, Windows laptops in management?
    Surfaces cross-OS depth gap on iDruide for non-education use.