# Vercel — Simplifying runtime caching on Vercel

- Company: Vercel (vercel.com)
- Announced: 2026-10-30T04:00:00+00:00
- Category: availability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://vercel.com/blog/simplifying-runtime-caching-on-vercel
- Record: https://forck.live/items/29976-simplifying-runtime-caching-on-vercel
- Subject: v0 / AI SDK / AI Gateway
- Pricing: Previously unbilled Data Cache reads and writes will follow Runtime Cache pricing

Vercel is folding its Data Cache into Runtime Cache so developers have one data caching product across frameworks and APIs, with no code changes for Next.js fetch caching or unstable_cache users. Data Cache had been Vercel's caching service for the Next.js App Router, while getCache and 'use cache: remote' used Runtime Cache; the migration brings all four APIs under one set of storage budgets and usage tools. On Pro, each project and environment now gets its own storage allocation, 8x the space of Data Cache's previous team-wide pool, and Enterprise projects get 10x their previous Data Cache storage. Vercel says the infrastructure handles more than 440 million reads and moves more than 18 TB of data every hour, with each region keeping its own cache and a cache hit taking one round trip. Circuit breakers enabled in every region in August let reads fall back to in-memory tag timestamps during traffic bursts, and Vercel says p99 cache-service read latency in its largest region fell to about one fifth of its previous level at comparable traffic. Previously unbilled Data Cache reads and writes will follow Runtime Cache pricing, new teams use Runtime Cache automatically, and existing teams will get migration and billing details in advance.

## Evidence

Verbatim from https://vercel.com/blog/simplifying-runtime-caching-on-vercel:

> Today, we’re bringing Data Cache into Runtime Cache, giving developers one product for data caching across frameworks and APIs. If you use Next.js fetch caching or unstable_cache , you won’t need to change your code. Pro and Enterprise projects will get larger storage allocations.
> 
> Runtime Cache lets your code reuse fetched or computed data across requests without operating a separate caching service. Over the past year, we’ve improved read performance during traffic bursts, increased storage budgets, and made cache usage easier to investigate.
> 
> Copy link to heading Why we built Runtime Cache
> 
> Data Cache was originally launched as Vercel’s data caching service for the Next.js App Router, used by fetch caching and unstable_cache . Unlike CDN caching , which stores complete HTTP responses, Data Cache stores data your application uses to generate those responses. A product page, for example, can reuse cached catalog data while rendering a personalized response for each visitor.
> 
> We wanted developers to have access to that service without depending on Next.js. Last year, we introduced Runtime Cache with a direct API: getCache from @vercel/functions .

---

Record: https://forck.live/items/29976-simplifying-runtime-caching-on-vercel
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md