Homebrew + Jamf Pro
Jamf manages your Macs. EnterpriseBrew manages what Homebrew is allowed to put on them. Together they close the gap MDM alone can't: open-source packages developers install themselves, outside the App Store and outside packaging pipelines.
Deploy through Jamf, once
Roll out the EnterpriseBrew agent to your fleet with a Jamf policy using the standard install script or package. After that, every brew install on those machines routes through your policies automatically.
Approved packages in Jamf Self Service
Publish curated Homebrew packages to Jamf Self Service with one click, icons included. Employees install approved developer tools the same way they install everything else — no terminal required, no tickets.
Device inventory that matches your MDM
EnterpriseBrew syncs devices and groups from Jamf, so package policies can be scoped to the same smart groups you already maintain. Fleet inventory shows what is installed where, per device.
Policy enforced at install time
Jamf answers "what is on the machine"; EnterpriseBrew answers "what is allowed onto the machine". Allowlists, blocklists, license rules, and minimum versions are enforced server-side the moment a developer runs brew install — with every decision written to the audit log under the real user and hostname.