Check the availability on our pricing page.
Build Retention allows you to define how long uploaded builds are stored in Applivery before they are automatically archived and permanently deleted.
Previously, uploaded builds were kept indefinitely. With this new system, builds are now retained based on your subscription plan and retention settings.
- Unlimited retention is only available for Enterprise plans and must be explicitly enabled upon request.
- Once a build reaches the end of its retention period, it moves to the Pending deletion stage, where it remains for a 30-day grace period before permanent deletion.
Automatic Retention Rules #
Even with retention limits in place, Applivery automatically preserves a minimum number of recent builds per publication.
This ensures that you always have access to the most recent builds for every app publication within your workspace.
When the retention limit is reached, the oldest builds are deleted first while newer ones are retained.
Configuring Build Retention #
You can configure build retention at two levels:
- Workspace level.
- App level.
Workspace level #
Once in the Applivery Dashboard, navigate to your Workspace (1) > Settings (2) > Storage (3). Scroll down to locate the Build retention policy (4) configuration.
Here you can:
- Specify the retention period (the number of days a build is kept before being deleted).
-
Set the number of recent builds to retain per publication (these are preserved even beyond the retention period).
App level #
Once in the Applivery Dashboard, navigate to App Distribution (5), select the App you want to configure, then go to the Settings (6) tab and open the Advanced (7) section.
Locate the Build retention policy (8) configuration.
At this level, you can:
- Inherit Workspace settings, or
Define a custom retention policy for that specific app — including unlimited retention (if available in your plan) or a custom retention period and number of builds to retain per publication.