Vercel Packages Cloudflare Edge
Thom Krupa, co-founder of Bejamas, on building dynamic apps on the Jamstack
The key point is that Vercel wins by packaging global edge infrastructure into a much simpler product than running Cloudflare directly. Teams push a Next.js app from Git, get previews, caching, rollbacks, and edge execution without stitching together Workers, routing, and deployment tooling themselves. That means the real product is not raw network capacity, it is the developer workflow layered on top of distributed infrastructure.
-
In the Jamstack stack, Cloudflare represents the underlying edge model, code running close to users across many locations, while Vercel turns that into an opinionated app platform for frontend teams. Multiple interviews describe Vercel as part of the same edge shift, but focused on making the happy path easier.
-
That is why Vercel and Cloudflare can be both partners and competitors. Vercel has historically benefited from Cloudflare style edge distribution, yet Cloudflare Pages and Workers also sell directly to developers who are willing to trade ease of use for more control, broader infra primitives, and lower level access.
-
The stack has also been moving inward. By June 25, 2025, Vercel said Edge Middleware and Edge Functions were powered by unified Vercel Functions infrastructure, which shows the long term direction, owning more of the compute layer while preserving the same developer experience at the surface.
Going forward, the market keeps converging around the same edge primitives, so the durable advantage shifts to who makes global apps easiest to build and operate. Vercel is moving deeper into owned infrastructure, while Cloudflare keeps moving upward into developer platforms, which pushes both toward a direct fight over the full modern web app stack.