Managing Homebrew at Scale: oversight and autonomy for your Mac fleet
Managing Homebrew at scale means balancing two forces that pull in opposite directions: IT needs oversight of what gets installed, and developers need the tools to do their jobs. Lock things down too tight and you create a shadow IT problem. Leave Homebrew unstructured and you lose visibility into what's running across your fleet.
In this session, we'll walk through how Workbrew puts both within reach - giving admins the visibility and policy enforcement they need, and giving developers a path to self-serve the tools they want without waiting on a ticket or a manual install.
📅 Thursday April 21st, 2026
🕐 9:00 AM PDT | 12:00 PM EDT | 4:00 PM UTC | 5:00 PM BST
📍 Zoom
Why attend You'll Learn
- Set guardrails on software installs across your Mac fleet with Policies while enabling developers to keep shipping
- Turn blocked installs into Package Requests, a self-serve approval workflow that empowers developers and gives admins a full audit trail
- Use Package Tags (AI-generated software categories) to see what's actually installed across your fleet and build policy by software type, not just package name
- Spot policy drift, outdated packages, and access gaps early with the Workbrew Console and its actionable dashboards
- Manage
brewaccess per device and configure it directly from the Console — no scripts, no SSH - Extend your existing MDM with Homebrew-layer visibility and oversight — Workbrew sits alongside - Fleet, Iru, Intune, Jamf, Mosyle, and the rest, not in place of them
Who should attend
- macOS IT admins responsible for managing or securing developer fleets
- Security managers who want software visibility and policy enforcement that empowers developers
- IT leaders evaluating how to bring Homebrew under management at scale
Agenda
- The oversight vs. autonomy problem – Why traditional MDM leaves gaps when developers are involved, and how Homebrew management fits in
- Package Requests – How blocked installs automatically become admin-reviewable requests, without anyone leaving the Terminal or the Console
- Package Tags and catalog intelligence – Using AI-generated categories to understand your fleet and build policy by software type, not just package name
- Fleet visibility and access management – Knowing who has brew access on each device and configuring it directly from the Console
- Actionable dashboards – Surfacing what needs attention and making it possible to act without navigating away
- Q&A
Hosts

John Britton