Frequently asked questions
Don't see your question? Email us and we'll add it here.
Most teams start on Team ($5/mo); it covers small internal betas and you only pay for the bytes you actually move. Upgrade to Business once your monthly metered usage approaches the $100 platform fee or you want SSO, longer retention, or BYOSA. Enterprise is coming soon.
No. You can add unlimited team members, reviewers, and CI bots on any plan. We bill for distribution (bytes moved and stored), not for headcount.
Yes. Upload a signed IPA + manifest; testers install via the device's standard ad-hoc install flow. No TestFlight queue. Apple provisioning rules still apply: testers' UDIDs must be in the provisioning profile, or you must use an enterprise (in-house) profile.
Not yet. v1 supports iOS only. Let us know via the contact page if Android is a blocker for you.
Bring-Your-Own-Storage Account. Available on Business. You point us at your own Azure storage account and we upload/download artifacts directly from your tenant. The three usage meters are disabled and your AppGantry invoice becomes the flat platform fee only. See the BYOSA page for the full pitch.
30 days by default on Team, 12 months on Business. Retention is configurable per organization in every plan. Storage is metered per MB-month, so longer windows are simply paid for.
Yes. Every hosted plan supports budget alerts (notify-on-approach) and a hard spend cap that blocks new uploads and downloads once the cap is reached. Existing artifacts stay readable. BYOSA orgs are exempt from cap enforcement entirely (your cloud provider handles the spend ceiling).
Yes. Every org gets an audit feed covering authentication, build uploads, tester invites, and configuration changes. Business adds richer event coverage.
Coming soon. SSO/SAML, custom region pinning, audit-feed export, and SLA-backed support will land in the Enterprise tier. Register interest via the contact page and we'll let you know when it's available.
Yes. Every action available in the web app is also available via the REST API. CI integrations should use personal access tokens (PATs) with the smallest scope that gets the job done.
Our security overview lives at /security. Vulnerability reports go to security@appgantry.com.