[elithrar]

> "Worker" functionality is already available on both Netlify and Vercel.

Workers at those providers do not run _at the edge_ for each request. They lean on AWS Lambda to pre-generate or render assets, but you can't reliably run a function there on every user-facing request without a noticeable latency penalty.

[edaemon]

Vercel's functions do run at the edge, but Netlify's are just AWS Lambda functions.

[oapsi]

How is this different than Vercel? We already has a big CF account so it would be easy to move there (we have a bunch of Stackbit sites that are currently deployed on Vercel)