The tools the Factory ships with

For: you have an app and something is wrong with it, or you are about to submit and want to know what Apple will flag first.

Point it at your App Store Connect account and it reports what is actually true, rather than what the web interface implies. It catches the failure that cost me eighteen days: a version reading WAITING_FOR_REVIEW while no live submission holds it.

It only ever issues GET requests. It cannot change a listing, cancel a submission or touch a price, which is what makes it safe to hand to an agent.

Source on GitHub

For: you already have a project, and you release it over and over.

The fastlane lanes behind every release I ship. Signing that survives a certificate wipe, TestFlight distribution, submission with in-app purchases attached the way Apple actually requires, and the analytics report requests you have to create before launch.

Each lane exists because the manual version of it failed at least once on a real release.

Source on GitHub

For: you have never shipped an app, and you want a build on TestFlight this week.

You start with an empty folder and a description of the app you want. It scaffolds the project, wires the release pipeline in from the start, sets up signing, and gives Claude Code the skills to walk you through every step to the App Store. Your first TestFlight build takes about an evening.

The run above is real: 23 files, a generated project, and a green test suite before a line of your code exists.

You will need an AI coding agent alongside it: Claude Code, Cursor, or any tool that reads an AGENTS.md. Everything else on this page ships inside it.