Jamstack: Workflow, Not Hosting
Diving deeper into
Bucky Moore, Partner at Kleiner Perkins, on Jamstack's big upside case
What it's about is the workflow on top of those services that makes everything really easy and low cognitive load to operate.
Analyzed 5 sources
Reviewing context
The real product is not hosting, it is the removal of dozens of small infrastructure decisions that slow teams down. Netlify turned storage, CDN, builds, rollbacks, previews, and serverless functions into a default workflow tied to Git, so a developer can push code, get a live preview URL, share it with teammates, and ship without touching provisioning, routing, or deploy machinery.
-
The clearest practical gain is in day to day collaboration. Branch deploys and preview URLs let designers, PMs, and clients review a working version from a pull request, instead of waiting for engineering to wire up a staging environment by hand.
-
This is why Netlify and Vercel were often compared to Heroku. The value is not cheaper raw infrastructure, it is opinionated defaults that package file storage, CDN, compute, routing, and rollback into one path that feels like a push button deploy.
-
AWS can offer similar underlying pieces, but it still asks teams to understand the pieces. Netlify and Vercel win when a frontend team wants the same outcome every time, without choosing services, tuning config, or risking a maze of cloud settings and surprise bills.
This points toward a larger shift where cloud infrastructure gets bought more like software than like raw compute. The winners will keep moving up the stack, owning the default workflow for building, previewing, and shipping, while the underlying cloud becomes an interchangeable input.