Monitoring for the Macs an MSP or an IT consultant is responsible for — the ones nobody enrolled in an MDM, sitting on desks and kitchen tables. It checks the things that actually go wrong, and says what it found in a sentence.
Not a dashboard of gauges. A list of Macs with something wrong, worst first, each with the specific fact rather than a severity score.
Fifty-six checks, each its own script, covering backups, encryption, disk, updates, battery, network, accounts and the security settings people quietly turn off. A check that cannot run says so — it never guesses, and it never reports a permission problem as a clean bill of health.
One notarized package for every customer. Your technician types the client's name at install; that is what says whose Mac it is. No per-customer build, no waiting on a notarization queue when you sign somebody new.
Every view prints properly, because a sheet left on a client's desk is still how a lot of this work gets communicated. The same stylesheet lays out the page and the paper.
Write a shell script, sign it on your Mac, roll it out to a few machines first. twotwelve stores a signature it cannot forge — the private key never leaves your laptop.
Anything you can do in the browser, a script can do with a token. Nobody should have to drive a headless browser to automate their own fleet.
Never a person's documents, media, messages, browsing history, or what they use their Mac for. System and configuration signals only.
The four checks that need a user's own settings — screen lock, Apple ID, iCloud, and which browser extensions are installed — run as that user, read only named preference paths, and report identity-level facts: an extension's name and version, an email address, whether a lock is set. Never content, never history, never another person's data.
Every script is published, so an MSP can point an auditor at exactly the code that runs on their customers' Macs.
twotwelve is in private testing with its first fleet. If you run Macs for other people and this sounds like the tool you have been improvising, write to [email protected].