Vercel Wins on Developer Experience
Thom Krupa, co-founder of Bejamas, on building dynamic apps on the Jamstack
Vercel wins by turning raw cloud infrastructure into a product that a front end team can use without thinking about infrastructure at all. In practice that means connecting a Git repo, getting preview deployments automatically, shipping serverless and edge functions with sensible defaults, and avoiding the setup, maintenance, and billing surprises that come with assembling S3, CloudFront, CI/CD, and functions directly on AWS.
-
The closest AWS equivalent is Amplify, which can connect a repository and deploy to a CDN, but custom AWS setups add build time and ongoing maintenance because someone has to own configuration, permissions, and reliability. That is the extra work Vercel is selling away.
-
This is the same pattern Heroku used for Rails. The underlying compute and storage are not unique. The value is the opinionated path. Vercel bundles storage, compute, CDN, routing, and deployment into one workflow, which is why teams pay a markup over base cloud costs.
-
The main breakpoint is not scale, it is economics and platform policy. Teams move to AWS when they want every workload under one vendor, need adjacent AWS services like ML or media tooling, or grow large enough that direct cloud pricing and in house DevOps start to pencil out.
Going forward, this competition shifts from static hosting to owning the whole developer loop, from writing code to previewing, deploying, and now generating apps with AI. The platform that keeps making the happy path faster will keep pulling work up from AWS, even while AWS remains the default place large companies consolidate infrastructure.