One Stack Ahead, Always
There is a particular skill Mathias (Matt) Biilmann Christensen has demonstrated twice in a decade: naming the thing everyone is fumbling toward before they realize they need a word for it. In 2016, over beers with a friend, he invented "Jamstack" - JavaScript, APIs, and Markup - and the web development world snapped into focus. In January 2025, he published "Introducing AX: Why Agent Experience Matters," and within twelve months Bessemer Venture Partners, Sequoia Capital, and the first job postings for "AX Specialist" all carried a term he coined on his personal blog.
This is what he does. He watches the edge of the map, builds infrastructure for what is about to be normal, and then names it so everyone else can find it. It is a strange talent for someone who started out reviewing records for Danish public radio.
Today, Biilmann runs Netlify from San Francisco - a company he co-founded in 2014 that now powers more than 35 million websites, has raised $212 million across five funding rounds, and sits at a $2 billion valuation. The platform began as a simple idea: connect a Git repository, deploy a fast, static site, and stop hand-editing files on FTP servers. It has since grown into a full frontend cloud - handling CI/CD, serverless functions, edge logic, A/B testing, visual editing, and now, increasingly, the infrastructure for AI agent workflows.
What makes Netlify's arc unusual is not the funding or the scale. It is that the company's strategy has consistently been five years ahead of market consensus - and its CEO has been the one writing the consensus into existence.
"AI agents are reading your website today. Most companies have never seen the version the agents actually get back. That's the gap that decides whether you're cited or skipped."- Mathias Biilmann Christensen
From Copenhagen Concert Halls to San Francisco Build Systems
Biilmann studied musicology at the University of Copenhagen, with a secondary in comparative literature. Neither discipline is an obvious on-ramp to web infrastructure. But he has repeatedly drawn a line between musical composition and programming - both deal in structure, separation of concerns, and the tension between formal constraint and creative freedom. Composers, he has noted, were the original programmers.
He worked as a freelance music journalist for Danmarks Radio, Denmark's public broadcaster, before pivoting to programming. The pivot was not abrupt - it was gradual, practical, and driven by curiosity. He wrote code for Webactiva and Cre8Buzz, then spent several years as Director of Development and CTO at Domestika, a Spanish creative education platform, running the engineering side of a consumer startup from San Francisco.
Around 2012, he founded Webpop - a hosted CMS startup aimed at agencies building websites for clients. It was organized around a principle that would define everything he built afterward: strict separation between content and design, letting designers work directly in HTML and CSS while content editors worked on top of the live site. This separation - the same idea at the heart of Jamstack - was already forming.
The Jamstack name was born over beers. A friend named Andreas - who works at Uber - suggested naming the new approach the way LAMP stack was named. Biilmann retroactively assigned the letters: JavaScript, APIs, and Markup. The next day he had a naming convention that would reshape an industry.
The Christmas Trip That Built Netlify
In 2013, childhood friend Christian Bach called Biilmann from Denmark. Bach had been diagnosed with Hodgkin's lymphoma. Biilmann flew back for Christmas. Over long conversations during Bach's treatment, two old friends sketched an idea: what if deploying a website was as simple as pushing to Git? No servers to configure. No FTP credentials to lose. Just a repository and a global content delivery network.
BitBalloon - a static file hosting project Biilmann had been running - was the kernel. Netlify was the vision. The company incorporated on January 27, 2014. Christian Bach joined as co-founder and eventually became CCO and CSO. The two Danes from Copenhagen built one of the defining web platforms of the 2010s and 2020s from San Francisco.
Netlify launched publicly on April 7, 2015. The free tier - designed specifically for open-source projects - seeded the developer community that became Netlify's primary growth engine. This was not charity. It was a deliberate community-building strategy: make the best tool free for the people who influence how other developers choose tools.
"Before it was really the most normal workflow for a front-end developer was to FTP into a production server and change code there."- Mathias Biilmann Christensen, on the problem Netlify solved
Jamstack: Naming the Movement, Bigger than the Product
Biilmann launched the term "Jamstack" publicly in 2016, on stage at Smashing Magazine's San Francisco conference. But the move that made it stick was deliberate: he branded Jamstack as a community concept, explicitly wider than Netlify. Anyone could use the term. Competitors could build Jamstack products. The community owned it.
It was a counterintuitive bet for a startup trying to own market share. But Biilmann understood that naming a category is more valuable than owning a trademark. By 2019, Jamstack had its own conference. By 2021, it was the default architecture for millions of professional web projects. Netlify - the company that invented the term for an approach that any platform could support - sat at the center of that ecosystem.
He has also been honest about the complexity that followed. In a 2021 React Summit talk titled "Keeping It Simple," he reflected on how Jamstack's growing sophistication risked reintroducing the same fragmentation and overhead that the original approach had swept away. Defending simplicity, he argued, is an active and ongoing choice - not a configuration you set once.
Netlify Funding History
Agent Experience: The Next Name He Coined
In January 2025, Biilmann published "Introducing AX: Why Agent Experience Matters" on his personal blog. The argument: just as User Experience (UX) defined the design discipline of the 2000s, and Developer Experience (DX) shaped the tooling decisions of the 2010s, Agent Experience (AX) would define the infrastructure choices of the 2020s. AI agents are already users of software. Most software was never designed with them in mind.
Within twelve months, the term appeared in investor memos from Bessemer Venture Partners and Sequoia Capital. Job postings for "AX Specialist" appeared. Biilmann launched agentexperience.ax as an industry resource. Netlify rolled out netlify.ai - its first product built specifically for AI agents rather than human developers, providing context, tools, and onboarding paths for agents learning to build with Netlify.
The Netlify GPT integration - an early proof of the concept - was already generating over 1,000 daily deployments originating from ChatGPT. The data made the case that thoughtful AX design is not philosophical but commercial: agents that understand your product drive measurable business outcomes.
Access
Can an AI agent reach and authenticate with your platform without human handholding?
Context
Does your platform provide the structured information agents need to make good decisions?
Tools
Are the actions agents need to take exposed as clean, reliable, agent-native interfaces?
Orchestration
Can multiple agents collaborate efficiently across your platform's surfaces?
"The largest disruption from the current evolution of AI will come from bringing agency to computers."- Mathias Biilmann Christensen, "Introducing AX: Why Agent Experience Matters," January 2025
The Recurring Theme: Separation of Concerns
There is a single idea that runs through Webpop, Jamstack, and AX: separate the concerns, and each piece becomes easier to build, deploy, and understand. Content from design. Front-end from back-end. Human UX from agent UX. Biilmann returns to this idea the way composers return to a theme - reharmonizing it for each new context.
He has also written about AI from a personal angle that most executives avoid. A February 2026 blog post, "My Bot Got Banned for Being a Bot," describes his personal AI agent triggering a Google account suspension for automating at a pace Google's systems read as malicious. He wrote about it not with frustration but with genuine curiosity: how should platforms distinguish helpful automation from harmful bots? The question has no easy answer. He asked it in public anyway.
His April 2026 post "AI and Ambition" makes a case that gets lost in efficiency-obsessed conversations about AI: the real value is not doing the same things faster, but attempting things that were previously out of reach. Projects that never fit a roadmap. Experiments that required too much overhead to justify. Bolder bets. "Tasks that would never fit a roadmap or a busy schedule suddenly become possible on a whim, from a phone, between things," he wrote.
"When we can really take components apart and have them very isolated from each other, it typically gets easier to work on those components."
"Every product already has an agent experience. The only question is whether that experience is good or bad."
"Tasks that would never fit a roadmap or a busy schedule suddenly become possible on a whim, from a phone, between things."
"Agents will far more frequently be collaborators and extensions of humans, rather than replacements."
Building the Platform Through Acquisition
Between 2021 and 2023, Netlify made five strategic acquisitions that expanded its platform from a deployment tool into a full development lifecycle system. FeaturePeek (Y Combinator-backed, frontend previews), OneGraph (GraphQL API composition), Quirrel (serverless job scheduling), Gatsby (Jamstack framework with a massive developer following), and Stackbit (visual editing for the web). Each acquisition plugged a specific gap in the Netlify workflow, moving the platform closer to the composable architecture vision Biilmann had described years earlier.
The acquisition of Gatsby was particularly notable - Gatsby was, in many ways, a Jamstack competitor. Bringing it under the Netlify umbrella reflected the same logic as the original Jamstack community strategy: make the ecosystem larger, capture more of the value, and grow the category faster than you could grow the company alone.