TestFlight is Apple's official iOS beta channel and the default recommendation for most testing scenarios. But it has limits — and for some workflows, those limits are dealbreakers. Here's when to bypass TestFlight and what to use instead.

TestFlight's real limits

  • Maximum 10,000 external testers — fine for most apps, but a problem for large rollouts
  • 90-day build expiry — testers can only run a build for 90 days, then it stops launching
  • Beta App Review — external testers require Apple to approve each build, taking 24-48 hours
  • App Store-style guidelines — Apple can reject your beta for the same reasons they'd reject the public app
  • Public link visibility — TestFlight public links are indexable and can be shared widely (sometimes unwanted)

When you should bypass TestFlight

  • You're testing app content/behavior that's against App Store guidelines (gambling, emulators, alternative app stores, etc.)
  • You need testers to have indefinite access without 90-day expirations
  • You're doing internal company testing and don't want any external review
  • You need installs faster than the 24-48 hour review cycle allows
  • You're past 10,000 testers
  • The app uses entitlements TestFlight doesn't permit in beta

Option 1: Ad-Hoc distribution (small teams)

Best for: under 100 known testers with registered UDIDs. Uses an Apple Distribution certificate with an Ad-Hoc profile listing each device.

  • Cost: $99/year Developer Program
  • Max devices: 100 per device class per year
  • Validity: 1 year
  • No Apple review

The downside: collecting UDIDs from testers and adding each to the profile is manual work.

Option 2: Enterprise distribution (large/unknown audience)

Best for: distributing to anyone, regardless of device. Uses an Enterprise certificate.

  • No UDID collection
  • Unlimited devices
  • One-tap install via web link
  • Apple revoke risk if the audience is too broad/public

This is what most professional beta channels and "alternative app stores" use. The downside is the revoke risk — if Apple detects mass public distribution, the certificate dies and all installs stop simultaneously.

Option 3: Hybrid — TestFlight + Enterprise

Common pattern: use TestFlight for the official beta within App Store rules, and Enterprise signing for private builds with content TestFlight wouldn't allow, or for testers without an Apple ID.

Practical workflow

For most teams bypassing TestFlight:

  1. Build the IPA in Xcode without signing (or with a placeholder).
  2. Hand the IPA to a signing service.
  3. Distribute the resulting install link to testers via Slack, email, internal portal.
  4. If you need a new build, repeat — turnaround is usually minutes.

For continuous beta workflows, see also enterprise iOS distribution for companies.