routing-middleware

Edge request interception is achieved by creating a root middleware.ts or proxy.ts file, configuring the runtime, and defining a matcher-based scope to apply rewrites and redirects before caching occurs.

Vercel routing middleware is runtime-agnostic and fully supports Edge, Node.js, and Bun runtimes, allowing framework-agnostic configuration for intercepting and manipulating incoming requests across any application.

Geo-based routing and personalization are implemented through platform-level request interception using Vercel middleware, applying location-based decisions and A/B style variations before the request reaches your application logic.

Configuring redirects and rewrites requires a root middleware.ts or proxy.ts file for Next.js 16, where you must define the active runtime and establish a matcher-based scope to control request interception.

Vercel middleware applies to any framework, providing platform-level request interception that enables precise routing, rewrites, redirects, and personalization across diverse frameworks and runtimes without framework-specific limitations.

Platform-level middleware intercepts and modifies requests before caching and application execution, enabling precise routing and geo-based decisions at the edge with lower latency than processing redirects within application code.