TestFlight review

TestFlight is Apple's managed beta-distribution service for app builds. It sits between a developer's build process and the people testing an app: teams distribute builds for beta testing rather than running their own tester-download service. Apple lists TestFlight among its downloads and says the Apple Developer Program includes beta-testing tools.

This is not a library or self-hosted server that becomes part of an application's runtime. It is a distribution endpoint in the development and release workflow. TestFlight supports internal testing for up to 100 testers, with up to 30 devices per internal tester, and external testing for up to 10,000 testers per app. Developers can test up to 100 apps at a time. Builds expire after 90 days, so teams need to account for build replacement in their testing cycles.

Apple presents TestFlight as a beta-distribution tool, not as an API product. The integration surface established by Apple's developer homepage is build distribution: TestFlight is listed under Downloads, and the Apple Developer Program includes beta-testing tools. The homepage also links to a Documentation Library, Sample Code, Xcode and Developer Forums.

Apple's homepage does not name a TestFlight REST API, SDK, CLI, programming language or plugin. Treat TestFlight as a managed distribution step, not a service your app calls at runtime. Before automating build submission or tester management, confirm the supported workflow and any SDK or API options in Apple's current documentation. The homepage also lists App Store Connect Help, but that alone does not establish a specific TestFlight integration. There is no basis here to assume a language-specific SDK or a command-line workflow.

TestFlight is not sold as a separate plan, and the pricing information lists no free TestFlight plan. Apple includes it with the Apple Developer Program, which costs $99 per year. Monthly billing is not published. The annual membership works out to $8.25 per month when divided across the year, but the stated billing is annual.

The membership includes the listed testing capacity: up to 100 internal testers, up to 30 devices per internal tester, up to 10,000 external testers per app and up to 100 apps tested at a time. Builds expire after 90 days. The pricing information lists no TestFlight add-ons or per-tester overage charges, so the bill does not grow by a published usage rate as testers or apps increase within those limits. Instead, the constraints are capacity and build expiry. Teams that exceed the external-tester cap need to manage access or find another distribution approach; no higher TestFlight tier is listed.

TestFlight is an Apple-operated service, not a package developers can install on their own infrastructure. Apple's developer homepage does not publish a TestFlight-specific open-source license or a self-hosting option. That makes the service dependent on Apple's distribution workflow and membership rather than infrastructure your team controls.

The practical lock-in is in the beta-testing process: tester access and build distribution run through TestFlight, so moving to another service means setting up a different distribution workflow and asking testers to use it. Apple's developer homepage does not publish TestFlight data-export terms. Before relying on the service for a long-running program, check what tester or testing records you need to retain independently and whether your release process can switch distribution tools without disrupting testers.

The main production constraints are explicit: external testing is capped at 10,000 testers per app, internal testing at 100 testers, each internal tester can use up to 30 devices, and builds expire after 90 days. The 100-app capacity can also matter for teams managing several products or active test tracks. Plan build replacement and tester access around those limits rather than treating capacity as unlimited.

One Reddit thread reports that a full external-testing pool blocked new sign-ups until existing users selected Stop Testing and freed slots. The post describes that limit as a wall, so teams running public betas should plan for slot turnover. Before making TestFlight a release-critical dependency, verify Apple's current availability, security and compliance terms against your requirements. The developer homepage identifies support resources including Help Guides, Developer Forums and Contact Us, but does not state service-level guarantees.