How to Distribute an iOS App Without the App Store (2026)

You can distribute an iOS app without the App Store in four legitimate ways: Apple's TestFlight, ad hoc distribution to registered devices, the Apple Developer Enterprise Program (employees only), and third-party over-the-air (OTA) tools. Which one fits depends on who your testers are, how fast you need builds in their hands, and how many devices you're targeting.

The App Store is the right channel for a public release. But during development you rarely want it: reviews add delay, and you're not shipping to the world — you're handing a build to a teammate, a QA engineer, or a client who needs to click something today. Here's every legitimate route, and how to choose.

The four ways, compared

Method	Who can install	Review?	Limit	Build expiry	Needs UDID?
TestFlight	Anyone you invite (email/link)	Yes, for external testers	100 internal / 10,000 external	90 days	No
Ad hoc	Only pre-registered devices	No	100 devices per type / year	Certificate lifetime	Yes
Enterprise Program	Your employees only	No	Internal use only	Certificate lifetime	No
OTA tools (e.g. Appisto)	Anyone with the link	No	Depends on plan	You control it	Automated

1. TestFlight

TestFlight is Apple's own beta platform. Internal testers (up to 100 App Store Connect users) get builds instantly; external testers (up to 10,000) can join by public link, but the first build of each version must clear Beta App Review first — usually around a day.

Good for: larger beta groups, public betas, teams already living in App Store Connect. Watch out for: every build expires after 90 days with no extension, external testers wait on review, and it's iOS-only — no help if you also ship Android. Testers also need the TestFlight app installed.

2. Ad hoc distribution

Ad hoc lets you install a build on specific iPhones or iPads whose UDIDs you've registered in the Apple Developer portal and baked into the provisioning profile. No review, no waiting — but only listed devices can run the build.

Good for: fast internal testing, quick client demos on known devices. Watch out for: you're capped at 100 devices per product type per membership year, and the count only resets once a year at renewal — disabling a device doesn't free a slot. You also have to collect every tester's UDID up front, which is the classic ad hoc headache. (See our guide on finding and registering a UDID and the 100-device limit.)

3. The Apple Developer Enterprise Program

The Enterprise Program ($299/year) issues certificates for distributing apps to your own employees, outside the App Store. It sounds like the answer to "just let me hand out builds" — but it isn't, for most teams.

Apple is explicit that enterprise distribution is for internal employees only. Using it to ship to external clients or public testers violates the agreement, and Apple has revoked certificates for exactly this — famously bricking Facebook's and Google's internal apps in 2019. It also requires 100+ employees to qualify. For anything client- or tester-facing, use one of the other three methods. (More on Developer vs Enterprise Program.)

4. Over-the-air (OTA) distribution tools

OTA tools wrap the ad hoc mechanism in a usable product. You upload a build, share a link or QR code, and the tester installs directly — the tool handles the manifest.plist, HTTPS hosting, UDID collection and build management for you. (Here's how OTA installation works under the hood.)

This is where Appisto fits: it distributes iOS and Android builds over the air with no store review, collects testers' UDIDs automatically instead of making you chase them, and plugs into your CI/CD via a REST API so every build lands in front of your team the moment it's built. It's EU-hosted and GDPR-compliant by design — which matters if your testers' data can't leave Europe. Unlike TestFlight, builds don't expire on a 90-day clock, and unlike ad hoc alone, you're not manually wiring up profiles and manifests. If a public release is also on your roadmap, see the iOS App Store review process and mastering mobile app releases; the Appisto workflow shows how to wire uploads into CI.

Which should you choose?

• Large or public beta, iOS only: TestFlight.
• A handful of known devices, need it now: ad hoc — or an OTA tool to skip the manual setup.
• iOS and Android from one place, or EU data residency: an OTA tool like Appisto.
• Distributing to your own employees at a 100+ person company: the Enterprise Program (and only then).

Frequently asked questions

Can I distribute an iOS app without the App Store for free? Yes. TestFlight is free with a $99/year Apple Developer membership, and ad hoc distribution works with the same membership. OTA tools typically have free tiers — Appisto's includes one app and 10 build uploads a month.

How do I send an iOS app to a client without TestFlight? Register the client's device UDID for an ad hoc build, or use an OTA tool that collects it automatically and sends them a one-tap install link — no App Store Connect account needed on their side.

Does an ad hoc build expire? It stays installable until its signing certificate or provisioning profile expires (up to a year), not on a fixed 90-day clock like TestFlight.

Key takeaways

• There are four legitimate ways to distribute an iOS app without the App Store: TestFlight, ad hoc, the Enterprise Program (employees only), and OTA tools.
• TestFlight suits large betas but is iOS-only and expires builds after 90 days.
• Ad hoc is instant but limited to 100 registered devices per type per year.
• The Enterprise Program is not a legal route to external testers.
• OTA tools like Appisto give you instant, cross-platform, review-free distribution with automated UDID collection — the closest thing to "just hand them the build."