Vercel lifts Blob store caps on all plans and bills creation as an operation

Vercel has removed all limits on how many Blob stores an account can create, according to a changelog post on the Vercel blog. Hobby plans were previously capped at 100 stores, Pro at 500 and Enterprise at 1,000; those ceilings are gone, and every plan can now create as many stores as it needs.

How creation is billed now

The offsetting change is that creating a store is now a metered action. Vercel says store creation is billed together with its other Blob Advanced Operations — the same bucket that covers put(), copy() and list() calls. On Pro, that bucket costs $5.00 per million operations. On Hobby, each store created draws down the 2,000 free operations the plan includes each month. Deleting a store remains free.

Storage, operations and data transfer continue to be billed on actual usage, Vercel notes, so spreading the same data across more stores costs the same overall — the new charge only attaches to the act of creating a store. Store creation entries appear under Blob Advanced Operations both on the usage page and in the Observability dashboard.

The patterns Vercel is encouraging

The company presents the change as a move away from naming conventions and toward true isolation boundaries, and it lists three patterns it has in mind:

• Giving production, staging and preview environments their own store, and therefore their own credential.
• Creating one store per customer in a multi-tenant app, so a single tenant's data can be exported or deleted in one call.
• Standing up a store for a preview branch or a migration and tearing it down afterwards — deletion is free, so temporary stores only cost their creation.

Where the free tier lands

For Hobby users, the practical limit is no longer the store count but the shared 2,000-operation allowance, which now has to absorb store creation alongside put(), copy() and list() calls. Projects that routinely create and destroy stores — one per preview branch, for instance — will want to watch that budget, since it draws from the same pool as ordinary Blob operations. Vercel's Blob pricing documentation carries the full details.

Why it matters

Store-count caps quietly shape architecture. Under the old limits, the sensible move was a small number of shared stores with key prefixes, which works fine until you need real isolation: separate credentials per environment, clean per-tenant deletion for compliance or offboarding, or a guaranteed wipe of preview data. Those are exactly the cases Vercel now highlights, and with the caps gone — including the 1,000-store ceiling that even Enterprise faced — store-per-tenant and store-per-environment designs become practical at any plan level.

The pricing model matches the pattern: because storage, operations and transfer are usage-based, extra stores cost nothing additional to keep, and the only gate on creation is a charge that falls under the same low per-million pricing as routine operations. For teams building multi-tenant applications on Vercel, this reads less like a pricing tweak and more like permission to model isolation the way they would with buckets on other object-storage platforms.