Vercel’s CDN, which can proxy requests to external backends, now caches proxied responses using the CDN-Cache-Control and Vercel-CDN-Cache-Control headers. This aligns caching behavior for external backends with how Vercel Functions are already cached.
This is available starting today, on all plans, at no additional cost.
Per the Targeted HTTP Cache Control spec (RFC 9213), these headers support standard directives like max-age and stale-while-revalidate, enabling fine-grained control over CDN caching without affecting browser caches.
You can return the headers directly from your backend, or define them in vercel.json under the headers key if your backend can't be modified.
No configuration changes or redeployments required. Return the header (or set it in vercel.json) to improve performance, reduce origin load, and ensure fresh content.
Learn more about CDN-Cache-Control headers.
Reference Architecture
Choose a stack and work through the decisions behind it, with curated documentation, guides, templates, and courses to help you build.
- Agent stack: Build and operate agents with models, tools, and durable workflows.
- Web applications: Choose rendering, data, authentication, and caching approaches.
- Backends: Choose a runtime, connect services, and run background work.
Build with prompts
Build an app, extend an agent, or improve your project with ready-to-use prompts for your coding agent.