From Heroku to Developer Operating Systems
Jason Lengstorf, VP of Developer Experience at Netlify, on Jamstack's anti-monolith approach
The real inheritance from Heroku is not just easy hosting, it is turning deployment into a default workflow instead of an infrastructure project. Heroku made git push to production feel normal for app developers, then Netlify and Vercel rebuilt that idea for the Jamstack era with previews, rollbacks, and managed integrations that fit front end teams working out of GitHub. Fly.io extends the same promise to full apps that need long running compute closer to users.
-
Heroku won by removing server chores from developers. By 2010 it was already running more than 105,000 Ruby apps, and its add ons and Postgres product turned third party infrastructure into one click building blocks. That model taught the next generation of dev tools that abstraction itself can be the product.
-
Netlify pushed the idea further into team workflow. A code change can automatically create a Deploy Preview, and edge logic ships in the same deployment system with atomic deploys and rollbacks. That means product, design, and marketing can review a live URL before release instead of waiting on a staging setup.
-
Vercel added a tighter framework loop than Heroku had. Its Next.js integration generates preview URLs for pull requests and ties hosting directly to the framework many React teams already use. That gives Vercel influence earlier in development, not just at the final deploy step, which is a deeper wedge than classic PaaS offered.
The category is moving from Heroku style painless deploys toward full developer operating systems. The winners will combine hosting, previews, edge execution, data and framework level defaults, so teams can ship production software without assembling their own stack from raw cloud parts. That is the path from convenience feature to durable platform.