What changed
Vercel announced on October 9, 2026 that Deployment Storage and Functions Storage charges of $0.10 per GB-month will apply to existing Pro teams, not just newly created Pro teams. Billing starts on the date Vercel communicates to each team by email; the announcement does not establish a universal billing start date. Separately, Vercel is reducing the default deployment retention window to 30 days. From October 23, deployments older than 30 days will be deleted unless the team opts out or changes its retention settings before then. New Pro teams already default to 30 days. This is distinct from the September Hobby-plan change that immediately deletes non-exempt deployments when a free team exceeds its 10GB limit.
Why it matters
Older deployments are often the fastest way to reproduce a production regression, investigate a release, or roll back to a known build. An automatic retention change can silently remove those options. At the same time, AI coding agents and CI pipelines are creating more builds and larger stored histories; two metered storage categories create a new ongoing cost for Pro teams. Teams need to make a deliberate choice between keeping rollback history and paying to store it, rather than discover the trade-off after October 23.
The October 23 deadline is about retention, not a universal invoice date
Vercel's October 9 changelog says deployments older than 30 days will be deleted starting October 23 unless a team opts out in its retention settings beforehand. Teams already configured for 30 days or less are unchanged. In contrast, Vercel says the billing start date for existing Pro teams is communicated by email, so it should not be assumed to be October 23. These are two separate operational clocks.
Deployment Storage and Functions Storage are two billable categories
Vercel lists $0.10 per GB-month for each category. Deployment Storage covers stored deployment outputs; Functions Storage is a separate meter for function bundles. The project Usage page shows both. A team with many builds, large static outputs or functions deployed to multiple regions should inspect its own usage rather than infer a likely monthly charge from another team's experience.
Longer retention remains configurable
New Pro teams default to 30 days, but Vercel says they can select longer periods in team settings. Existing Pro teams should review retention separately for Pre-Production, Production, Canceled and Errored deployments. Shortening the window reduces storage use; retaining more history can protect incident response and rollbacks but may cost more. Vercel warns that deleted deployments cannot be restored or used for rollback.
This is not the same rule as Hobby's September storage cap
BTN previously covered Vercel's September 16 change to free Hobby accounts: a shared 10GB allowance, fewer protected deployments, and immediate cleanup of non-exempt history when over the cap. The new Pro change is a paid-plan billing expansion and time-based retention default, with a specific October 23 action deadline. Builders comparing plans must not confuse the two failure modes.
A practical check before the deadline
Review the team's email for the applicable billing start date; check Deployment Storage and Functions Storage by project in Usage; identify old deployments needed for rollback, compliance or debugging; set a retention period explicitly before October 23; and reduce future build outputs, large static assets and function bundles where possible. If a release must remain reproducible indefinitely, preserve its artifacts independently of deployment retention.