Skip to content
Install Core free
ProductsCompare Core, Hub, Connect and MDM pricing
Solutions
Docs
ResearchPricing
CompareCompare all AI data-leak tools
TrustBenchmarks
Start 30-day free trial

Shadow Hub for your business

Tell us about your team and we'll help you get started.

We use these details only to reply to your enquiry. No newsletter, no cookies, no trackers.

Shadow MDM vs traditional MDM: suggest-first device management compared

Pick a traditional MDM if you need full device lifecycle management: app distribution, every configuration profile, zero-touch enrolment and complete Apple and Windows management. Consider Shadow MDM if you don’t have an MDM yet and need the compliance baseline for ISO 27001, SOC 2 or ISO 42001, or if you want AI-tool controls and audit evidence alongside the MDM you already run.

Shadow MDM overview · Pricing

“Traditional MDM” here means the category of device management platforms in general, not any one product; capabilities vary by vendor and plan.

Traditional MDMShadow MDM
What it isA device management platform, usually with its own agent or OS enrolment profileIncluded in Shadow Hub, built into the Shadow agent (Rust) you already run for AI privacy
Extra agentUsually its own agent or enrolmentNone beyond Shadow; no osquery, no Fleet
How changes happenAn admin configures policies and pushes themShadow writes Proposals (what, why, evidence, impact, when, if you don’t); an admin approves
RolloutDepends on the platform and how groups are set upPilot group first, health checks, auto-pause, one-click rollback
TimingUsually scheduled by the adminEach laptop’s learned idle window
Compliance baselineBuilt by the admin, often from CIS templatesChosen from your frameworks: framework minimums, strictest wins
Audit evidenceReports and exports, varying by vendorEnforcement Map from framework to device, point-in-time view, auditor role, signed exports
AI tools on laptopsUsually app-level allow or blockAI traffic through Shadow, personal data masked, approved AI tools and MCP servers, local model runtimes
App distribution and profilesYes, a core featureNo
Zero-touch enrolmentCommonly supportedNo
macOS remote lock and wipeYes, through Apple MDMComing (Apple certificate pending)
LinuxVaries widelyPosture checks; disk encryption is report-only
Lock and wipe approvalOne admin, typicallyAlways two admins
Price modelPer device or per user, varying by vendorIncluded in Shadow Hub at $3 per user per month; Enterprise priced on request
  • Small and mid-sized teams preparing for an audit that have no MDM and need the endpoint controls in place with evidence. See Pass ISO 27001 without an MDM.
  • Teams adopting ISO 42001 or preparing for the EU AI Act that need controls over AI tools on laptops. See ISO 42001 for AI on laptops.
  • Teams that already run an MDM and want posture evidence and the Enforcement Map without changing their MDM. Shadow never fights another MDM: on devices that report one, it only reports posture.
  • You need to distribute and update apps, certificates, Wi-Fi and VPN profiles.
  • You buy devices through Apple Business Manager or Windows Autopilot and want zero-touch enrolment.
  • You need macOS remote lock and wipe today.
  • You manage phones and tablets as well as laptops.

Deploy Shadow with your MDM (how), keep the MDM in charge of settings, and use Shadow for AI privacy, posture evidence and the AI controls. If you later move devices off the MDM, Shadow MDM can take over enforcement, one approved Proposal at a time.

Frequently asked questions

Should we replace our current MDM with Shadow MDM?

Usually not, if it works for you. Traditional MDM platforms do far more than Shadow MDM: app distribution, configuration profiles for every setting, device enrolment programmes, and full Apple and Windows management. Shadow MDM is for teams without an MDM who need the compliance baseline, and it works alongside an existing MDM without fighting it.

What can't Shadow MDM do yet?

It does not distribute apps or manage arbitrary configuration profiles, and macOS remote lock and wipe through the Apple MDM protocol are coming (Shadow's Apple certificate is pending). Disk encryption on Linux is report-only.

Why suggest-first?

Because most MDM incidents are changes pushed to everyone at the wrong time. Shadow writes a Proposal with evidence and impact, waits for approval, then rolls out to a pilot group with health checks and one-click rollback.