Vercel and Netlify Win on Developer Experience
Bucky Moore, Partner at Kleiner Perkins, on Jamstack's big upside case
The real wedge for Vercel and Netlify is not raw infrastructure, it is packaging cloud primitives into a workflow that feels obvious to front end teams. AWS is built to sell compute, storage, and databases that work for millions of use cases. Vercel and Netlify win by turning those same building blocks into one click deploys, preview links for every pull request, and defaults tuned for JavaScript teams.
-
The product difference shows up in daily work. Netlify automatically creates a unique preview URL for each pull request, posts status back into the repo, and lets teams review changes before production. That is a much tighter loop than wiring up S3, CloudFront, Lambda, and CI by hand on AWS.
-
Even when AWS offers a simpler layer like Amplify, it is still mainly an on ramp into AWS. Internal interviews describe it as good on the happy path, but once a team needs something custom, they fall back into the full maze of underlying AWS services. That reflects AWS's core strength in primitives, not polished opinionated workflows.
-
This pattern has precedent. Heroku won developers by making deployment far easier than raw cloud setup, and Jamstack platforms apply the same playbook to modern front end stacks. They are not inventing new infrastructure so much as selling saved time, fewer DevOps hires, and better collaboration around shipping code.
Going forward, the market is likely to keep splitting in two. AWS will keep improving baseline tools for the broad cloud customer base, while specialists like Vercel, Netlify, and newer edge platforms keep moving faster on opinionated developer experience. As long as web teams value speed and simplicity over lowest level control, that layer will remain defensible.