routing-middleware

Edge redirects and rewrites can be handled by adding a root middleware.ts file with a default export function. This intercepts requests at the Vercel platform layer before caching, allowing routing changes without application code deployments.

Yes, routing middleware is framework-agnostic and works across Next.js, SvelteKit, Astro, and Nuxt. It uses a consistent middleware entrypoint to apply CDN routing rules universally across these deployed frameworks.

You can restrict middleware execution to specific routes by setting the config.matcher property in your middleware entrypoint. This targets scoped interception, reducing unnecessary compute for high-traffic routes before cache.

Edge-level personalization routes requests based on geolocation or experiment assignment using platform-friendly primitives. It intercepts requests at the CDN edge, applying header injection and targeted routing without touching app runtime logic.

Vercel routing middleware supports Edge, Node, and Bun runtimes. It requires a root middleware.ts or middleware.js entrypoint with default export semantics to function across these supported environments.

Use edge middleware for CDN routing when you need to adjust request routing rules, headers, or redirects without redeploying app code. It applies lightweight per-request behavior at the platform level before caching for high-traffic routes.