The Guy Who Built DevOps's Backbone - and Won't Let It Stay Broken
Adam Jacob does not fit the Silicon Valley origin story. No Stanford dorm room. No YC cohort. No wealthy family with connections. He is a self-taught systems administrator who learned networking from bulletin boards as a kid, paid long-distance fees out of his own allowance to access FidoNet, and eventually ran ISPs before writing a single line of what would become one of the most important open-source tools in DevOps history.
That tool was Chef. And the company around it, Opscode, was co-founded by Jacob in 2008 with a single obsession: automate infrastructure completely, repeatably, and at scale. By the time Progress Software acquired Chef in 2020 for $220 million, Jacob had already left to start something new. That is not a red flag. That is the pattern.
Today he is CEO and co-founder of System Initiative, a company built on a genuinely contrarian idea: Infrastructure as Code - the thing Jacob helped popularize - is still fundamentally broken. His answer is not another YAML file. It is a visual, simulation-based platform that models infrastructure like a digital twin, letting teams draw connections between components, catch configuration flaws before deployment, and actually collaborate instead of just hoping culture changes on its own.
The idea that you are going to change your culture toward a more collaborative approach without the tooling forcing a more collaborative approach - was lies. The tooling must push you together, because individual people won't do it alone.
- Adam JacobThis is the through-line of everything Jacob builds: technology and culture are not separate problems. They are the same problem wearing different clothes. You cannot fix one without the other. And if your tools do not structurally enforce collaboration, no amount of DevOps workshops will close the gap.
Jacob grew up with the kind of obsession that precedes great careers. As a teenager, he built a bulletin board that could reboot into Linux so his friends could use his ISP account and get internet access. He used his allowance to keep the FidoNet connection alive. He ran ISPs. He spent over a decade as a systems administrator before founding HJK Solutions, where he built automated infrastructure for 15 different startups over two years - the crash course that produced Chef.
Building the Tools That Defined a Movement
When Jacob co-founded Opscode in 2008 with a $2.5 million seed round from DFJ, infrastructure automation was still a craft skill. Most teams hand-configured servers. Repeatability was aspirational. Scaling was painful. Chef changed that by treating infrastructure as code - version-controlled, tested, deployed like software.
The original Chef was written by Jacob. So was InSpec, the compliance testing framework that lets teams define security policy in human-readable code. So was Habitat, the application packaging tool that made Chef relevant in the container era. Three major open-source projects, one author, over a decade of iteration. That is not a portfolio. That is a worldview expressed in code.
Chef became the backbone of DevOps at companies like Facebook, Bloomberg, and Nordstrom. It helped establish a vocabulary - cookbooks, recipes, nodes, roles - that shaped how an entire generation of engineers thought about infrastructure. When the DevOps movement needed proof that automation worked at scale, Chef was Exhibit A.
Jacob left the CTO role in 2019. Not because Chef failed - it was acquired for $220 million the following year. He left because he saw something the market had not admitted yet: the movement he helped build was stuck. The tools were better, but the gap between DevOps aspiration and DevOps reality was still enormous. He wanted to do something about it.
From Bulletin Boards to Digital Twins
What Comes After Infrastructure as Code
The thesis of System Initiative is uncomfortable for anyone who spent the last decade building IaC pipelines: the whole model is wrong. Not the intent - the intent was always right. The intent was collaborative infrastructure management that moves fast and breaks nothing. The execution - files, state, drift, manual coordination, the gap between the human model and what actually runs - that execution has been failing for years.
System Initiative's answer is a platform built on digital twins. Rather than writing configuration files that describe what you want, you build a visual model of your infrastructure where components are connected graphically. The system simulates changes before applying them. It can detect configuration errors automatically. And crucially, it is designed so that the tooling itself enforces collaboration, not just enables it.
The company raised $3 million in seed funding from Amplify Partners (with participation from Storm Ventures and Battery Ventures), followed by a $15 million Series A from Scale Venture Partners in 2023. Total funding reached $24.2 million by 2025. The backing is credible. The problem is real. The team - Jacob, Mahir Lupinacci, and Alex Ethier - has built in this space before.
Our aspirations in the DevOps movement were right, but too many of us are stuck, not achieving those goals. And now we're kind of at risk of having those aspirations fade, and becoming a thing that sounded good, but was just hype.
- Adam JacobIn February 2025, Jacob presented "The Future is a Hypergraph" - a framework for thinking about infrastructure relationships that goes beyond the tree structures most tools assume. It is the kind of conceptual work that precedes a category shift. Whether System Initiative becomes the standard is still an open question. But the question it is asking is the right one.
What He Has Actually Done
The Lore of Adam Jacob
Tools influence culture, and culture influences tools.
- On the DevOps feedback loopFor me, that's one of the reasons I started building great tools for systems people. Because I just - that was always bullshit. It remains bullshit today.
- On the hierarchy between ops and devLeaders need to realize that implementing DevOps means changing the technology system as well as the cultural system. They must acknowledge that both are intertwined and, to be successful, both systems must evolve to drive velocity.
- Adam Jacob on DevOps leadership