Enterprise iOS App Distribution: Every Option Explained

Who this guide is for

You have an iOS app that does not belong in the public App Store — an internal tool, a field-operations app, a client-facing app for a specific customer — and you need it on somewhere between ten and a few thousand iPhones and iPads. This guide compares the main distribution routes, their eligibility and operational costs, where each one breaks, and how to choose.

It is written by the team behind AppDeploy, a private app distribution platform, and we link to our own product where relevant. The guide covers every Apple route, TestFlight and Custom Apps included, so you can see how each one works before you choose.

The main enterprise iOS distribution routes at a glance

Apple offers several distribution routes, and many rollout problems come from using one beyond what it was designed for. In brief: the public App Store (everyone can see it), TestFlight (beta testing, builds expire after 90 days), Custom Apps through Apple Business (private distribution over App Store infrastructure), Unlisted App Distribution (App Store hosting, link-only visibility), the Apple Developer Enterprise Program (enterprise-signed in-house distribution for eligible organisations), and MDM-based managed app installation (silent install on supervised devices). Ad Hoc distribution, which installs an app directly on devices registered in a developer account (up to 100 per product family each membership year), is mainly a testing tool and is not covered further here.

Apple Business (formerly Apple Business Manager, often shortened to ABM) is the current name to use when planning Custom Apps, Apps and Books licences, and eligible device assignments. Older guides and existing administrator workflows may still use the ABM name.

Many organisations combine two or three. The rest of this guide takes each in turn, then gives you a decision framework.

TestFlight is for testing, not internal distribution

TestFlight is Apple's beta-testing service: up to 10,000 external testers and up to 100 internal testers from your App Store Connect team, with builds delivered through the TestFlight app. The first build you add for external testers goes through TestFlight App Review. For testing pre-release builds it is genuinely excellent, and it is free.

The problems start when teams use it as a permanent distribution channel. Every build expires 90 days after upload, so a team has to keep supplying fresh builds. Testers must use the TestFlight app, and its tester activity is not the same as a production record of which employees are entitled to which release on managed devices. If a field team depends on the app every day, choose a production route before build expiry becomes an operational deadline.

Use TestFlight for what it is: the testing stage before one of the real distribution routes below.

Since October 2025, Managed Apple Accounts can be invited to TestFlight, although accounts created in reserved domains cannot test builds.

The Apple Developer Enterprise Program: a restricted in-house route

The Apple Developer Enterprise Program (ADEP) lets eligible organisations distribute proprietary in-house apps directly to employees outside the App Store. It is a specific programme for internal use, not a general shortcut around App Review.

Apple limits this programme to organisations with 100 or more employees and proprietary internal-use apps whose needs are not adequately met by its other distribution routes. Membership, signing certificates, and provisioning profiles need ongoing care; expiration or revocation can interrupt installed apps. Membership costs 299 USD a year and needs a legal entity with a D-U-N-S number, a verification interview and continuing evaluation. Distribution provisioning profiles expire after 12 months, and the distribution certificate after three years or when membership ends, whichever comes first; revoking the certificate invalidates every app signed with it. On iOS and iPadOS 18 and later, an in-house app installed manually rather than through device management needs a device restart to complete trust of its provisioning profile.

If you already hold ADEP membership, enterprise-signed .ipa delivery remains useful for eligible internal apps; through AppDeploy, in-house apps install on enrolled company devices. If not, check Apple's current eligibility criteria before planning around that route; Custom Apps through Apple Business are often the better starting point.

Custom Apps through Apple Business: Apple's intended answer

Custom Apps are one of Apple's supported routes for private business distribution. Your app goes through App Review, but instead of appearing publicly it is offered privately to the specific organisations you choose through Apple Business. Each new version also goes through App Review, which Apple says typically takes one to two days. Distribution then works through Apps and Books: licence-based assignment to devices or Managed Apple Accounts, or redemption codes handed to individual users.

The strengths are real: no TestFlight-style 90-day build expiry, App Store hosting and updates, and no in-house distribution certificate to manage. The frictions are also real: your app must pass App Review, the receiving organisation needs Apple Business set up, and the underlying licence and account workflow takes planning. Redemption codes work without device management, but only managed distribution, which needs a device management service, lets the organisation revoke and reassign licences while keeping ownership of them. AppDeploy can sync Apps and Books content and give employees a branded place to find approved apps.

Unlisted App Distribution: link-only App Store access

Unlisted apps are hosted on the App Store but discoverable only with a direct link. Apple suggests them for limited audiences such as part-time employees, franchisees and partners, and they can also be reached through Apple Business and Apple School Manager.

