Vercel has altered its free Hobby plan retention: deployments that exceed the 10 GB storage cap are now removed immediately unless they fall under specific protection rules. Practitioners who rely on Vercel for rapid iteration need to understand how the tighter limits affect rollback windows, CI/CD storage budgeting, and incident recovery.
Vercel deployment storage limits tighten on free Hobby tier
The updated policy removes the previous 30‑day grace period for projects that go over the 10 GB limit. When the limit is breached, any deployment that is not covered by an exception is deleted at once. The only deployments that survive are:
- The three most recent production deployments for each project.
- The three most recent deployments of any type, regardless of age.
- The current production deployment, any aliased deployment, and the latest preview on an active Git branch.
Earlier, Hobby projects kept the ten most recent production deployments and enjoyed a separate count‑based exception for preview builds. Those broader protections have been removed for all Hobby projects, not just those exceeding the storage quota.
Why the change matters to engineers
Vercel reports handling more than 10 million deployments per day, a six‑fold year‑over‑year increase. The surge in deployment frequency means dormant builds can silently consume the limited storage allocated to free accounts, eventually blocking new deployments. For AI engineers, cloud platform teams, and SREs, the immediate deletion of unprotected builds reduces the risk of hitting a hard storage ceiling during a release cycle, but it also shortens the historical artifact pool useful for debugging or rolling back to a known good state.
From a CI/CD perspective, the loss of older preview artifacts means that automated tests that reference previous preview URLs may fail if those previews are pruned. Security engineers should note that the 30‑day recovery window still applies, but only after a deployment has been successfully built; the window does not protect against the immediate removal of unprotected builds.
Operational steps to stay within the free tier
Practitioners can mitigate disruption by adopting a few low‑effort practices:
- Monitor the
Deployment Storagemetric and set alerts before the 10 GB threshold is reached. - Leverage the built‑in 30‑day recovery area under Settings → Security → Recently Deleted to restore mistakenly removed builds.
- Trim unnecessary output from build steps (e.g., large source maps, unused assets) to keep each deployment footprint small.
- Consider upgrading to the Pro plan if the project consistently exceeds the free limit; Pro adds $0.10 per GB‑month and retains more generous retention exceptions (last 10 deployments, last 20 production and non‑production deployments).
These actions align with Vercel’s stated goal of keeping the Hobby tier sustainable while still supporting active developers.
Related CloudNinjas coverage: DevOps.
What This Means For Practitioners
In practice, teams on the free tier should treat the 10 GB cap as a hard limit and plan their deployment cadence accordingly. Verify that critical rollback points are among the three most recent production builds, and incorporate storage‑size checks into your CI pipeline. If your workflow depends on a longer history of preview builds, evaluate the cost‑benefit of moving to a paid tier or archiving needed artifacts elsewhere. By proactively managing storage and understanding the new retention rules, you can avoid unexpected deployment failures and maintain a reliable development loop on Vercel’s free offering.