AppGantry documentation¶
Welcome. These docs are for developers using AppGantry to distribute iOS and Android builds to their teams and testers.
Start here¶
- Getting started: create an organization, upload your first build, invite testers.
- Invite your testers: get a build onto someone else's device.
- First-build troubleshooting: when the install doesn't work.
Popular destinations¶
| I want to… | Read |
|---|---|
| Understand what my plan covers | Plans & pricing |
| Ship builds from CI | CI with project access tokens |
| Manage who gets which build | Channels & releases |
| Add and organize testers | Managing testers & groups |
| Find a screen or web app feature | Web app feature guide |
| Fix "unable to install" on iOS | Enrolling test devices |
| React to events in my own systems | Webhooks |
| Sign in through my own identity provider | Single sign-on (SAML) |
| Deal with someone leaving the team | Offboarding a member |
| Know whether I can publish to the App Store | Feature availability |
| Keep artifacts in my own Azure storage | BYOSA |
| Control spend | Billing, usage & caps |
| Secure my account | MFA, passkeys & sessions |
| Call the REST API | API conventions |
| Find the right API resource | API surface map |
| Add in-app updates to my iOS app | In-app updates SDK |
| Just get a quick answer | FAQ |
How these docs are organized¶
We follow the Diátaxis shape: each page answers one kind of question.
| Section | When to read it |
|---|---|
| Getting started | First time using AppGantry. Follow it top to bottom. |
| Concepts | "What is this and why does it exist?" |
| Guides | "How do I do X?" Step-by-step recipes for real tasks. |
| SDK | Integrating in-app updates into your app. |
| Reference | "What are the exact rules?" Conventions, errors, events, glossary. |
| API | The interactive OpenAPI reference, generated from the service. |
| About | Security reporting and what's available where. |
| FAQ | "Quick answer please." |
If a page tries to do more than one of those, it's the wrong shape. Open an issue and we'll split it.
Two surfaces, one product¶
Almost everything can be done either way:
- The web app is where humans work: uploading, releasing, inviting, reviewing. The guides are written around it.
- The REST API is where automation works: CI uploads, release promotion, tester management. Start with API conventions and the interactive reference.
A few operations are currently available through only one of them. Feature availability says which.
Found a mistake?¶
Use the pencil icon in the header of any page to edit it on GitHub, or email us. Docs accuracy bugs are treated as service bugs.
Security issues go to security@appgantry.com instead — see Security & disclosure.