macOS software packaging
Mac application packaging customized to your needs
What is Mac application packaging - and why outsource it?
Mac application packaging means turning a vendor’s app into a standard installer that runs on its own – the same way on every Mac you manage.
Nobody has to drag anything into the Applications folder. The installer puts the files in the right directory, sets the permissions macOS expects, applies your settings, and runs any scripts needed before or after installation. When it finishes, it reports back to your management tool.
macOS uses three delivery formats, and they are not interchangeable:
- .pkg – the native installer format. A pkg file bundles a payload (the files to be installed) with a distribution definition and optional scripts. It is the only format most deployment tools accept directly.
- .dmg – a disk image. Convenient for manual downloads, but it is a container rather than an installer, so it usually has to be repackaged before it can be deployed.
- .app – the application bundle itself. Technically a folder that macOS treats as a single object, which still needs wrapping into a pkg file for managed installation.
On top of the format, packages have to be code-signed with an Apple Developer ID and, in most cases, notarised. Without that, Gatekeeper blocks the installation on current macOS versions.
That combination is why many organisations hand the work over. Doing it in-house means maintaining macOS packaging expertise, a signing certificate, a test environment covering both Intel and Apple Silicon, and a repeatable process for every application update. For teams whose primary platform is Windows, that is a lot of specialist knowledge for a comparatively small share of the estate.
For a deeper explanation of the concepts, our guide on application packaging and deploying for macOS walks through the formats and the deployment process in detail.
Mac packaging - efficient, secure, and built for Mac software deployment
How we package your Mac software, step by step
Every project follows the same five steps, from source file to finished deployment. You stay in control of the requirements; we do the packaging work.
Step 1 – You send us the source. The vendor installer, any licence or configuration details, and a short note on how the application should behave.
Step 2 – We build the package. Files, folder structure and permissions are defined, install parameters set, and any pre- or post-install scripts written to match your requirements.
Step 3 – We sign and notarise it. The package is code-signed with an Apple Developer ID and, on request, notarised by Apple so Gatekeeper does not block the installation.
Step 4 – We test it. Installation, uninstallation and upgrade over an existing version are verified on both Intel and Apple Silicon, and the payload is scanned for malware.
Step 5 – You deploy it. The finished pkg file arrives ready for upload to Intune, Jamf or another MDM, together with detection rules, scripts and documentation.
Mac packaging - What you get
A fully managed service that covers package creation, testing and Mac software deployment readiness. Packages are built to match your specification and support modern Mac environments, including Apple Silicon, custom configurations and Intune-based delivery.
Support for key macOS formats
Packages delivered in .pkg, .dmg, or .app format - based on your deployment preferences.
Support for Intel and Apple Silicon
Packages created for Intel-based (x86_64), Apple Silicon (arm64), or as a universal build - depending on your requirements.
Built to your requirements
Custom install logic, scripts and configuration, applied exactly as you specify.
Signed, tested, and notarized
Every package is code-signed, scanned for viruses and malware, tested, and notarised by Apple on request.
Intune, Jamf and other MDM tools
Packages are structured for your existing deployment tool. We fit into your process rather than replacing it.
Minimal input required
Only the source application and packaging instructions are needed — all packaging, testing, and delivery are handled by our experts.
When to use our Mac application packaging service
Packaging for Mac brings requirements that Windows tooling does not cover. These are the cases we see most often.
Ideal for:
- Creating one universal installer for Intel and Apple Silicon Macs
- Upgrades that remove the previous version cleanly instead of leaving it behind
- Delivering apps that need custom install logic or post-install actions
- .pkg files prepared for Microsoft Intune or Jamf
- Packaging work that has no owner because in-house macOS expertise is limited
These are typical scenarios rather than a fixed list. Non-standard and custom setups are part of normal work. If your estate is mostly Windows, our Windows application packaging service covers the other side of the same process.
Frequently asked questions about Mac application packaging
What is Mac application packaging?
It is the process of converting an application into a standardised installer that can be deployed automatically to managed Mac devices. Packaging defines which files are installed, where they go in the directory structure, what scripts run before and after installation, and how the software is configured on first launch - so that every device ends up in the same state without anyone touching it.
Which formats do you deliver (.pkg, .dmg, .app)?
Primarily .pkg, because it is the format Intune, Jamf and other deployment tools consume directly. We also work with .dmg and .app as source material: a disk image or an application bundle is unwrapped, its payload inspected, and rebuilt as a signed pkg file that installs silently. If your process requires a different output format, we build to your specification.
How do you deploy Mac packages via Intune or Jamf?
We build the package so it fits your existing deployment tool - we do not replace it. For Microsoft Intune, a signed pkg file can be uploaded as a macOS app or converted to the .intunemac wrapper, with detection and pre-install scripts included where needed. For Jamf, packages are delivered ready for upload to your distribution point, together with any scripts and installation parameters. The same package works with other MDM platforms as well.
Do you support Apple Silicon and Intel (universal builds)?
Yes. Packages are built for Apple Silicon (arm64), Intel (x86_64), or as a universal build that covers both from a single installer. Which one makes sense depends on the vendor: some applications ship a universal binary, others require separate builds.
What is code signing and notarisation, and do we need it?
Code signing attaches your organisation's Apple Developer ID to the package so macOS can verify its origin. Notarisation is an additional check by Apple that scans the payload for malicious code. On current macOS versions, unsigned or un-notarised installers are blocked by Gatekeeper, so for managed deployment both are effectively mandatory. We handle signing and, on request, notarisation as part of the packaging work.
What do you need from us to get started?
The source files and your packaging requirements. That usually means the vendor installer, any licence or configuration details, and a short description of how the application should behave - silent installation, custom settings, scripts to run, versions to remove first. Everything else, including testing and documentation, is handled on our side.
How are Mac applications kept up to date after packaging?
A package reflects one version of an application. When the vendor ships an update, the package has to be rebuilt, tested and released again. Some organisations handle that internally and send us each new version; others prefer a standing arrangement so updates are packaged as they appear. We are happy to discuss which model fits your release cycle.
Can you package in-house and legacy applications?
Yes. Internally developed tools, older applications without a modern installer, and software that needs custom install logic are all part of normal packaging work. Where an application has no usable installer at all, we repackage it - capturing the files, folders and settings it requires and rebuilding them as a clean pkg file.