# Keep mobile builds beyond CI artifact retention

**Use AppBarn when an IPA, APK or AAB must remain available after your CI provider deletes its artifacts.** Your CI still compiles the app; AppBarn retains an uploaded copy and the associated build details.

## How it works

1. Finish your normal Xcode or Android build. Export an IPA, APK or AAB.
2. [Upload it in your browser](/quickstart) or use the [same CLI in CI](/ci/).
3. Select the target App and Environment. AppBarn stores the artifact with its build version, SHA-256 checksum and available source/CI provenance.
4. Find the Build later by its recorded version, environment or build history, then download it. [See build management](/cli/builds).

**Example:** A QA team needs the exact APK tested two months ago. Instead of recovering an expired CI run, it opens the retained Build, checks the version and checksum, and downloads that APK.

## Limits and trade-offs

- Stored Builds have no automatic age-only expiry while the Workspace remains active and within its plan limits. This is not a backup or indefinite-availability guarantee.
- The file size limit is 2 GiB per upload; Workspace storage and build limits can be lower. [Current limits](/reference/artifacts-limits).
- CI artifacts may be enough for short-lived debugging. AppBarn adds another storage and access system. [Compare options](/ai/compare).
- Keep separate backups of artifacts you cannot rebuild.

[Upload a build](/cli/upload) · [Build provenance](/reference/provenance) · [CI setup](/ci/) · [Pricing](https://app-barn.com/pricing)