Vercel Updates Default Deployment Retention Policy to 30 Days for New Pro Teams
Vercel now sets a default 30-day retention policy for deployments on newly created Pro teams to optimize storage usage and costs. Retention beyond 30 days incurs storage charges, and deleted assets cannot be restored.
Vercel has changed the default deployment retention period for newly created Pro teams from unlimited to 30 days. This adjustment aims to curb escalating storage costs resulting from the surge in deployment frequency driven by automated coding agents. Deployments older than 30 days will be systematically purged according to policy, rendering them permanently unrecoverable for rollbacks or asset retrieval.
Primary source
Open Vercel Changelog ↗This article summarizes the source. Check the original for full details and conditions.
Comparison
| Aspect | Before / Alternative | After / This |
|---|---|---|
| Default Retention Period | Unlimited deployment retention | 30 days default retention |
| Storage Billing | No explicit charge for historical storage | $0.10 per GB per month for retention past 30 days |
| Scope of Application | All legacy and active team settings | Applies strictly to newly created Pro teams |
| Expired Deployment Data | Retained indefinitely for rollbacks | Permanently deleted and unrecoverable |
Action Checklist
- Review current deployment retention policies in team settings Verify whether existing or newly created Pro teams require historical deployment data beyond 30 days.
- Evaluate storage usage against cost trade-offs Retention extending past 30 days incurs a charge of $0.10 per GB per month.
- Adjust retention configuration if extended rollbacks are necessary Ensure critical staging or production releases are backed up independently if retention policies delete older builds.
