⌘K
Amy Egan Hey, James. Appreciate you reaching out about this. The team shipped an update yesterday so your dashboard now reflects each day's deployment storage amount instead of the billing period maximum. I'm linking some Deployment Storage optimization tips in case you still need help reducing the amount of storage used https://vercel.com/docs/deployment-storage/optimize
James Singleton Hi Amy. Yea after doing some Googling I was able to find stuff about it. It's a little concerning that this was pushed out without an email letting users know. All of a sudden I was getting emails saying that I was using 40 GB of the 10 GB of deployment storage with a single deployment taking up like 30 GB. I started to panic! One issue I ran into is that retention policies were defaulted to 30 days for everything. Even after setting some to 1 week and in some cases 1 day, I wasn't seeing deployments being removed. I had to go through and manually delete deployments. I basically had to delete all by 6 deployments for my major project with 5 of those being production deploys and one being a preview. I am down to 11 GB now out of 10... I was below 10 earlier today but then opening a PR to a repo pushed me up to 11 GB. So I have gone through and done what the docs say to do, yet it seemed that Vercel was not going and removing the old deploys after I saved the changes, even days after updating.
James Singleton To add to this, there are projects where the retention is 30 days and I have deployments from January still in my Deployments tab. This project was defaulted to 30 days and I have deployments from Jan-May still there.
Tw9jsn5hmc 5685 Any updates?
Amy Egan The team shipped an update yesterday so your dashboard now reflects each day's deployment storage amount more quickly. If you still need help with high storage use, please try the optimization steps linked below and let us know if you run into any issues https://vercel.com/docs/deployment-storage/optimize
Jacob Paris I've temporarily unsuspended the store, I think it re-suspended itself for still being over the limit — if you remove a few files to get it below the Hobby limits then it'll remain unsuspended this time, but either way you can get your files out now
Dzirnavu113a 1462 Hello, I have the same issue with my Vercel Hobby Blob store. My store bf-latvija-wordpress-blob is blocked after exceeding the Advanced Operations limit (2.2k / 2k). This Blob store contains the SQLite database for my WordPress site, so the block currently prevents WordPress from reading the database and saving any changes. I also tried the one-time unblock form, but it says: "This endpoint only works for teams that are currently soft-blocked." Could you please temporarily unsuspend/unblock my Blob store so I can regain access to my WordPress database and migrate it to another storage solution? I am not requesting additional quota. I only need temporary access to recover my existing data. Thank you!
Ryu Hi Kapeel, Not necessarily. The current replacement path for Vercel KV-style usage is usually Upstash Redis through Marketplace, but it does not have to be one shared database for every project. Upstash's current Redis pricing page says you can create up to 10 Redis databases for free, then additional databases are charged after that: https://upstash.com/pricing/redis So if you only need a few projects, I'd first try creating separate Redis databases from the Upstash console, then connect each one to the relevant Vercel project by adding the generated env vars for that project: ``` UPSTASH_REDIS_REST_URL UPSTASH_REDIS_REST_TOKEN ``` If the Marketplace flow is only showing one database from inside Vercel, that may just be the integration/provisioning UI path rather than the actual Upstash account limit. Creating/managing the databases directly in Upstash and then adding the env vars in Vercel should still work. For small projects where hard isolation is not important, another option is one Redis database with key prefixes per project/environment: ``` project-a:prod:session:... project-a:preview:session:... project-b:prod:session:... ``` But if you want the same mental model as "one KV store per project," I'd use separate Upstash Redis databases until you hit the provider's free database or usage limits.
Kapeel Kokane I checked the link that you shared to verify but still found that only 1 Redis database is allowed on the free plan. Am I missing something?
Ryu Hi Kapeel, You’re not missing something — I think my earlier wording was too broad. Looking again, the Upstash pricing page/UI is not as simple as “10 free Redis databases” in the same way Vercel KV used to feel like “one store per project.” The free Redis plan appears to be limited to 1 free database in the plan comparison, while additional databases may require moving into their paid / usage-based setup. So for the exact old Vercel KV experience of “one separate KV database per Vercel project at no cost,” I don’t think there is currently a perfect 1:1 replacement. The practical options seem to be: ``` 1. Use one Upstash Redis database and separate projects with key prefixes 2. Use separate Upstash Redis databases if you’re okay with their paid/usage-based limits 3. Use a different storage provider if you need free per-project isolation ``` For small apps, key prefixes can work fine, for example: ``` project-a:prod:... project-a:preview:... project-b:prod:... ``` But if you need hard isolation per project, then yes, Upstash’s current free plan may not match what Vercel KV previously provided.
