The short answer
MDM.Plus is delivered only as SaaS. We do not sell private deployment, buy out the system, or release source code. That is not simply about protecting trade secrets — it follows from how the platform is built, how risk is controlled, and where responsibility sits.
1. The architecture is built for the cloud
From day one this has been a multi-tenant SaaS platform, not software installed in a customer server room. It uses a cloud-native stack — a unified task queue, message bus, push gateway, configuration centre, monitoring and logging — and depends on managed services such as object storage, databases, caching, message queues, KMS and WAF. Under this design, packaging a copy for a customer is not a matter of copying code: each customer would need a system rebuilt for their local environment. Multiple custom versions then make every upgrade, patch and policy change slower and less stable, which is why unified cloud delivery is the premise for consistent service quality.
2. Keeping source control limits exposure
In device supervision, Activation Lock detection and rental risk control, the security of the running system matters more than the code itself. With SaaS, source stays in controlled internal repositories, while code, configuration and keys sit under one security boundary. A buyout or private deployment puts source into many customer environments and outsourcing teams. Each added environment increases the chance of leakage, reverse engineering or misuse. For bypass actors, source is effectively a textbook for studying detection logic, so limiting its spread is designed to help reduce risk across the industry.
3. The value is continuous updates, not one-time delivery
- Keep pace with Apple protocol and system-version changes.
- Keep refining supervision policies and risk rules, and keep countering new bypass methods.
- Deploy changes on the platform side; all customers sync automatically instead of running separate upgrade projects.
In a buyout model, upgrades become separate projects and budgets, so many environments age even while the system appears to run. For high-risk rental business, security capability that lags by six months or years is more dangerous than having no system.
4. Operations and responsibility stay with us
SaaS gives every customer the same high-availability and disaster-recovery base: multi-availability-zone deployment, data redundancy, automatic failover, unified monitoring and alerting, and 7×24 incident response. Replicating that in one server room is costly, and a local power or network failure can halt everything. We would rather customers invest in acquisition, risk strategy and operations. Under our contract the responsible party is clear: core systems, network and security policies are run by us, with audit and access-control trails that can be traced, and we take the first responsibility when a security issue occurs.
The final scope is subject to the confirmed product specification and service agreement.
