Skip to content

Getting started

This page takes you from "I just signed up" to "my testers can install the build" in about ten minutes.

1. Create your account

Sign up at app.appgantry.com/signup. You'll receive a verification email; click the link to activate the account. The account is yours personally and travels with you between organizations.

2. Create an organization

Every build, tester, and project lives inside an organization. You'll be prompted to create one (or join an existing one if a teammate has already invited you).

  • Team ($5/mo, pre-paid) is the default and fits most small teams.
  • Business ($100/mo) unlocks SSO, longer default retention, and BYOSA. Pick this from the signup form if you already know you need it.
  • Enterprise is coming soon. Register interest.

You can upgrade later from your org settings.

3. Create a project

Inside the org, create a project for each app you distribute. The project name shows up in install links and tester invitations, so a clear name like "Acme iOS" is better than the bundle ID.

4. Upload your first build

In the project's Builds tab, click Upload build and pick your artifact:

  • iOS: a signed .ipa. We generate the install manifest for you. The build's UDIDs must be in your provisioning profile (or you can use an enterprise / in-house profile if you have one).

Android support is on the roadmap. Contact us if it's a blocker for you.

The upload streams direct to storage. Bigger builds take longer; you can close the tab and come back; we'll email you when it's done.

5. Invite testers

In the project's Testers tab, paste a list of tester emails and click Invite. Each tester gets an email with an install link. Existing testers can be added to new builds with one click.

The install page works on the tester's device with no AppGantry account required.

6. (Optional) Wire up CI

Most teams stop logging into the web app to upload builds after the first week. From CI, you'll:

  1. Create a project access token with the Read + Download + Upload role.
  2. Call POST /api/v1/organizations/{org_id}/projects/{project_id}/builds from your pipeline.

The full recipe is in CI with project access tokens.