External rewrites between projects within the same team now use Fast Data Transfer only for the destination request. This change makes Fast Data Transfer for the original request free.
Commonly used as a reverse proxy or for microfrontend architectures, rewrites can be configured in vercel.json, middleware, or next.config.ts to route requests between the same or separate Vercel projects without changing the URL shown to the user.
Usage for external rewrites to the same team:
Fast Data Transfer for the original and destination request have been optimized and consolidated into a single stream, reducing overall transfer.
Each external rewrite triggers a full request lifecycle, including routing and Web Application Firewall checks, ensuring security policies are enforced per project, and counts as a separate Edge Request.
Learn about rewrites and monitor your Fast Data Transfer usage and observability.