Edge Middleware on the platform

Vercel-compatible Edge Middleware now runs on Easel. Your middleware bundle ships with the deploy, and the edge runs it before the request reaches static assets or functions. Middleware executes as a Function in US East (iad).

How it ships

When your framework produces a middleware artifact, Easel packages it with the rest of the deployment. There is no separate upload step. On each request that matches middleware, the edge calls your middleware first.

You can rewrite, redirect, set headers, or gate access the same way you would on Vercel-style middleware. Keep work short; middleware sits on the hot path for matched routes.

What to expect

Middleware shares the platform’s edge runtime packaging, so versions stay consistent across projects. Failures and timing show up in Observability with the rest of the request path.

If you rely on request headers for geo or client hints, see CDN headers. For broader edge behavior, start with CDN.