The app must already be on the App Store or be ready for final distribution and submitted to App Review; Apple declines requests for apps in a beta or prerelease state. Anyone with the link can download the app, so a link is not an access-control boundary: protect sensitive data with the app's own sign-in.

MDM-managed installation: silent, powerful, and priced accordingly

Mobile Device Management can install apps silently on enrolled, supervised devices — no tap, no App Store visit, combined with configuration profiles, OS update enforcement and device actions. On company-owned, supervised hardware it is the gold standard for zero-touch operation, and paired with Automated Device Enrollment (ADE) a new iPhone configures itself out of the box.

Two costs come with it. The first is commercial and operational: some third-party MDM products charge per device, and an IT team must maintain enrolment, certificates, policies, and support. Apple Business now includes free built-in device management; AppDeploy builds on Apple Business with a branded app store, deployment evidence and AutoDeploy, its own device management with release controls. The second is the employee conversation: enrolling a personal phone raises legitimate questions about what the organisation can see and remove. Apple's User Enrollment mode limits the management boundary, but you still need a clear policy and informed users.

The honest question is whether app delivery is the job, or device management is. If you need OS updates enforced, settings applied or a lost iPhone or iPad locked or erased, those devices need management: AutoDeploy, AppDeploy's device management, covers iPhones, iPads and Macs on macOS 14 or later, with the first 5 devices free.

The portal model

In the portal model, employees open a branded page to find approved apps. The portal can record entitlement and user actions; installing an app, and showing that it stays installed, is the job of device management on enrolled devices.

For a team with one to a few private apps and a mix of personal and company phones, list the apps in one place and install them on the company devices that need them. AppDeploy offers the branded portal with Distribution, and AutoDeploy, which installs your private apps on enrolled company iPhones and iPads: free for the first 5 devices and priced per device beyond that (Enterprise by agreement).

The trade-off to state plainly: a portal cannot put anything onto a device. A device that should receive your apps needs enrolment.

Compare the full cost of each route

For 100 recipients, compare more than a headline subscription. TestFlight has no distribution fee but requires an ongoing beta-release process. Custom Apps require App Review and the receiving organisation's Apple Business setup. Enterprise-signed delivery requires eligible membership plus certificate and hosting operations. Third-party MDM may add per-device cost and ongoing enrolment support, while Apple Business includes built-in device management. AppDeploy has no base fee: up to 5 devices are free, and each device beyond 5 is £1 a month or £10 a year; Distribution, your own branded app store, is £29 a month or £219 a year, with or without devices.

Ask each vendor what happens when a new employee joins, a device is replaced, an app fails, or you need proof of an installed version. Use a dated quote in the same currency and include device minimums, app limits, onboarding work, and management features you actually need. AppDeploy's current prices are published on its pricing page.

Security and compliance: what reviewers actually ask

Whichever route you choose, procurement and security reviews converge on the same questions. Who can install this app, and how is that entitlement removed when someone leaves? Where is the evidence of who installed what, and when? Are binaries hosted and transferred securely, with integrity guarantees? What happens when a signing certificate or push certificate expires? Can you export the audit trail?

Two certificate deadlines deserve calendar entries wherever you land: enterprise provisioning profiles (annual) and the Apple MDM push certificate (annual — if it lapses, managed delivery stops for every enrolled device at once). And if an auditor or a customer asks you to show that deployed app versions are current, that is much easier when your distribution tool keeps device records and audit logs as a by-product. This is why audit trails and compliance evidence are not enterprise garnish on a distribution platform; they are the part you will be asked for.

A decision framework

Pre-release app for known testers: use TestFlight. Production app private to named organisations: consider Custom Apps in Apple Business. App Store-hosted app for a broader link-based audience: consider Unlisted App Distribution. Company-owned devices needing policy enforcement and confirmed installs: enrol them with AutoDeploy, AppDeploy's device management. Eligible in-house app outside App Review: consider ADEP with careful signing operations. Mixed fleet with one to a few private apps: install them on the enrolled company devices that need them.

App count is not the deciding factor. Ownership, installation method, enforceable removal, and the evidence you need after rollout are more important. The related 1–3 app decision guide walks through those questions in detail.

A first-two-weeks rollout plan

Day one: pick the route with the framework above. Set up Apple Business if your chosen route needs it. Days two to three: submit a Custom App for App Review or prepare an eligible signed build, then configure branding, access, and the installation instructions for each device group.

Week one: pilot with a few real users and enrolled devices; watch where installation fails. Week two: expand by enrolling more devices with a shared enrolment link or QR code. Review the evidence separately: a portal visit or install request is not an installed app, while a managed device can report installation state. Follow up on unknowns rather than counting them as successes.

