Vercel has tightened its free-tier rules because dormant deployments were consuming storage. The change connects two parts of the service that can seem separate at first: deployments that are no longer active and the storage those deployments continue to use.
The central issue is simple. A deployment can be dormant while still taking up space, and that space remains part of Vercel’s storage use. When dormant deployments accumulate, they consume resources even though they are not active.
That is why Vercel changed the rules around its free tier. The decision focuses on storage consumption caused by deployments that are no longer active, rather than on active deployments alone.
The storage problem behind the rule change
Free-tier services place limits around the resources they provide without charge. In this case, Vercel’s rules now account for storage used by dormant deployments. The reason given for the change is that those deployments were consuming storage.
The word “dormant” matters here. These deployments are not described as active, but they still occupy storage. That creates a gap between what is being used in practice and what the storage system must continue to hold.
Vercel’s rule change addresses that gap by tightening its free-tier rules. The company is responding to storage use that remains tied to deployments after those deployments become dormant.
This makes the change less about a new kind of deployment and more about how long deployments continue to occupy storage. The deployment status and the storage use are connected, even when a deployment is no longer active.
What the change means
The clear takeaway is that dormant deployments now matter under Vercel’s free-tier rules. A deployment does not stop affecting storage simply because it is dormant, so storage use remains part of the reason for the tighter limits.
Vercel’s decision also shows why storage can become the focus of a free-tier policy. A service may need to account for deployments that remain stored even when they are not active. In this case, dormant deployments were the specific source of that storage consumption.
There are no additional figures, dates, or quoted statements attached to the change. The verified explanation is limited to one point: Vercel tightened its free-tier rules because dormant deployments were consuming storage.
That makes the policy change easy to summarize, even if the underlying resource issue is easy to miss. Dormant does not mean absent. The deployments still consume storage, and Vercel changed its free-tier rules to address that use.
For anyone looking at the change, the key distinction is between activity and storage. A deployment can be dormant in terms of activity while continuing to occupy storage. Vercel’s updated approach treats that storage use as the reason the free-tier rules needed to become tighter.
The result is a clearer connection between dormant deployments and the limits of the free tier. Vercel’s explanation centers on the storage those deployments consume, and that remains the main fact behind the policy change.
