Fast Data Transfer for rewrites between your team's projects is now free
By Steven Van ·
Each external rewrite still counts as a separate Edge Request, with routing and firewall checks enforced for each project.
Only the destination request now incurs Fast Data Transfer usage when an external rewrite routes traffic between projects on the same Vercel team. Transfer for the original request is free, with the two streams consolidated to reduce overall transfer.
Routing between projects
Rewrites forward requests without changing the URL shown in the browser. Teams can use them as a reverse proxy or to combine multiple Vercel applications into one website, configuring routes in vercel.json, middleware, or next.config.ts. Vercel’s rewrites documentation explains the setup.
Edge Requests still count separately
Each external rewrite still counts as a separate Edge Request and runs through a full request lifecycle, including routing and Web Application Firewall checks. Security policies remain enforced for each project.