The Official Story: A Revolution in Web Development
The public-facing history of Netlify is a classic startup tale. It begins with Danish co-founder and CEO Matt Biilmann, who, frustrated with the cumbersome, monolithic systems of the early 2010s, envisioned a better way to build websites. His initial
side project, BitBalloon, allowed users to simply drag and drop a website folder to deploy it globally. This idea, refined with co-founder Chris Bach, grew into Netlify, a platform designed to abstract away the complexities of servers and infrastructure. A core part of this story is the 'Jamstack'—a term Biilmann coined for an architectural approach using JavaScript, APIs, and pre-rendered Markup. This wasn't just a technical blueprint; it was a movement. Netlify positioned itself as the pioneer of this faster, more secure, and scalable way to build for the web, raising hundreds of millions in funding and attracting millions of developers to its platform.
The First Point of Disagreement: The 'Jamstack' Label
For many senior engineers, the first point of friction is the term 'Jamstack' itself. The practices it described—decoupling the frontend from the backend and using static site generators—were not new. Developers had been building fast, static sites for years. The disagreement isn't that Netlify invented these techniques, but that it successfully branded and commercialized a pre-existing grassroots movement. Some developers see 'Jamstack' as a brilliant marketing move that gave a scattered community a unifying banner. Others argue it was a co-opting of an ecosystem, reframing it around the company that coined the term. This tension came to a head when Netlify itself began de-emphasizing 'Jamstack' around 2023, favoring the term 'composable architecture' to appeal to large enterprise clients, leading many developers to declare the term 'dead'. Biilmann's counterargument is that the architecture simply won, becoming synonymous with 'modern web development'.
The Second Point: Who Gets the Credit?
Like many startup narratives, the focus often falls on the CEO. Matt Biilmann is widely credited as the visionary coder. However, other accounts emphasize the crucial role of his co-founder, Chris Bach. While Biilmann had the technical insight, it was Bach, with his agency and storytelling background, who saw the potential to create an entirely new category rather than just another hosting platform. Multiple sources credit Bach as a co-originator of the Jamstack concept and a key strategist in building its community and marketing. This isn't to say there's a public feud, but the nuance is often lost. The debate among engineers often circles back to a broader industry issue: tech history tends to lionize the 'hacker' founder, sometimes at the expense of the co-founders who build the business, brand, and market around the code.
Why This 'History War' Matters
These disagreements aren't just about splitting hairs. They tap into a deep cultural vein in the software world concerning authenticity and credit. The debate reflects a tension between opensource ethos and venturebacked commercialization. Was the Jamstack a communitydriven evolution or a marketingled category creation? Can it be both? For senior engineers who were part of the 'staticfirst' movement before Netlify gave it a catchy name, it is a matter of acknowledging the foundational work that made companies like Netlify and Vercel possible. The narrative also affects a companys relationship with its core audience. Developers are famously allergic to being marketed to, and when a companys story feels more like branding than a reflection of reality, it can create a trust deficit. The discussion is less an accusation against Netlify and more a communitys attempt to selfcorrect its own history in real time.
