What is Build Retention in Applivery?

Build Retention defines how long uploaded Builds are stored in Applivery before automatic archiving and permanent deletion.

How long are Builds kept before deletion?

Builds are retained based on your subscription plan and retention settings, with a 30-day grace period before permanent deletion.

How can I get unlimited Build Retention?

Unlimited retention is available for Enterprise plans and must be explicitly enabled upon request.

Where can I configure Build Retention settings?

You can configure Build Retention at the Workspace level or at the individual App level.

What happens when a Build reaches its retention limit?

The Build moves to a Pending deletion stage for 30 days before being permanently deleted.

How do I set a custom retention policy for a specific app?

In the App's Settings, under the Advanced section, you can define a custom retention period and number of Builds to retain.

Where do I find the Build retention policy settings in the Applivery Dashboard?

Navigate to Workspace Settings > Storage > Build retention policy to configure workspace-level settings.

Applivery Build Retention: Control Your App Storage

Q: Does Applivery automatically retain recent Builds?

Yes, Applivery automatically preserves a minimum number of recent Builds per Publication, even with retention limits.

Warning

This feature may vary depending on your current plan. 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 Settings (1), select Storage (2) from the left-hand menu and scroll down to locate the Build retention policy (3) 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).

Note

By default, all Apps within the workspace inherit these settings.

Warning

In Enterprise plans, you can enable Unlimited retention if it has been previously activated after contacting our team. For other plans, you can adjust the values within the limits of your subscription.

App level

Once in the Applivery Dashboard, select the App you want to configure, then go to the Settings tab and open the Advanced section.

Locate the Build retention policy 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.

Key Takeaways

Build retention allows you to manage storage by automatically deleting older builds.

You can configure retention policies at both the workspace and app levels.

Applivery automatically preserves a minimum number of recent builds per publication.

Enterprise plans may have access to unlimited retention.