Urgent.News

What's breaking now, across thousands of outlets.

Tech

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

Vercel announced this week that teams on its free Hobby plan will now have older, unprotected deployments deleted immediately if The post “Dormant deployments were quietly consuming storage”: Why Vercel tightened its free-tier rules appeared first on The New Stack .

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

Vercel recently announced changes to its free Hobby plan that will automatically delete old, unprotected deployments if they exceed the 10GB Deployment Storage limit. According to Jas Garcha, Vercel's head of pricing, this change aims to keep the free tier viable as deployment volumes have grown significantly. Previously, teams on the free tier could keep eligible deployments for up to 30 days, but that window has been eliminated for teams exceeding the 10GB limit.

Now, if users go over the standard 10GB limit, old deployments not covered by Vercel's exceptions will be deleted immediately. Hobby projects will still retain the three most recent production deployments and three most recent deployments of any type, regardless of age. Preview deployments will also lose their separate protection.

Vercel's policy update aims to free up storage for active projects as deployment rates have increased sixfold year-over-year. The deleted deployments remain in a 30-day recovery period, and users can restore them from their project settings. Users can choose to move to the Pro tier, where storage beyond the plan's allowance is billed at $0.10 per GB-month, or optimize their Deployment Storage usage to stay within the free 10GB limit.

Written by urgent.news from The New Stack's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at thenewstack.io →

More in Tech

Workers Should Not Inherit Your Logging Handlers

Have you ever watched pool.join() sit there after a logging cleanup that looked boring in review? The workers are not crunching data.

  • Inheriting logging handlers in forked processes causes deadlocks.
  • Spawn creates new handlers, but ignores existing ones.
  • QueueListener decouples logging from worker processes.

How to Clean Up Your Gmail Storage Space

A nearly full Gmail account does not always mean you have too many emails. Large attachments, old conversations, years of … Read More The post How to Clean Up Your Gmail Storage Space appeared first…

More from Saturday 19 September →