Skip to content
Machinery Software · Apple device management

The fleet repository lives
inside the product.

mngd hosts your fleet repository itself. Propose a change, read the gates' refusal in plain English, apply the exact commit you were shown — then read what the Mac says it did, in its own words.

Join the waitlist Read the receipt

mngd is early and not generally available. There is no trial to start and no account to create yet — the waitlist is the whole front door, and what is below is what has actually run.

The loop

Propose, refuse, apply, attest.

In the mode mngd hosts the repository, the whole loop runs on a directory: no forge, no external CI service, no credential, no token, and nothing to configure on somebody else's server. [E-116]

  1. 01

    Propose

    A change to the fleet is a branch in the repository, with its title, author and date read off the tip commit. Nothing about the proposal lives in a table that could disagree with git.

    E-116
  2. 02

    Read the refusal

    Three gates run in-process and answer in plain English, each able to fail on its own. A refusal names what is wrong and what to run next — and the command it recommends has to be able to succeed against the state that produced it.

    E-112 · E-125
  3. 03

    Apply the commit you were shown

    Fast-forward only, as a law rather than a limitation: the merged tree IS the reviewed tree. Applying compiles desired state out of the repository this instance hosts, not out of something baked into a release.

    E-119
  4. 04

    Let the Mac answer

    Desired state and device-reported state sit side by side. When the console says an app is installed, that is the device attesting it — including the identifier of the declaration it says caused the install.

    E-130
A receipt, quoted

When the console says installed, that is the Mac talking.

On 2026-09-11 a MacBook Air installed Google Chrome from a declaration this repository holds, and reported back with the version on the device and the identifier of the declaration it says caused it. Both panels below are quoted out of the device page — the left is what git asked for, the right is what the Mac answered.

Declared — what git asks for
Google Chrome 153.0.8010.37 com.google.Chrome from roles/baseline/com.mngd.package.google-chrome.json role baseline declaration com.mngd.package.google-chrome Install behaviour Required
Reported — what the Mac says
installed version on the device: 153.0.8010.37 name: Google Chrome Because git said so the device names this declaration com.mngd.package.google-chrome Verdict installed

E-130 — one MacBook Air against a staging instance, panel timestamped 2026-09-11 12:30 UTC. No agent was involved: macOS did the install because a declaration told it to.

What is proven, and where

Two different words: on hardware, and in a container.

A Mac installed a package because a declaration said so
One MacBook Air, watched on the device page, reported by the device. [E-130]
on hardware
Propose, gate, apply, and compile from the hosted repository
Run end to end in its own container with a generated admin token. No device was involved in this one. [E-112, E-116, E-119]
in a container
Everything else
Not claimed here. When a thing has been watched working, it gets a Field Note and an evidence ID; until then this page stays quiet about it.
not yet

We haven't seen another MDM that hosts the repository itself. That is an observation about what we have looked at, not a claim about what exists — config-as-code for Apple fleets is a road with other people already on it, and they are named here.

Want to watch this get built?

The waitlist gets the Field Notes — what ran, what refused, and what the device said, with the evidence ID attached. No launch dates, because there aren't any.

Join the waitlist Read the Field Notes