What Mullenweg's Forced Leave Means for WordPress and the Open Source Community
- Introduction about the news
- Background on Automattic and WordPress
- What we know from the Slack message
- Implications for the WordPress ecosystem
- What this means for the broader tech community
- Closing thoughts
In a move that's sent shockwaves through the tech community, Automattic's board of directors has forced CEO Matt Mullenweg into a leave of absence. According to reports, Mullenweg stated in a company Slack message that this action was taken against his will — a remarkable admission that suggests significant internal turmoil at the company that powers approximately 43% of all websites on the internet.
The Man Behind WordPress
For those unfamiliar with the backstory, Matt Mullenweg isn't just a CEO — he's essentially the godfather of modern content management. His creation of WordPress in 2003 revolutionized how we think about publishing on the web. When he founded Automattic in 2005 to commercialize WordPress while keeping the open source project alive, he created a model that many in the tech world admired: a successful business built on and around freely available technology.
This isn't just a story about corporate governance or boardroom drama. This is about what happens when the personal vision behind a transformative technology collides with shareholder interests and institutional pressure.
What's Really at Stake Here
When we talk about WordPress, we're not just talking about a website builder. We're talking about infrastructure. Hospitals use WordPress. News organizations use WordPress. Small businesses, Fortune 500 companies, governments — all rely on WordPress in some capacity. The open source project's governance has always been somewhat unique, with the WordPress Foundation owning the trademark while Mullenweg maintained significant influence over the project's direction through Automattic.
The forced leave raises uncomfortable questions about the power dynamics in open source sustainability. Can a company truly "own" an open source project while maintaining the community trust that makes such projects valuable? What happens when the person who built the brand becomes inconvenient for investors?
The Broader Implications for Tech Leadership
This situation offers a cautionary tale for founders and tech executives building companies around open source technology. The tension between maintaining community trust and satisfying investor expectations is real and ongoing. Automattic has raised significant venture capital over the years, and at some point, those investors expect returns — or at minimum, control.
For startups building on open source foundations, this should serve as a reminder that the terms of your relationship with upstream projects matter. The license might be permissive, but the governance isn't always as neutral as it appears.
What Comes Next
The WordPress ecosystem has weathered storms before, but this one feels different. The fact that Mullenweg himself publicly characterized the leave as involuntary suggests that whatever internal conflict led to this moment has escalated beyond the point of private resolution.
Whether this results in a temporary separation, a permanent departure, or some kind of reconciliation remains to be seen. But one thing is certain: the WordPress community, already dealing with years of debate about Gutenberg, the block editor, and the direction of the project, now faces its greatest uncertainty in recent memory.
At NameOcean, we've always believed that the best technology is technology that empowers everyone to build on the web. Whatever happens with Automattic's leadership, we hope the open source principles that made WordPress great don't get lost in the shuffle.
The internet runs on trust, and right now, a lot of that trust is hanging in the balance.