Skip to content

Build Independently confirmed2 publishers 2 min read Published

Vercel cuts Hobby rollback depth from ten production deployments to three

Vercel's free Hobby plan now protects three production builds plus three deployments of any type, with anything else deleted the same day once a team passes the 10GB storage quota. Its head of pricing says few users will notice.

The Engineer · Build desk

Send a correction

Illustration accompanying Vercel cuts Hobby rollback depth from ten production deployments to three
Generated illustration

What happened

  • Vercel's updated Deployment Retention Policy deletes older unprotected deployments immediately once a free-tier Hobby team exceeds its 10GB Deployment Storage allowance, ending the previous 30-day holding window.
  • Every Hobby project, over the limit or not, now keeps only its three most recent production deployments plus its three most recent deployments of any type, down from ten production deployments.
  • Hobby also loses the count-based preview protection that keeps the last 20 non-production Ready deployments on Pro and Enterprise, though the latest preview on an active Git branch stays protected on every plan.
  • Deletion is not instantly permanent: successfully built deployments stay recoverable for 30 days from a project's Settings, under Security, Recently Deleted.
  • Jas Garcha, Vercel's head of pricing, told The New Stack the platform now handles more than 10 million deployments a day, more than six times its volume a year ago.

Why it matters

  • What it limits constraint Rollback depth on Hobby is three production builds, so undoing a fourth-from-last release means rebuilding from Git instead of promoting a build that already exists.
  • What it costs cost Keeping the old retention behavior now costs money. The route is the Pro plan, where storage past the included allowance is metered by the gigabyte-month.
  • Who has to decide decision Anyone who kept old preview URLs alive on Hobby has to pick which ones to alias or park on an active branch, because those are the only protections left beyond the six newest builds.
  • What doesn't add up contradiction Garcha says few Hobby users will feel the effects, yet the shortened exception list applies to every Hobby project, including the ones nowhere near 10GB.

Next story · Build · 23h ago

Vercel sells Pro teams $80 of GLM 5.3 and Kimi K3 credit for $30 a month

Confirmed2 publishers

Deployment Storage on Hobby is a 10GB quota. Every build a project keeps uses part of it. "Every deployment you keep uses some of it, and going over the limit can block you from deploying until you free some up," Vercel wrote in its changelog [8]. Retention is how the space comes back. A deployment that is not on the exception list is eligible to go.

"Your current production deployment is never deleted, and aliased and active-branch deployments remain protected, along with each project's most recent deployments," Jas Garcha, Vercel's head of pricing, told The New Stack [7][17]. For a project already over the quota, the deletions now arrive sooner. So does the space. Under the old defaults that storage stayed locked up for as long as 30 days while the project sat blocked [2][8][9].

The paid tier keeps a longer list: the last 10 deployments created in a project, the last 20 production deployments in a Ready state, and the last 20 non-production ones [13]. Set against Hobby's three and three, that is seven more production builds and a full 20-deep window for previews [18][6]. Storage past Pro's included allowance bills at $0.10 per GB per month, so carrying 10GB of overage costs $1 a month and $12 a year [10][20].

Garcha said: "Our former retention defaults were designed for teams that ship constantly and need deep rollback history. They made less sense for Hobby projects, where dormant deployments were quietly consuming storage that active projects need." [15] He put current volume at more than 10 million deployments a day, more than a 6x increase year over year [16]. Divide the two and the platform was handling roughly 1.7 million deployments a day a year ago [19].

That figure counts deployments across the platform, not Hobby storage, and Vercel did not publish how many Hobby teams sit over the 10GB line. Garcha said few Hobby users will feel the effects [21]. For the change to be as quiet as that, most Hobby projects would have to hold no more than six deployments anyone still wants, or their older builds would have to be ones nobody will ask for again. Vercel's advice for staying under the limit includes reducing unnecessary deployment output [11].

What to watch

  • Whether Vercel publishes the share of Hobby projects sitting over 10GB.
  • Whether restoring a build from Recently Deleted counts against the 10GB quota while a team is still over it.
  • Whether the three-and-three exception list migrates upward into Pro defaults in a later changelog.

Clarity's read

What the record supports and how the coverage leans. The claims behind it follow.

