Frequently asked questions

Most teams start on Team ($5/mo); it covers small internal betas and you only pay for the bytes you actually move. Choose Business ($50/mo plus metered usage) when you need SSO, longer retention, or standard support. Enterprise, which adds BYOSA and custom region pinning, 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 and testers install it over the air from the install link; the manifest is generated for you. 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. Connect App Store Connect and AppGantry can register collected UDIDs with Apple for you.

Yes. Upload a signed APK and testers install it from the same install link or the tester portal: Android downloads the file directly rather than using an over-the-air manifest, so the page walks the tester through allowing installs from your app once. Play App Bundles (.aab) are not accepted, because an .aab is a publishing format Android cannot install directly.

Bring-Your-Own-Storage Account. Available on Enterprise only, not Team or 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. Enterprise is not generally available yet, so BYOSA starts with a conversation rather than a subscription. 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 a hard spend cap, set for the whole organization or for a single project or channel. Once a cap is reached, new uploads and downloads are refused until you raise it or the billing period rolls over: your artifacts are kept, but they cannot be downloaded while the cap is binding. A channel cap is the exception and covers downloads only, because a build joins a channel when it is released, which is after the upload is metered. Budget alerts email your admins as settled spend approaches a cap (for an organization cap, the organization's admins; for a project or channel cap, the owning project's admins together with the organization's managers and admins), so you hear before it binds rather than after. Alerts are email only; there is no in-product notification. Set your organization, project and channel spend caps from the dashboard. 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, on every plan, with a CSV export from the dashboard. Business keeps it for longer: 365 days of audit retention by default against Team's 90.

Testers are invited by email and can be collected into named tester groups. A group can be granted access to the whole organization, to specific projects, or to specific channels, so a new tester joins one group instead of being wired up build by build. Testers sign in to their own portal to see and install everything they have been granted.

Yes. Every channel and release has an analytics page: download activity over time, plus a per-tester install table for a release showing whether each tester installed it, how many times they downloaded it, and when they last did. Available on every plan.

Yes. An organization can register outbound webhooks for build and release events. Each delivery is signed with an HMAC secret we show you once at creation, and the delivery log records attempts and retries so a receiver outage is visible and recoverable. Available on every plan.

App-based two-factor authentication (TOTP) with one-time recovery codes, and passkeys (WebAuthn) for phishing-resistant sign-in. You can review and revoke active sessions, and organizations on Business can require SSO/SAML through their own identity provider. All of it is self-service in account settings.

Partly, today. You can store App Store Connect, Google Play, and Microsoft Intune credentials against a project as a store connection, and the App Store Connect connection is used to register your testers' collected UDIDs with Apple so ad-hoc builds install on their devices. Submitting a build to a store is not working yet: the per-store adapters are still being built, so a submission is recorded and then fails rather than reaching the store. Keep using your existing release pipeline for store submission.

Not yet, and it is not generally available: there is nothing to buy and no quote to ask for. Custom region pinning, custom retention windows, and SLA-backed support are what an Enterprise tier would add. SSO/SAML is not part of that wait: it is a Business feature, and Business organizations can configure it now. Nor is the audit feed's CSV export, which every plan already has from the dashboard. See the pricing page for current Business availability. Register interest via the contact page and we'll let you know when Enterprise is available.

Yes. Every action available in the web app is also available via the REST API. For CI and other automation, use project access tokens: they are scoped to a single project with a capped role, and they belong to the project rather than to a person, so they keep working when a team member leaves and can be rotated or revoked without touching anyone's account. Personal access tokens are still available for individual, interactive use. Give a project access token the smallest role, and a personal access token the smallest scope, that gets the job done.

Our security overview lives at /security. Vulnerability reports go to security@appgantry.com.