Data Cache is moving to Runtime Cache

Data Cache is exiting beta and moving to Runtime Cache. Next.js fetch caching and unstable_cache will switch over on every version without code changes. On Pro, each project and environment gets its own Runtime Cache storage allocation, with 8x the space of Data Cache’s previous team-wide pool. Enterprise projects get 10x their previous Data Cache storage.

Once your 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.

Hobby teams get 1 million read units and 200,000 write units free each month across all projects. On Pro, usage draws from your $20 infrastructure credit each month, and anything beyond it is billed at regional rates. For Enterprise pricing, contact your account team.

Migration

Teams created on or after October 30, 2026 use Runtime Cache by default.

If your team already uses Data Cache:

• Hobby: We’ll migrate your team on November 29, 2026.
• Pro: We’ll notify you of your migration date and when billing changes take effect.
• Enterprise: Your account team will contact you with migration details.

Before you migrate, review your project's Data Cache usage in Observability. To cut unnecessary reads and writes, follow the optimization guide or copy the agent prompt into your coding agent. In the Runtime Cache dashboard, you can also select Optimize with Vercel Agent.

Starting October 30, existing Hobby and Pro teams can opt in early from your team's CDN settings. Runtime Cache pricing applies as soon as you opt in.

You can also disable fetch and unstable_cache caching in CDN settings, which sends more requests to your data sources but doesn’t stop your migration.

Read about the architecture and recent improvements in the blog post.