Common failure modes to pre-empt: an enrolment profile built with a temporary tunnel URL that later dies (use a stable HTTPS hostname from day one); Apple Business devices left unassigned to the intended MDM service during Automated Device Enrollment; and too few Apps and Books licences for the devices receiving the app. Each needs a different fix, even when the employee simply reports that installation stalled.

Managed Apple Accounts, federation, and licence assignment

Apple Business supports Managed Apple Accounts, including accounts federated with identity providers such as Microsoft Entra ID or Google Workspace. The older terms Managed Apple IDs, Apple Business Manager, and ABM may still appear in existing customer instructions.

Before a rollout, confirm that the Custom App is available to the intended organisation, that enough licences exist, and that the chosen device-based or user-based assignment route matches the device and account setup. Account creation and invitation are separate from proving that an app installed.

Device-based assignment can avoid a user account on a supervised device, but it requires the appropriate managed-device path. For personally owned phones, confirm the permitted installation route and privacy expectations before asking anyone to enrol.

What about Android?

If your organisation also uses Android devices, note that Android's landscape is simpler in one way — a signed APK can be installed without any Apple-style gatekeeping — and messier in another: 'sideloading' without management raises real security review questions, and Google's managed alternative (Managed Google Play with private apps) requires Android Enterprise enrolment much as Apple's managed routes require MDM.

The same portal-versus-management logic applies, though AppDeploy does not manage Android devices. If you need a private APK delivered to known people with an audit trail, portal delivery of a signed APK does the job: AppDeploy supports this as an extra on its Enterprise plan. Plan the two platforms together rather than letting each team pick its own route: reviewers ask about both, and one audit story is easier to tell than two.

Frequently asked questions

Can employees install a private app without a Managed Apple Account?

Yes, in some routes. Device-based assignment on an eligible managed device does not require the employee to sign in with a Managed Apple Account. An unmanaged App Store installation normally uses the person's Apple Account. Enterprise-signed delivery requires the distributor to qualify for Apple's Enterprise Program.

Does a private app need App Review?

Custom Apps and Unlisted App Store apps go through App Review. TestFlight is for beta testing and has its own review process for external testers. Eligible in-house enterprise-signed apps are distributed outside the App Store, but Apple restricts that programme.

What happens when someone leaves?

Revoke their portal access immediately. On an eligible managed device, the organisation can request removal of a managed app and verify the outcome. On an unmanaged personal device, revoking access does not by itself prove that the binary was removed; sensitive data should also be protected by the app's own authentication and server-side access controls.

Is there a TestFlight alternative for internal apps?

Yes. TestFlight is for beta testing, and each build expires after 90 days. For production internal apps, use Custom Apps through Apple Business or, if your organisation is eligible, enterprise-signed apps. AppDeploy lists Custom Apps in your branded app store and installs them on enrolled company iPhones and iPads; in-house apps install on enrolled company devices. The person may be asked to accept an install.

Is 90 days really the TestFlight build limit?

Yes. Each TestFlight build expires after 90 days. If a production workflow depends on continually replacing beta builds to keep an app running, move to a production distribution route.

What is the difference between TestFlight and production app distribution?

TestFlight distributes beta builds to testers, and each build expires after 90 days. Production distribution keeps an approved release available to the right employees, with updates and removal when people leave, through Custom Apps, managed distribution or an eligible in-house route.

Is Apple Business the same as Apple Business Manager?

Apple Business replaced Apple Business Manager, Apple Business Essentials and Apple Business Connect when it launched on 14 April 2026, and Apple says it combines the capabilities previously found in those services. Custom Apps, apps and books licences and device assignment are now managed in Apple Business.

Primary sources

• Apple Developer: business app distribution — Current Custom App, Unlisted App, and in-house distribution choices.
• Apple Developer Enterprise Program — Current eligibility and use restrictions for proprietary internal apps.
• Apple Business announcement — How Apple Business replaced Apple Business Manager and added built-in device management.
• Apple Platform Deployment Guide: Custom Apps — Apple's current guidance for privately distributing Custom Apps to organisations and devices.
• Apple Business: Learn about Custom Apps — App Review for each Custom App version, typically one to two days.
• Apps and Books distribution in Apple Business — Managed distribution compared with redemption codes.
• TestFlight overview — Tester limits, build expiry and TestFlight App Review.
• Invite external testers — External tester invitations, including the reserved-domain rule for Managed Apple Accounts.
• Apple Business Manager release notes (archived) — October 2025: Managed Apple Accounts can be invited to TestFlight.
• Unlisted app distribution — Eligibility and limits for link-only App Store apps.
• Apple Platform Deployment: in-house apps — Certificate and profile lifetimes and installation rules for proprietary in-house apps.
• Apple Developer: registered devices — Device registration limits for Ad Hoc distribution.