Deep Dive: Automattic's Board Forces CEO Matt Mullenweg on Mandatory Leave

Overview

Automattic, the parent company behind the open-source content management system WordPress, has experienced a major leadership upheaval: the board of directors has forced founder and CEO Matt Mullenweg into a mandatory leave of absence.

Notably, Mullenweg stated in the company's internal Slack that this decision was made against his will. This is not a routine executive transition — it represents a substantive power struggle between the board and the company's founder.

As the central figure in the WordPress ecosystem, Mullenweg has embodied both the technical idealism of the project and the driving force behind its commercial decisions. The board's forceful move to sideline him marks a rare and public fracture in Automattic's governance.

The Relationship Between Automattic and WordPress

Understanding this event requires some background on Automattic's unique position in the open-source world. WordPress itself is an open-source project whose trademark is held by the non-profit WordPress Foundation. Automattic is a private company that builds commercial services around WordPress, operating products such as WordPress.com, WooCommerce, Jetpack, and Tumblr.

Matt Mullenweg is both the co-founder of WordPress and the founder and CEO of Automattic. This dual role — simultaneously serving as open-source community leader and commercial chief — has long been a sensitive governance point in the WordPress ecosystem. The highly concentrated power structure once provided unified direction for the project, but it also sowed the seeds of potential governance risk.

The Deep-Rooted Conflicts Behind the Power Struggle

The rift between the board and Mullenweg didn't emerge in a vacuum. His recent and highly contentious conflict with managed hosting provider WP Engine had already pushed the WordPress community into a state of significant tension.

Disputes over trademark usage, responsibilities around open-source contributions, and the distribution of commercial benefits triggered a serious crisis of trust within the community. Some developers publicly questioned Mullenweg's unilateral, hardline decision-making, arguing that his personal will had come to dominate over the open-source community's collective governance.

Against this backdrop, the board's decision to force the CEO on leave can be read as a corporate-level signal to cool tensions and reassert governance authority. When a founder's individual actions begin to threaten the company's overall reputation and business operations, the board activates its checks-and-balances mechanisms.

Implications for Open-Source Governance

This incident highlights a core dilemma in the commercialization of open source: how to strike a balance between the "benevolent dictator" model and modern corporate governance.

Many successful open-source projects relied early on in their history upon a founder's strong leadership to drive technical direction. But when a project evolves into critical infrastructure affecting millions of websites and involving substantial commercial interests, overly concentrated power can itself become a source of instability. Automattic's board stepping in represents a corporate governance structure attempting to correct for an overreach of founder power.

For the broader open-source ecosystem, this event offers a thought-provoking case study:

• The necessity of checks and balances: Even founders must face board oversight and accountability
• The fragility of community trust: A personalized decision-making style can erode the trust a community has built up over years, especially during controversy
• The tension between commerce and open source: Blurred boundaries between a for-profit company and an open-source project can give rise to structural conflict

What to Watch Next

Automattic has yet to release further public details about operational arrangements during Mullenweg's leave or any upcoming changes to its governance structure. Mullenweg's statement via Slack that the decision was made "against his will" suggests this turbulence may not be over.

For the millions of website operators, developers, and business partners who depend on the WordPress ecosystem, the stability of Automattic's leadership is critical. How the board will reshape its governance structure — and whether Mullenweg will return, and in what capacity — are key questions worth watching closely.

This is not merely a high-level personnel change at a single company. It may well become an important window through which to observe the evolving governance models of open-source commercialization.