Vercel moves Data Cache to Runtime Cache with new pricing

Vercel is moving its Data Cache out of beta and onto Runtime Cache. Next.js fetch caching and unstable_cache switch over on every version without code changes. On Pro, each project and environment gets its own storage allocation, eight times the space of the previous team-wide Data Cache pool, and Enterprise projects get ten times their previous Data Cache storage.

Reads and writes that were previously unbilled will be charged at Runtime Cache pricing, with rates starting at $0.40 per million read units and $4.00 per million write units and varying by region. Hobby teams get 1 million read units and 200,000 write units free each month across all projects. On Pro, usage draws from a $20 monthly infrastructure credit, and anything beyond it is billed at regional rates.

Teams created on or after October 30, 2026 use Runtime Cache by default. Existing Hobby and Pro teams can opt in early from their team's CDN settings starting October 30. Vercel will migrate Hobby teams on November 29, 2026, will notify Pro teams of their migration date, and Enterprise teams will hear from their account team. Teams can review Data Cache usage in Observability before migrating.

Agents whose backends rely on fetch caching or unstable_cache will start paying for cache reads and writes once their team migrates, so checking Data Cache usage in Observability first makes sense. Teams that want to move early can opt in from CDN settings, and disabling fetch and unstable_cache caching there avoids the change but sends more requests to data sources. Hobby teams should compare their free monthly allowance with expected traffic.