Vercel's Blob update removes plan-specific limits on the number of stores. That lets an application use separate stores as boundaries between environments or customers, with separate access credentials, rather than relying only on different paths within one store.
This can simplify handling one customer's data or disposing of storage created for a temporary preview. Store creation now counts as a billed advanced operation, while deletion is free. Storage, other operations and data transfer remain usage-based charges, so the announcement expands organizational flexibility without making the stored data itself unmetered.
Key takeaways · AI-distilled
On Hobby, Blob store creation counts toward the 2,000 free Advanced Operations each month, the same bucket as put(), copy() and list() calls, and deleting a store is free.
Vercel suggests stores as hard boundaries instead of pathname conventions: separate production, staging and preview data with their own credentials, or give each tenant a store so one customer's data can be exported or deleted in a single call.
Storage, operations and data transfer are still billed on usage, so Vercel says splitting the same data across more stores costs the same. Store creation appears under Blob Advanced Operations on the usage page and in the Observability dashboard.
