myMDM vs OpenText ZENworks Patch Management

myMDM is an open-core unified endpoint management platform for managing device fleets from one console. Its self-hosted core, released under AGPL-3.0, includes a policy engine, platform agents, enrollment, app management, identity federation, and a web console. Listed device support spans Apple Declarative Device Management and classic MDM, Android Management API, Windows OMA-DM, a Linux agent, and ChromeOS enrollment. Policies cover passcodes, Wi-Fi, VPN, restrictions, OS updates, compliance, mobile threat defense integration, geofencing, and workflow automation. App tools include managed apps, an enterprise catalog, and automated third-party patching for 100+ titles. Identity options include LDAP/AD sync, SAML 2.0, OIDC, SCIM 2.0 provisioning, and role-based access control. The managed product is marked “Coming Soon” and invites visitors to join a waitlist. Free covers up to 25 devices; Pro is $4 a month. Self-hosting supports Docker, Docker Compose, and Helm, with stated requirements including Docker 24+ or Kubernetes 1.28+, PostgreSQL 15+, and a public HTTPS endpoint for callbacks.

OpenText ZENworks Patch Management has no write-up on Specifiction yet; its figures are above.