WordPress Wars: What the Automattic Power Struggle Means for the Open Source Web

WordPress Wars: What the Automattic Power Struggle Means for the Open Source Web

Sep 14, 2026 wordpress automattic open source tech leadership web hosting corporate governance matt mullenweg

WordPress Wars: What the Automattic Power Struggle Means for the Open Source Web

The internet rarely sees corporate drama quite like this. Matt Mullenweg, the co-founder of WordPress and CEO of Automattic, appears to have reclaimed control of his company after a board-initiated leave—sending a Slack message to employees declaring "I'm back in control." The reversal, reported by TechCrunch, raises uncomfortable questions about corporate governance, founder authority, and the fragile balance between open source ideals and commercial enterprise.

A House Divided

For those unfamiliar with the backstory, Automattic is the commercial entity behind WordPress.com and the primary corporate steward of the WordPress open source project. Mullenweg has long served as the project's "Benevolent Dictator for Life"—a title that sounds tongue-in-cheek but carries real weight in open source governance. The recent board action to place him on leave represented an extraordinary break from that tradition.

What makes this situation particularly fascinating is the philosophical dimension. WordPress is open source software, meaning its code belongs to everyone. Yet Automattic, as the dominant commercial force in the WordPress ecosystem, has sometimes faced criticism for exerting influence disproportionate to its formal authority. When the board moved against Mullenweg, it wasn't just a corporate restructuring—it was a potential fracture in how open source projects navigate commercial interests.

What This Means for Web Hosting

At NameOcean, we watch the WordPress ecosystem closely because so many of our customers depend on it. WordPress powers a substantial portion of the web, from personal blogs to enterprise websites. Turmoil at Automattic doesn't directly affect the open source code itself—WordPress will continue to be developed and released regardless of corporate drama. But the indirect effects could be significant.

Automattic drives much of the investment in WordPress development, contributes to core code, and maintains crucial infrastructure like WordPress.com VIP. If the company's internal struggles create leadership uncertainty, strategic pivots, or talent departures, the broader WordPress ecosystem could feel the ripple effects over time.

The Founder-Board Dynamic

What strikes us most about this situation is its illustration of a tension that plays out across tech companies: the relationship between founders who built something transformative and boards tasked with corporate governance. Founders often carry deep conviction about their product's direction, while boards respond to shareholders and market pressures.

Mullenweg's apparent return suggests the board's intervention was either reversed, reconsidered, or never fully implemented. Automattic has not confirmed the details publicly, leaving the community to parse Slack messages and anonymous sources. This opacity is itself notable—automattic has historically maintained a relatively transparent relationship with its community.

Looking Forward

The WordPress community is resilient. The project has survived previous controversies, forks, and internal debates. Whatever the ultimate resolution of this Automattic drama, WordPress itself will endure because of the thousands of contributors who donate their time and expertise.

However, this episode serves as a reminder that the tools we build our businesses on are never completely separate from the human institutions that maintain them. Whether you're hosting a WordPress site, running a SaaS application, or building the next big platform, governance matters. The people who control an organization shape its priorities, its culture, and eventually its product.

We'll continue monitoring this situation as more information emerges. For now, the WordPress wars provide a masterclass in tech company politics—and a cautionary tale about the complexity of building commercial ventures on open source foundations.


What do you think about the Automattic power struggle? How do you evaluate risk when choosing platforms for your business? Share your thoughts with us.

Read in other languages:

IT HU