Vercel starts billing Pro teams for deployment storage and cuts retention to 30 days

Billing expands to existing Pro teams

Vercel is bringing Deployment Storage and Functions Storage billing to all existing Pro teams, with both metered at $0.10 per GB-month. In a changelog post, the company says teams should check their email for the exact date billing begins for them.

The more disruptive part is retention. Alongside the new charges, the default deployment retention window drops to 30 days. Deployments older than that will start being deleted on October 23, unless a team opts out in its retention settings before the date. Teams already set to 30 days or shorter will see no change.

New Pro teams get the same default

A second Vercel changelog post confirms that newly created Pro teams now default to 30-day deployment retention as well. Longer retention is still available in team settings for those who need more history for inspection or rollback — but under the new billing, keeping that history costs money.

The stated reason: agents are flooding deployment history

Vercel's motivation, according to its own posts, is the rise of coding agents. Automated agents have sped up development, driving up how often teams deploy and, with it, the volume of stored deployment history. Shorter retention keeps recent records on hand while trimming older ones and the bill that comes with them. The retention cut is effectively the mitigation for the billing change: less history stored means less to pay for.

What teams can do now

Vercel points to several levers for keeping costs down:

• Review the Deployment Retention Policy, which sets separate periods for Pre-Production, Production, Canceled and Errored deployments.
• Check the Usage page, which shows Deployment Storage and Functions Storage per project, to find where the bulk of the data sits.
• Shrink future deployments by removing unnecessary build files, moving large assets to Vercel Blob and trimming Function bundles.
• Decide before October 23 whether to opt out of the 30-day default, since that is the point of no return for older deployments.

Deleted deployments are gone for good

The key constraint is that deletion is permanent. Vercel notes that deleted deployments cannot be restored or rolled back to. Any team whose incident response depends on reverting to a build older than a month now has to choose between a longer, billable retention policy and a different recovery strategy. Opting out preserves history, but it leaves everything older than 30 days counting toward storage at the new rate.

Why it matters

This is the kind of platform change that quietly turns into either a surprise invoice or surprise data loss, depending on which deadline a team misses. After October 23, deployments older than 30 days begin disappearing unless someone has changed the retention settings, and there is no undo for what gets deleted. At the same time, storage that existing Pro teams were not previously billed for is now metered, which adds up quickly for teams with high deployment churn.

The change also signals a broader shift. As coding agents make deployments cheaper and faster to produce, the history they generate becomes a real cost line that teams have to budget and manage, rather than an incidental byproduct. Vercel is effectively pricing that reality in. Teams on Pro plans should treat October 23 as a hard deadline: audit retention settings, check per-project usage, and decide deliberately how much rollback history is worth paying for.