Vercel Is Merging Data Cache Into Runtime Cache: Migration Dates, Pricing and What Changes
Vercel is merging its Next.js Data Cache into Runtime Cache, giving every project its own storage allocation at 8x (Pro) or 10x (Enterprise) the old team-wide pool, with no code changes needed for fetch caching or unstable_cache. New teams created on or after October 30, 2026 use Runtime Cache by default; existing Hobby teams migrate on November 29, 2026, and Pro and Enterprise teams get individual migration notices. After migrating, previously free Data Cache reads and writes are billed at Runtime Cache rates, though Hobby keeps a free monthly allowance. [1] [2]
SeekVero editorial · Published · Prepared with AI assistance; no hands-on testing claimed.
Prepared from cited sources. No hands-on testing claimed.
What's changing, and why
Vercel announced on October 30, 2026 that Data Cache is exiting beta and merging into Runtime Cache. Next.js fetch caching and unstable_cache switch over on every Next.js version without any code changes. [1]
Data Cache was introduced with Next.js 13 as a specialized cache for segment-level data in the App Router: using fetch or unstable_cache automatically provisions globally distributed caching infrastructure with no extra configuration. Runtime Cache keeps that same no-config behavior but adds faster performance under load, more storage per project, and deeper observability. [2]
Each project and environment now gets its own Runtime Cache storage allocation instead of sharing one team-wide pool. Pro projects get 8x the space Data Cache's previous team-wide pool had, and Enterprise projects get 10x. [1]
In Next.js 15, fetch and unstable_cache already use Data Cache. In Next.js 16, those two APIs keep using Data Cache as a separate layer, while new caching code built with Cache Components should use use cache: remote to store data directly in Runtime Cache. [2]
When does your team migrate?
Teams created on or after October 30, 2026 use Runtime Cache by default for fetch caching and unstable_cache, in every project, on every Next.js version. No action is needed for those teams. [1] [2]
Existing teams migrate on a schedule set by plan: Vercel will migrate existing Hobby teams on November 29, 2026. Pro teams will be notified of their specific migration date and of when billing changes take effect. Enterprise teams will be contacted directly by their account team with migration details. [1] [2]
Starting October 30, 2026, existing Hobby and Pro teams can also opt in early from their team's CDN settings, and Runtime Cache pricing applies as soon as a team opts in. [1]
When a team migrates, Vercel repopulates existing fetch, unstable_cache, and use cache: remote entries from live traffic, so some extra cache misses and backend requests should be expected right after migration. Entries that were written through getCache are kept. [2]
What it will cost
Once a team migrates, Data Cache reads and writes that were previously unbilled are charged at Runtime Cache pricing: rates start at $0.40 per million read units and $4.00 per million write units, and vary by region. [1]
Hobby teams get 1 million read units and 200,000 write units free each month across all projects. On Pro, usage draws from the plan's $20 monthly infrastructure credit, and anything beyond that credit is billed at regional rates. Enterprise teams should contact their account team for pricing. [1]
How to prepare before you migrate
Before migrating, review your project's current Data Cache usage in Observability to estimate the cost impact. If usage is higher than expected, Vercel's optimization guide walks through finding and reducing unnecessary reads and writes, or you can copy Vercel's own agent prompt into your coding agent to have it investigate for you, or select "Optimize with Vercel Agent" directly in the Runtime Cache dashboard. [1] [2]
Teams can also disable fetch and unstable_cache caching entirely from CDN settings. This sends more requests through to the underlying data sources, and does not stop the migration from happening. [1]
Data Cache fits data that can be reused across requests, such as API responses that stay the same across multiple requests, database queries that don't change often, or data fetched inside server components or route handlers. It is not meant for user-specific data, data that must be fresh on every request, or complete HTTP responses, which should use CDN Cache instead. [2]
Frequently asked questions
Do I need to change my code for this migration?
No. Fetch caching and unstable_cache switch from Data Cache to Runtime Cache automatically on every Next.js version, with no code changes required. [1]
When exactly does my team move to Runtime Cache?
New teams created on or after October 30, 2026 use Runtime Cache immediately. Existing Hobby teams migrate on November 29, 2026; existing Pro teams get a specific migration date by notification; Enterprise teams are contacted directly by their account team. [1] [2]
Will migrating cost me more?
Possibly. Data Cache reads and writes that were previously unbilled become billed at Runtime Cache rates ($0.40 per million read units, $4.00 per million write units, varying by region) once a team migrates. Hobby teams still get a free monthly allowance of 1 million read units and 200,000 write units, and Pro usage draws from the plan's existing $20 monthly infrastructure credit before extra charges apply. [1]
Can I switch to Runtime Cache before my scheduled migration date?
Yes. Existing Hobby and Pro teams can opt in early from their team's CDN settings starting October 30, 2026, though Runtime Cache pricing applies as soon as they do. [1]
What happens to my already-cached data when I migrate?
Vercel repopulates existing fetch, unstable_cache, and use cache: remote entries from live traffic after migration, so expect some extra cache misses and backend requests at first. Entries written through getCache are kept as-is. [2]
Next step
Vercel's own documentation covers every migration step, pricing tier, and optimization option for teams moving from Data Cache to Runtime Cache.
Read Vercel's Runtime Cache migration docs