Reality

Evidence70
Adoption58
Hype gap−10
Incentives72
Confidence70
Why these scores

Claim ledger

Ranked by verification strength, evidence, and original report placement.

  1. [1]

    Vercel announced this week that teams on its free Hobby plan will now have older, unprotected deployments deleted immediately if they exceed the 10GB Deployment Storage limit.

    Reported SupportedView cited source
  2. [2]

    Before the change, users on the free tier could count on eligible deployments to stick around for up to 30 days.

    Reported SupportedView cited source
  3. [3]

    Each Hobby project now keeps its 3 most recent production deployments, plus its 3 most recent deployments of any type, regardless of age.

    Reported SupportedView cited source
  4. [4]

    The previous Hobby exception preserved the 10 most recent production deployments, and the new rule applies to every Hobby project, not only teams over the 10GB limit.

    Reported SupportedView cited source
  5. [5]

    Hobby lost the count-based preview exception; the latest preview deployment on an active Git branch is still protected on every plan.

    Reported SupportedView cited source
  6. [6]

    Pro and Enterprise teams keep their last 20 non-production deployments in a Ready state, and that protection no longer applies to Hobby.

    Reported SupportedView cited source
  7. [7]

    "Your current production deployment is never deleted, and aliased and active-branch deployments remain protected, along with each project's most recent deployments."

    Reported Supported Source: Jas Garcha, head of pricing at Vercel, to The New StackView cited source
  8. [8]

    "Every deployment you keep uses some of it, and going over the limit can block you from deploying until you free some up."

    Reported Supported Source: Vercel changelogView cited source
  9. [9]

    If a team is over the 10GB limit, deployments outside the exceptions are now deleted immediately instead of after 30 days.

    Reported SupportedView cited source
  10. [10]

    On the Pro plan, storage beyond the included allowance is billed at $0.10 per GB per month.

    Reported SupportedView cited source
  11. [11]

    Vercel offers guidance for optimizing Deployment Storage usage to help users stay under the free 10GB limit, such as reducing unnecessary deployment output.

    Reported SupportedView cited source
  12. [12]

    Vercel gives successfully built deployments a 30-day recovery period, and users can restore them from a project's Settings under Security, Recently Deleted.

    Reported SupportedView cited source
  13. [13]

    Pro retention exceptions are the last 10 deployments created in a project, the last 20 production deployments in a Ready state, and the last 20 non-production ones.

    Reported SupportedView cited source
  14. [14]

    "This change allows us to continue supporting a Hobby community that's deploying at a much higher rate than it was a year ago."

    Reported Supported Source: Jas Garcha, head of pricing at Vercel, to The New StackView cited source
  15. [15]

    "Our former retention defaults were designed for teams that ship constantly and need deep rollback history. They made less sense for Hobby projects, where dormant deployments were quietly consuming storage that active projects need."

    Reported Supported Source: Jas Garcha, head of pricing at Vercel, to The New StackView cited source
  16. [16]

    According to Garcha, Vercel now handles more than 10 million deployments every day, more than a 6x increase year over year.

    Reported SupportedView cited source
  17. [17]

    Jas Garcha is head of pricing at Vercel.

    Reported SupportedView cited source
  18. [18]

    The Hobby production exception fell by seven deployments, from the 10 most recent production deployments to the 3 most recent.

    Derived Supported
  19. [19]

    At more than 10 million deployments a day and more than a 6x year-over-year increase, Vercel was handling roughly 1.7 million deployments a day a year earlier.

    Derived Supported
  20. [20]

    At $0.10 per GB per month, 10GB of storage above Pro's included allowance costs $1 a month and $12 a year.

    Derived Supported
  21. [21]

    Garcha says few Hobby users will feel the effects of the change.

    Reported InsufficientView cited source

Sources

2 independent publishers whose own reporting we read for this story.

  1. blog.vercel.com

    1 article · September 16, 2026

    Hobby projects now retain fewer deployments to free up storage
  2. thenewstack.io

    1 article · September 19, 2026

    “Dormant deployments were quietly consuming storage”: Why Vercel tightened its free-tier rules

Topics and entities

Topics

  • Free-tier economics
  • Platform pricing
  • Deployment retention

Entities