Regional Runtime Cache

Runtime Cache is now regional and served from Easel’s edge, matching Vercel’s model. Every deployment connects to it automatically, with no credentials or environment variables to set.

Use it from your code

Call getCache() from @vercel/functions and use get, set, delete, and expireTag as you would on Vercel. In Next.js, 'use cache: remote' stores entries in Runtime Cache so instances in a region share them. Plain 'use cache' keeps Next.js’s in-memory cache per instance, checked against Easel’s tag state so an expired tag is never served.

Tags are one namespace across Easel’s caches. revalidateTag and revalidatePath expire matching Runtime Cache entries, and getCache().expireTag purges ISR, CDN, and 'use cache' entries with that tag. Tag expiry reaches every region.

How the cache behaves

• Regional: each function reads and writes the cache in its home region
• Persists across deployments: on Pro, each project has one cache per environment; on Hobby, a workspace’s projects share one
• Never stale: after a delete, overwrite, or tag expiry, the old value is never served
• Bounded: 64 MiB per cache per region on Hobby, 128 MiB on Pro; when full, Easel evicts the least recently used entries instead of failing writes

Purge cache on the project clears the cache the live deployment uses.

Usage and billing

Reads bill Cache Read Units on hits only, and stored writes bill Cache Write Units, priced in the cache’s home region. Misses, deletes, tag expiry, and evictions are free. The Runtime Cache panel in Observability shows reads, writes, hit rate, and storage per region.

See Runtime Cache for examples and limits.