QA teams
Keep recurring builds in one App history and give each QA audience an explicit Release link.
iOS and Android app distribution
Upload a signed iOS IPA or Android APK, review package details, keep Release history, and create tester links with the access rules you need. DistKit does not sign or re-sign packages.
Inspect a package, keep its version history, and share the right build with each audience. Explore the checks and controls on the Product page.
Read app metadata and embedded provisioning details before a tester opens the Release.
02Keep builds grouped by App, with blocked reasons and replacement history visible.
03Set a password, expiry, delivery-handoff limit, and enabled state per audience.
04Use iOS OTA manifests or direct signed APK downloads from the same Release model.
Use your existing signing process. Manage the build handoff in DistKit.
Keep recurring builds in one App history and give each QA audience an explicit Release link.
Inspect provisioning details before sharing a build with collaborators or a small tester set.
Separate client-review links by password, expiry, request limit, and current Release.
DistKit analyzes the package you provide and controls its delivery path. Apple certificates and profiles remain in Apple Developer; Android signing keys and export settings remain in your build pipeline.
Review the iOS distribution steps, storage and access controls, or plan limits before you start.
Create a workspace, upload a signed IPA or APK, and review its package report before sharing.