Heroku Abstraction Extended to Frontend
Jason Lengstorf, VP of Developer Experience at Netlify, on Jamstack's anti-monolith approach
Heroku’s breakthrough was selling relief to developers, not by writing business features, but by removing the repetitive infrastructure work sitting between code and production. Instead of making teams wire up runtimes, add services, and manage deployment machinery by hand, Heroku turned that into a managed path with buildpacks, dynos, and add ons. Netlify and Vercel extended the same idea upward into the frontend workflow, where every pull request can generate a preview, rollback is built in, and deployment becomes part of everyday product iteration.
-
The middle of the stack means developer operations work that users never see directly, but that determines how fast a team ships. At PayPal, moving static assets through traditional server deploys could take hours. Jamstack tooling separated markup from APIs so teams could ship the UI fast without redeploying whole server fleets.
-
Heroku abstracted server era plumbing. Developers pushed code, Heroku detected the language with buildpacks, packaged the app, ran it in dynos, and let teams plug in databases and other services through add ons. That removed a lot of manual setup, which is why it became the reference point for later developer platforms.
-
Netlify and Vercel changed the unit of abstraction from app server to frontend change set. Netlify automatically creates a Deploy Preview for pull requests and uses atomic deploys. Vercel creates preview deployments for PRs and branch pushes. That makes review, rollback, and stakeholder feedback part of the default workflow instead of extra process.
The next step is deeper automation around edge compute, server rendering, and collaboration, so the winning platforms will own more of the path from local code to live customer experience. The market keeps moving from managed infrastructure toward managed workflow, and the companies that win will be the ones that keep deleting invisible developer chores without boxing teams into a rigid stack.