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
| Category | Cleanup | Archive |
|---|---|---|
| Purpose | Delete stale packages, builds and RB V2 | Move stale packages to long-term archive (ABHINAV WANTS TO CHANGE THIS) |
| Use Case | Free up space and improve operational efficiency |
|
| Restore and Access Data |
|
|
| 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 |
|
|
| License Required | Enterprise + |
|
| 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 For | Active DevOps environments | Regulated industries, long-term retention |
Updated 2 days ago
