I read three fresh takes on Munki so you don't have to. Here's the debrief.

Exhibit A: The Home Lab Rebel

Steve Quirke, self-described "Mac Nerd, Motorcyclist, 2cv fan," decided that using SimpleMDM's managed version of Munki was too easy, so he set out to rebuild the whole thing from scratch in a home lab — the sysadmin equivalent of turning off GPS to "really learn the city."

His plan: skip Docker Desktop entirely, because its licensing changes gave him actual professional trauma, and use Colima instead. This also meant finally, grudgingly, installing Homebrew — something he'd apparently been avoiding since his university days like it personally owed him money.

The best part is his very first docker run command immediately failed, because of course it did. Quirke's whole vibe is refreshingly honest about how much of DevOps is improvisation:

"It's all about knowing enough to be dangerous."

He eventually got an Nginx container serving files from a folder cheekily renamed from "web" to "munki" — which is basically the tech equivalent of putting a name tag on a rental car and calling it yours. And in true Greg Neagle fashion (the actual creator of Munki), the whole philosophy boils down to one delightfully unglamorous truth:

"A munki server is just a webserver."

Somewhere, an entire industry of enterprise MDM vendors is quietly sweating.

Exhibit B: The Minimalist Who Wants No Part of This

Then there's Alan Siu, who shows up to the Munki bootstrapping conversation, drops two genuinely useful open-source tools — a signed package and a script for zero-frills Munki bootstrapping — and then, in the most refreshingly unbothered developer move of 2025, essentially shrugs and walks away:

"I don't use these myself, but I'm hoping you may find one of these two projects helpful"

That's it. That's the whole post. No dashboard, no "We're setting up your Mac!" progress bar, no swiftDialog theatrics. Just a login window quietly reinstalling things and rebooting until it's satisfied, like a Roomba that occasionally needs to restart the whole house to get under the couch.

Exhibit C: The Consultants Who Have Seen Some Things

Finally, the London-based MSP Stabilise weighed in with the most grown-up take of the three, opening with the tone of someone who has had this exact argument at a client dinner too many times:

"Munki is not dead, not abandoned, and not obsolete."

Their headline news: Munki 7 ditched its Python guts entirely and got rewritten in Swift — which is a genuinely wild glow-up for a tool most people associate with cron jobs and hope. But their real point is sharper than "it's still alive": Munki was never trying to be an MDM, so asking "does it beat Jamf" is like asking whether a screwdriver beats a toolbox. It doesn't compete with your MDM — it sits quietly underneath it, doing the unglamorous job of actually getting software onto machines without stepping on itself mid-install.

They also drop the delightfully petty detail that they personally don't run Munki at all, preferring Installomator instead — which feels like showing up to a birthday party for someone else's favorite tool just to explain, calmly, why you have a different favorite tool.

Put the three side by side and you get a strangely complete picture of open-source software's whole emotional lifecycle:

1. The tinkerer rebuilds it in a home lab for fun, half-fights Docker licensing, and calls it a learning experience.

2. The pragmatist ships something genuinely useful, then disclaims all personal attachment to it.

3. The professionals show up years later to calmly explain that everyone's been arguing about the wrong question, then quietly recommend a different tool anyway.

Munki, for its part, just keeps installing software at login screens, blissfully unaware it's the subject of three separate personality types' worth of internet content. Long may it reboot.