Product Introduction
- Definition: BuildFerry is a cloud-based iOS beta distribution and ad-hoc provisioning platform that allows developers to distribute
.ipabuilds to testers via a single web link without requiring TestFlight, App Review, Xcode, or a dedicated local macOS environment. - Core Value Proposition: It eliminates the friction of iOS beta testing by automating device registration, UDID collection, and cloud-based re-signing using the developer's own Apple Developer account, serving as a streamlined TestFlight and Diawi alternative for over-the-air (OTA) installation.
Main Features
- Automated UDID Collection and Device Registration: Testers open a web link in Safari and allow a one-time configuration profile. BuildFerry automatically captures the device UDID and registers the iPhone with the developer's Apple Developer account, removing manual device identifier management.
- Cloud-Based Code Signing: BuildFerry takes an exported
.ipabinary and re-signs it in the cloud for newly approved iPhones. The platform handles certificates and provisioning profiles using encrypted API keys without requiring a local Mac, cable connection, or manual Xcode builds. - CI/CD Pipeline Integration: The platform integrates natively into automated deployment workflows through a GitHub Actions workflow action (
iamsrikanth-dev/buildferry-upload), a fastlane plugin, or an NPX command (npx buildferry upload), ensuring every build from a continuous integration pipeline automatically updates the distribution link. - Access Control and Security: Share links feature granular administrative controls including PIN protection, link expiration dates, manual approval workflows, and auto-approve settings. Apple keys are encrypted at rest and loaded into temporary signing containers exclusively during active build jobs.
Problems Solved
- Pain Point: iOS ad-hoc distribution traditionally requires manual UDID collection via spreadsheets, updating provisioning profiles in Apple Developer portals, local Xcode rebuilding, and dealing with Apple's 100-device annual hardware limit. Furthermore, TestFlight introduces review delays and forces testers to install a secondary app.
- Target Audience: iOS Developers, Indie Hackers, QA Engineers, Product Managers, and CI/CD DevOps Engineers who need fast, continuous ad-hoc distribution outside of the App Store review cycle.
- Use Cases: Rapidly distributing early-stage staging builds to QA testers and stakeholders without waiting for Beta App Review; onboarding new client test devices instantly without collecting manual device identifiers; and automating daily or pull-request builds directly from GitHub Actions or fastlane.
Unique Advantages
- Strengths & Limitations (Pros & Cons):
- Pros: Eliminates local macOS requirements for signing; bypasses TestFlight review times; keeps persistent distribution links updated automatically via CI/CD; works natively with a developer's existing paid Apple Developer account.
- Cons: Limited strictly to iOS ad-hoc distribution (no Android support); requires a paid Apple Developer membership; bound by Apple's strict hardware limit of 100 registered iPhones per membership year.
- Key Alternatives & Differentiation:
- TestFlight: Unlike TestFlight, BuildFerry requires no App Review, does not force testers to download a separate client app, and installs directly via Safari links, though it remains subject to Apple's 100 ad-hoc device limit.
- Diawi / BetaDrop: While tools like Diawi simply host static pre-signed files—requiring manual UDID collection and profile rebuilding for every new tester—BuildFerry dynamically registers new devices and re-signs builds in the cloud using a single persistent link.
- Firebase App Distribution (iOS): Firebase collects UDIDs but leaves developers to manually add them to Apple Developer accounts and trigger new builds; BuildFerry automates the entire provisioning and signing lifecycle end-to-end.
Frequently Asked Questions (FAQ)
- How does BuildFerry bypass Apple's TestFlight app review?
BuildFerry utilizes ad-hoc distribution rather than App Store Connect submission. It registers the tester's iPhone UDID directly to your Apple Developer account and re-signs the
.ipafile in the cloud, allowing direct over-the-air installation through Safari without review delays. - Do testers need to install a companion app or create an account? No. Testers simply open your unique BuildFerry link in Safari on their iPhone, install a temporary verification profile to share their device identifier, and tap the install button once the build is approved and signed.
- Do I need a Mac or Xcode to use BuildFerry?
No local Mac or Xcode installation is required to sign or distribute builds. You only need a paid Apple Developer membership, an exported
.ipafile (which can be generated via cloud CI/CD runners like GitHub Actions), and a connection to your App Store Connect API key. - How does BuildFerry handle Apple's 100-device limit? BuildFerry tracks your active device count against Apple's limit of 100 registered iPhones per family membership year, displaying real-time usage metrics within your dashboard before you approve new tester devices.
