gacor: Vercel moves Next.js Data Cache into Runtime Cache

Vercel announced on October 30 that its Data Cache is leaving beta and consolidating into Runtime Cache. For Next.js applications, fetch caching and unstable_cache are expected to move without code changes.

What changes for teams

• Runtime Cache becomes the common product for framework cache APIs and Vercel's direct cache API.
• Vercel says Pro projects receive per-project, per-environment storage with eight times the space of the previous team-wide Data Cache pool; Enterprise projects receive ten times the previous allocation.
• Previously unbilled reads and writes follow Runtime Cache pricing after migration, so teams should review usage and the rollout details.

The announcement also describes a migration schedule for existing Hobby teams and individual dates for Pro and Enterprise teams. Check the current dashboard and official documentation before changing settings; early opt-in starts billing under Runtime Cache pricing.

This is a platform and billing change, not a change to the application's cache API. Teams with high cache traffic should measure reads and writes before their migration date.