Apple's TestFlight is the most famous way to beta-test an iOS app, but it is far from the only one. Whether you are blocked by TestFlight's 10,000-tester limit, need faster turnaround than Apple's beta review allows, or simply want to send a build to a handful of internal testers, there are several practical ways to distribute an iOS app for testing without going through the App Store. This guide walks through the main options and when each one makes sense.

Why look beyond TestFlight?

TestFlight is excellent for public betas, but it introduces friction: every build is reviewed by Apple (usually within a day, but occasionally longer), testers must install the TestFlight app, and you are capped at 10,000 external testers per app. For rapid internal iteration, executive demos, or enterprise rollouts, those constraints can slow you down. The alternatives below let you ship an .ipa directly to a device.

Option 1: Ad-hoc distribution

Ad-hoc distribution lets you install a build on up to 100 devices per year (per Apple Developer account) that you have registered by their UDID. You sign the build with a development or distribution certificate, embed an ad-hoc provisioning profile listing those UDIDs, and distribute the resulting .ipa.

It is ideal for:

  • Small QA and internal testing teams
  • Demoing a build on a known set of devices
  • Situations where you need a build in minutes, not a day

The main cost is operational: every new device must have its UDID added to your developer account, the provisioning profile regenerated, and the app re-signed. For more than a few dozen testers this becomes painful to manage by hand.

Option 2: A web-based install page (.plist + OTA)

This is where a dedicated download platform shines. iOS supports over-the-air (OTA) installation: you host a small .plist manifest that points to your signed .ipa, and an itms-services:// link tells Safari to download and install the app. To the tester, the experience is almost as smooth as the App Store: they open a link or scan a QR code, tap "Install," and the app appears on their home screen.

The build still needs to be ad-hoc or enterprise signed — the OTA mechanism is a delivery channel, not a signing method — but the platform handles the manifest generation, QR code, and install page for you.

A single download page with a QR code removes the back-and-forth of emailing .ipa files and .mobileprovision files. Testers just scan and install.

Option 3: Apple Developer Enterprise Program

If you are distributing an app purely inside one company and never to the public, the Apple Developer Enterprise Program ($299/year) lets you sign apps that can be installed on any device the company controls, without registering UDIDs and without the 100-device limit. The certificate is tied to your organization and must not be used to distribute outside the company.

Enterprise distribution is powerful but comes with strict responsibilities. Apple has cracked down on enterprise certificates being misused to distribute apps to the general public, so this path is genuinely for internal, in-house apps only.

Option 4: MDM (Mobile Device Management)

For organizations, an MDM solution can push an internal app to managed devices silently or via a self-service catalog. MDM pairs naturally with enterprise-signed builds (or the App Store's private app distribution) and gives IT control over which devices get which version.

Choosing the right approach

  • Public beta at scale → TestFlight is still the right default.
  • Fast internal builds to known devices → ad-hoc distribution via an OTA install page.
  • Company-wide internal app → enterprise signing + a private download page or MDM.

What testers actually see

Whichever method you choose, the tester's first run will show an "Untrusted Enterprise Developer" (for enterprise builds) or a similar trust prompt the first time they open the app. This is expected: iOS requires the user to manually trust non-App-Store developers in Settings → General → VPN & Device Management before the app will launch. Documenting this one step in your install page cuts down almost all "it doesn't open" support tickets.

The takeaway

You do not need the App Store — or even TestFlight — to get an iOS app onto testers' devices. For most teams, a combination of ad-hoc or enterprise signing with a hosted OTA install page offers the best balance of speed, control, and tester experience. The signing model is the constraint; everything else is just delivery, and a good distribution platform makes that delivery effortless.