The Promise of a Simpler Web
To understand the disagreement, you first have to understand the dream Netlify was selling. In the mid-2010s, building for the web was often a complex, server-heavy affair. Netlify, along with others, championed a new architecture called the Jamstack
(JavaScript, APIs, and Markup). The idea was deceptively simple: instead of building web pages on the fly for every visitor, you pre-build them into static files and serve them from a global network. The result was faster, more secure, and cheaper-to-run websites. Netlify didn't invent this concept, but they built a powerful, user-friendly platform around it. With features like seamless Git integration and one-click rollbacks, they made a highly technical process feel magical. For thousands of developers, Netlify wasn't just a hosting provider; it was the flag-bearer of a better way to build.
A Tale of Two Histories
Here’s where the historical accounts diverge. In one telling, Netlify’s co-founder, Matt Biilmann, coined the term “Jamstack” and the company evangelized the architecture, building a community and an ecosystem where none existed. In this version of history, Netlify is the visionary protagonist that gave a name and a platform to a powerful set of emerging best practices. The other perspective, held by many veteran engineers, is less romantic. Critics, such as architect and conference speaker Brian LeRoux, argue that “Jamstack” was a clever marketing term for what was essentially just well-known static site generation. They contend that Netlify successfully rebranded a decades-old concept and positioned itself as the indispensable tollbooth on a road that was already being built. To them, the “history” Netlify promotes is a form of revisionism that centers the company in a movement that was always larger and more decentralized.
The Pivot and The 'Betrayal'
The disagreement might have remained a niche academic debate if not for Netlify's recent evolution. As a venture-backed company, Netlify needed to grow. That growth came from moving beyond simple static hosting and into more complex, dynamic functionality. The company introduced features like Edge Functions (which run code on the server, closer to the user) and On-demand Builders, which generate pages when they’re first requested—a practice that sounds suspiciously like the old server-based methods Jamstack was meant to replace. For early adopters, this felt like a betrayal. The original promise of Jamstack was portability and simplicity. You could take your pre-built site and host it anywhere. But as Netlify added more proprietary, server-side features, the line blurred. Building a modern “Jamstack” site on Netlify started to look a lot like just building a “Netlify site,” locking developers into a specific platform.
More Than Just Semantics
This fight over history isn't just about corporate branding; it’s about the soul of the open web. The core tension is between open, interoperable standards and the closed, platform-specific ecosystems that technology companies inevitably build to create a competitive moat. Senior engineers who remember a web before dominant platforms are often wary of any single company defining an entire architectural pattern. When Netlify expanded the definition of Jamstack to include its own server-side products, critics saw it as a classic bait-and-switch: lure developers in with an open, simple standard, then slowly replace the open parts with profitable, proprietary services. The disagreement, therefore, isn’t just about who gets credit for the past, but who gets to control the future of how developers build and deploy websites.
