# New Pro teams now default to 30-day deployment retention By Steven Van · 2026-10-09 Teams can extend retention for reviews and rollback, but deleted deployments cannot be restored. Teams that need more than a month of deployment history can choose a longer retention period in [Vercel](). New Pro teams now start with a 30-day default, limiting older stored history as coding agents increase deployment frequency. ## Set retention for teams or projects Under Team Settings, open Security & Privacy, then Deployment Retention Policy. Set the periods for Canceled, Errored, Pre-Production, and Production deployments, then save. The team default applies to new projects. Selecting “Apply this policy to all existing projects” also replaces every existing project's retention policy. For a single project, open Settings, then Security, and change its Deployment Retention Policy. This leaves the team default and other projects' policies unchanged. ## Keep enough history for recovery Production retention should cover incident recovery, rollback, and release audits. Pre-Production retention should allow time for reviews, quality assurance, approvals, and regression investigation. Older deployments may be deleted under the policy. Deleted deployments cannot be restored or used for rollback. Deployment Storage and Functions Storage each cost **$0.10 per GB-month**. To check retention's effect, compare both metrics in the team's Usage page using the same projects and 30-day date range after Usage refreshes. Vercel's [storage optimization guide]() explains the retention settings and usage checks. ![Vercel]() Vercel The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config. [View Vercel →]() [Original source]() [Read New Pro teams now default to 30-day deployment retention on Creators Toolbox]() --- Canonical source: https://creatorstoolbox.com/blog/vercel-new-pro-teams-now-default-to-30-day-deployment-retention