WordPress Power Struggle: What Mullenweg's Leave Means for the Open-Source Ecosystem

In a move that's sent shockwaves through the web development and open-source communities, Matt Mullenweg—the co-founder of WordPress.org and CEO of Automattic—has been placed on a paid leave of absence. The decision, made by Automattic's board, with CFO Mark Davies stepping in as interim CEO, marks one of the most dramatic leadership transitions in the history of the modern web.

According to reports, Mullenweg claims the move was the result of a "conspiracy" involving Davies and board members Ann Dunwoody, Toni Schneider, and Sue Decker. Whether or not that's the full picture, one thing is clear: something significant has broken down in the relationship between Automattic's leadership and its founding visionary.

The Context: A Turbulent Year for WordPress

This leave of absence doesn't exist in a vacuum. 2024 has been an exceptionally contentious year for the WordPress ecosystem. Mullenweg launched what many characterized as a public pressure campaign against WP Engine, a major WordPress hosting provider. The dispute escalated into legal territory and divided the otherwise collaborative open-source community. Critics argued that Mullenweg's approach undermined the very spirit of open-source development that WordPress was built upon.

For those of us who've built businesses, websites, and applications on the WordPress platform, these developments are more than gossip—they're consequential. WordPress powers roughly 43% of all websites on the internet. When there's turbulence at Automattic, the ripples affect millions of site owners, developers, agencies, and hosting providers worldwide.

What This Means for the WordPress Ecosystem

At this point, it's too early to predict long-term outcomes, but several scenarios are worth watching:

1. Leadership Stability Concerns Interim CEO Mark Davies now faces the unenviable task of maintaining operational stability while the company navigates what appears to be significant internal conflict. For customers and partners, this uncertainty can be unsettling.

2. Open-Source Governance Questions WordPress.org remains an open-source project, but Automattic controls significant commercial interests around the platform. This situation highlights a recurring tension in open-source: how do you balance the influence of commercial entities with community governance?

3. Trust and Perception Mullenweg has been the public face of WordPress for nearly two decades. His leadership style—passionate, sometimes aggressive, always opinionated—has shaped the platform's direction. Whether the new leadership will take a different approach remains to be seen.

Lessons for Tech Leaders and Startups

Regardless of your feelings about Mullenweg or the specifics of this situation, there are broader takeaways for anyone building tech companies:

• Succession planning matters: Even indispensable-seeming leaders need transitions plans. Companies that don't prepare for leadership changes do so at their peril.
• Governance structures protect everyone: Clear board structures, defined decision-making processes, and transparent communication channels can prevent situations from becoming crises.
• Open-source isn't immune to business tensions: The idealism of open-source development still operates within the reality of business, funding, and competing interests.

Looking Forward

The WordPress story is far from over. Mullenweg remains on the board, and this may prove to be a temporary pause rather than a permanent departure. What's certain is that the platform—and the ecosystem of developers, hosts, and businesses built around it—will continue to evolve.

For our part, we'll be watching closely. The health of the WordPress ecosystem matters to everyone in web hosting and development. Whatever happens next, the principles that made WordPress successful—openness, accessibility, community—should guide the way forward.

The internet runs on infrastructure we often take for granted. When leadership changes at companies like Automattic, it's a reminder that the tools we depend on are built by people, governed by organizations, and subject to the same human dynamics as any other enterprise.

We'll keep you updated as this story develops.

What are your thoughts on this leadership change? How does it affect your WordPress projects or business? Share your perspective with us.