Smplify · Field Note · 001
THE STUDY OF CONVERGENCE
RELEASE · 3 SECTORS
07 · 2026
Three platforms, one governed plane

In July 2026, over one weekend release, Smplify stopped being an Apple MDM and became a device control plane. Plate 001 is the drawing of that moment: three platforms converging on a single governed point, published alongside the release itself.
This note explains what shipped, and more importantly what each piece is worth to the people who run fleets for a living.
§ 01 · How to read the plate
The solid dot at the centre is the control plane. Every sector radiates from it because that is the architecture: one place where intent is declared, one place where policy is enforced, one place that speaks each platform's native protocol so nothing else has to.
THE TEXTURE LEGEND
- SOLID continuous arcs are macOS: years of accumulated capability, drawn as unbroken lines.
- DASHED arcs are Windows: newly assembled, drawn as segments still joining up.
- DOTTED arcs are Linux: ephemeral cloud instances, drawn as scattered points.
EVERY TEXTURE IS A PLATFORM · EVERY SPOKE CROSSES A GATE
The squares on the spokes are approval gates, and one of them carries two bars where the others carry one. We leave that unexplained on purpose. There is also a message hidden somewhere in the drawing, in Morse. It has been there since the day we published it.
§ 02 · What shipped, and why it matters
Windows, natively. Enrollment over the OMA-DM protocol, configuration through CSP policies, BitLocker, Defender, OS updates, and MSI app deployment. The value is not the checkbox; it is that Windows joined the same policy model as Apple. You describe what should be true once, and the plane translates it into each platform's dialect. No second console, no second policy language, no second team.
Linux, without scripts pretending to be management. A hardening engine covering firewall, SELinux and AppArmor, SSH, auditd, PAM, disk encryption and kernel parameters, with drift detected and remediated automatically. For the security lead, the value is that Linux stops being the fleet's unmanaged corner. Both platforms shipped rolling out, not GA, and we said so at the time.
Approval Gates. High-blast-radius actions stopped executing on a single keystroke. A wipe, a mass unenroll, a production policy change: each one now waits for a separate authorized human, with the gate enforced inside the platform where no client can route around it. This is separation of duties as architecture, and it is the foundation everything since has built on.
Dual-channel macOS updates, ADDE and ADUE enrollment, OCSF telemetry to your SIEM. Enrollment met users where they are, updates stopped being all-or-nothing, and every privileged action on the plane began streaming out in an open schema your security stack already reads. Device management started speaking the language of the SOC.
§ 03 · What changes at the admin's desk
The honest measure of a release is what stops being your job. This one retires a few of the worst ones.
The second console goes away. Before this release, a mixed fleet meant one tool for Macs, another for Windows, scripts and a wiki page for Linux, and three places where the same intent could drift apart. Now disk encryption everywhere is one policy. The plane compiles it into a DDM declaration for the Mac, a CSP policy for Windows, and a hardening rule for Linux, and reports drift against all three in one place. Fewer consoles is not a convenience; it is fewer places to be wrong.
Two in the morning gets safer. Approval Gates mean the tired keystroke cannot wipe a fleet. The action queues, a second person approves from their phone, and the audit trail writes itself. Admins do not lose speed on routine work; tiers apply to the action, not the person, so low-risk changes flow and high-blast-radius ones wait for a colleague.
Updates stop being a gamble. Dual-channel macOS updates mean a test ring sees the release before the fleet does, from the same policy surface. And because every action lands in your SIEM in OCSF, the security team stops asking you to export CSVs to prove what happened. The evidence is already in their stack, in their schema.
§ 04 · The thesis underneath
Everything above shares one property: none of it requires an endpoint agent. The plane manages through each platform's native protocol, which means nothing to install, nothing to conflict with your EDR, and nothing for an attacker to live inside.
Three platforms did not get three products. They got one plane.
CONVERGENCE IS THE RELEASE · THE PLATE JUST DRAWS IT
FIELD NOTE 001 · THE STUDY OF CONVERGENCE · 07 2026