Retention Policies

Retention Policies in JFrog help organizations manage storage and maintain system performance as the volume of binaries grows with faster development cycles. These policies allow you to clean up or archive stale artifacts to optimize storage and meet compliance requirements.

Cleanup

The JFrog Cleanup solution allows platform and project administrators to define customizable policies based on specific criteria for removing stale binaries from across their JFrog platform. This provides control over storage utilization and ensures optimal system performance. By setting specific criteria and rules, system administrators can customize a repeatable cleanup process that aligns with their organization's requirements. To get started with configuring and using Cleanup Policies, for more information, see Cleanup.

Archive

The JFrog Archive solution allows platform and project administrators to define customizable policies for archiving stale artifacts. By defining specific criteria, administrators can automate the movement of stale artifacts from an active Artifactory instance to an archive instance backed by low-cost storage. This helps maintain system performance, reduce storage costs, and meet regulatory compliance requirements. For more information, see Archive.

Cleanup vs Archive — Quick Comparison

CategoryCleanupArchive
PurposeDelete stale packages, builds and RB V2Move stale packages to long-term archive (ABHINAV WANTS TO CHANGE THIS)
Use CaseFree up space and improve operational efficiency
  • Free up space and improve operational efficiency in active instance after moving items to archive instance
  • Long-term retention and compliance
Restore and Access Data
  • ❌ Data is permanently lost if cleanup is done without using the Trash Can.
  • Trash Can configured: Not readily accessible, but available on restore
  • ✅ Data is available in Archive instance.
  • Not readily accessible, but available on restore
Automation✅ Policy-based cleanup✅ Policy-based archive
Designed for Compliance✅ Smart retention strategies that align with compliance requirements can be implemented✅ Archives packages along with metadata and evidence for compliance
Storage Optimization✅ Yes✅ Yes
Platform Support
  • Packages
    • Cloud: supported from 7.98.2
    • Self-hosted: supported from 7.98.7
  • Release Bundles V2
    • Cloud: supported from 7.104.2
    • Self-hosted: supported from 7.104.5
  • Builds
    • Cloud: supported from 7.125
    • Self-hosted: supported from 7.125
  • Smart Archiving
    • Cloud: supported from 7.111.1 for packages
    • Hybrid: supported from 7.117.14 for packages
    • Active Instance: Self-hosted
    • Archive Instance: Cloud
    • Self-hosted - Available soon
  • Legacy: Supported on self-hosted only
License RequiredEnterprise +
  • Smart Archiving: Enterprise+
  • Legacy: Enterprise X/+
Risk of Data Loss⚠️ Yes, if misconfigured and Trash Can not configured❌ No, data available in Archive instance and can be restored on-demand
Best ForActive DevOps environmentsRegulated industries, long-term retention