Developer Experience as a Product
Jamund Ferguson, senior engineer at PayPal, on using Jamstack in the enterprise
The real product here is not hosting, it is a faster path from code to a live site. Netlify and Vercel sit on top of commodity cloud pieces like storage, CDN, and serverless compute, then bundle the annoying setup work into defaults like Git based deploys, preview links, rollbacks, and edge delivery. That convenience is valuable because it saves expensive engineering time, even when the underlying infrastructure is not unique.
-
The closest historical analog is Heroku. The pattern is to take cloud primitives that already exist, hide the wiring, and make deployment feel like a push button workflow. In practice that means a front end team can connect a repo, push code, get a preview, and ship without touching buckets, CDNs, or provisioning logic.
-
This is why these platforms can charge a markup over raw cloud services. Netlify framed the value as replacing staff time spent on setup, rollback, DNS, and delivery plumbing, while broader market work showed these platforms selling at materially higher bandwidth prices than CloudFront because customers were paying for workflow, not raw bytes.
-
The weak point is that the premium narrows as the big clouds copy the workflow. AWS Amplify already offers repo connected CI/CD and a bundled on ramp into AWS, and Cloudflare has pushed real infrastructure innovation with Workers and edge execution. That means the durable advantage is whoever keeps the developer workflow simplest as features converge.
Going forward, this market keeps moving up the stack. Basic hosting features will keep becoming standard inside AWS, Azure, and Cloudflare, so the winners will be the platforms that turn deployment, previews, observability, edge logic, and adjacent tools into one smooth default workflow. The markup survives as long as using the platform stays easier than assembling the pieces directly.