Vercel merges Data Cache into Runtime Cache
Vercel is consolidating its Data Cache into Runtime Cache, so Next.js fetch and unstable_cache caching now use the same storage as the existing Runtime Cache APIs. Pro and Enterprise projects receive larger storage allocations, and the Runtime Cache view gains deployment markers, revalidation causes, and write utilization.
Why it matters
Next.js fetch and unstable_cache users need no code changes. Pro gets per-project, per-environment storage at 8x the previous team-wide Data Cache pool, and Enterprise gets 10x. One set of storage budgets and usage tools now covers all four caching APIs.
Who should care
Next.js developers using fetch or unstable_cache, teams on Vercel Pro or Enterprise, developers using getCache or use cache: remote
What you can do
Open the Runtime Cache view in the Vercel dashboard and check which entries are written often but rarely read, to decide what to stop caching.