AI Signal 88
Hobby projects now retain fewer deployments to free up storage
↗
Vercel has reduced the deployment retention for Hobby projects to three recent production and three recent total deployments, removing separate protection for preview deployments.
This change forces Hobby users to actively manage storage or upgrade to Pro, as exceeding the 10GB limit now triggers immediate deletion of non-protected deployments rather than a 30-day grace period. It shifts the burden of storage optimization from the platform to the individual developer.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Hobby projects now retain only the three most recent production deployments and three most recent deployments of any type.
Preview deployments no longer receive specific retention protection, making them subject to immediate deletion if storage limits are exceeded.
Teams over the 10GB storage limit face immediate deletion of unprotected deployments instead of a 30-day retention window.
THE READ
What the cluster adds up to.
Vercel has tightened its storage constraints for Hobby tier users by reducing the number of retained deployments. Previously, deployments were kept for 30 days, but now only the three most recent production deployments and three most recent deployments of any type are protected from deletion. This change directly impacts how developers manage their project history and rollback capabilities on the free or low-cost tier.
The most significant operational shift is the removal of specific protection for preview deployments. While current production, aliased, and active-branch deployments remain safe, preview environments are now treated as standard deployments. If a Hobby team exceeds the 10GB storage limit, these unprotected preview deployments are deleted immediately rather than after a 30-day period, which can disrupt testing workflows that rely on historical preview links.
For teams already over the 10GB limit, the consequence is immediate storage reclamation. Deployments outside the protected exceptions are removed instantly to bring the account back under the cap. This creates a hard stop for deployment frequency if storage is not optimized, potentially blocking new releases until old artifacts are manually cleared or the account is upgraded.
The economic trade-off is clear: Hobby users must either optimize their deployment storage usage or pay $0.10 per GB per month on the Pro plan. This pricing structure makes the Hobby tier less suitable for teams with high deployment frequency or large build artifacts, pushing them toward paid plans to maintain a longer deployment history and avoid the risk of immediate data loss.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER