Vercel Starts Charging Pro Teams for Deployment Storage

Vercel will charge all Pro teams $0.10 per GB-month for deployment storage, and delete deployments older than 30 days from October 23.

What changes

• Billing for Deployment Storage and Functions Storage begins for all Pro teams, each at $0.10 per GB-month. Vercel says to check your email for the date billing starts for your team.
• The deployment retention window moves to 30 days, which Vercel frames as a way to keep storage costs low.
• Deployments older than 30 days will be deleted starting October 23, unless you opt out in your retention settings before then.
• Teams whose retention is already 30 days or shorter are unchanged.
• New Pro teams now default to a 30-day deployment retention period.

Who has to act, and by when

Your team	What happens	Deadline
Existing Pro, retention longer than 30 days	Older deployments deleted unless you opt out in retention settings	Before October 23
Existing Pro, retention already 30 days or shorter	Retention unchanged; storage billing still applies	Billing date arrives by email
New Pro team	Starts at the 30-day default; a longer period is a settings change	None

Why Vercel points at coding agents

The retention change is not framed as a pricing grab. Vercel's reasoning is that coding agents have accelerated development, increasing deployment frequency and the amount of stored deployment history, and that shorter retention keeps recent history available while limiting older history and its storage costs.

That is a plausible read of how agent-driven teams actually ship: more deploys per day means more preview builds parked in storage, each one now metered. The practical effect is that the teams leaning hardest on agents are the ones whose storage line will move first.

The tradeoff nobody should skip

Deleted deployments cannot be used for rollback. That single line is the reason to decide retention deliberately rather than letting the default land. If your incident process assumes you can roll back to a build from six weeks ago, a 30-day window quietly removes that option on October 23.

Vercel points to the Deployment Retention Policy, where retention is set separately for Pre-Production, Production, Canceled, and Errored deployments. Shorter periods reduce stored history. Those four buckets are not equally valuable — as analysis, not as Vercel guidance: Canceled and Errored history is the cheapest to shorten, Production history is the one your rollback plan depends on.

What to do before October 23

Open the Usage page, where Deployment Storage and Functions Storage are shown per project, and find out how many GB you are actually storing before guessing what $0.10 per GB-month costs you. Then set retention per bucket rather than globally: keep Production long enough to cover your real rollback horizon, and trim Pre-Production, Canceled, and Errored. If you need more history for inspection or rollback, a longer retention period is available in your team's settings — you will simply pay storage for it.