Automattic CEO Forced on Leave: WordPress Ecosystem Faces Governance Crisis

Overview

Matt Mullenweg, co-founder and CEO of Automattic — the parent company of WordPress.com — has been temporarily suspended by the company's board of directors and placed on paid leave. The news was first reported by tech outlet 404 Media and quickly drew widespread attention across the industry.

As the central figure behind the open-source content management system WordPress, Mullenweg has long served as the spiritual leader and de facto helmsman of the WordPress ecosystem. His sudden departure is more than a routine executive personnel change — it reflects deepening governance tensions within a company that plays a critical role in global internet infrastructure.

Mullenweg's Accusations: A Power Struggle Goes Public

According to internal communications obtained by 404 Media, Mullenweg stated that Automattic CFO Mark Davies and certain board members had "conspired" to put him on leave. He said the board "voted to place me on paid leave" — language that carries a distinctly combative tone.

The choice of words is telling. CEO leave arrangements are typically communicated in neutral, procedural terms. The fact that Mullenweg reached for a loaded word like "conspired" signals that this was not a friendly, negotiated outcome — it looks more like an internal power struggle that has now broken into the open.

Cracks in the Power Structure

When a CFO and board act in concert against a CEO, it usually signals irreconcilable disagreements over finance, strategy, or governance. For a company long dominated by its founder, a breakdown between the board and the founding CEO typically points to deep-seated problems.

Mullenweg is not just any CEO — he is a co-founder with enormous symbolic weight and institutional influence. The fact that the board was able to push through his suspension indicates that other stakeholders, including the CFO and outside directors, have accumulated enough collective power and consensus to check the founder.

Context: A Period of Ongoing Controversy

This event did not occur in a vacuum. Mullenweg and Automattic have been at the center of controversy for some time. Most notably, he was embroiled in a fierce, very public conflict with WordPress hosting provider WP Engine, involving multiple rounds of legal and public-relations battles over trademark usage and open-source contribution obligations. That dispute fractured the WordPress community and drew widespread scrutiny of Mullenweg's leadership style and decision-making.

During that episode, Mullenweg took hardline measures — including restricting WP Engine's access to WordPress.org resources — that triggered significant backlash from developers, contributors, and users. Critics argued that he was placing his personal stance toward one company above the interests of the broader open-source community, and that he was blurring the lines that should clearly separate the WordPress Foundation, WordPress.org, and Automattic as a commercial entity.

Concerns About Governance Transparency

WordPress powers more than 40% of websites worldwide, yet its governance structure has long been heavily dependent on Mullenweg as an individual. WordPress.org is effectively under his personal control, not operated by an independent foundation — a power concentration that may run smoothly in calm times but exposes a dangerous lack of checks and balances when disputes arise. In a sense, this CEO suspension is the result of that governance tension building to a breaking point.

WordPress has long faced a structural governance problem: the boundaries between the WordPress Foundation, WordPress.org, and Automattic have never been genuinely clear. The WordPress Foundation nominally holds the WordPress trademark and promotes the open-source mission, but its actual decision-making authority is highly dependent on Mullenweg personally. WordPress.org — the core platform for software distribution and the plugin/theme repository — is likewise under Mullenweg's effective control, rather than being governed through an independent community process. By contrast, mature open-source governance organizations like the Apache Software Foundation and the Linux Foundation all have independent committees, transparent decision-making processes, and clear conflict-of-interest policies. WordPress's lack of such structures means that conflicts between commercial interests and open-source community interests have become heavily concentrated in Mullenweg as a single individual — and it makes it difficult for outsiders to tell whether any given decision represents the public interest of the open-source community or the commercial interests of Automattic.

The dispute between Automattic and WP Engine escalated publicly in the second half of 2024. WP Engine is a company focused on WordPress hosting services, once valued at over a billion dollars. One core issue was Mullenweg's view that WP Engine was heavily monetizing the WordPress brand while contributing insufficiently to the open-source community — a position he used to justify imposing access restrictions at the WordPress.org level, including blocking WP Engine users from obtaining plugin updates through official channels. Critics described this as weaponizing WordPress.org — a piece of public infrastructure — to settle commercial-level competitive and licensing disputes. Several long-term core contributors publicly criticized these actions, and some left the community entirely. This episode was the first time a large-scale developer community began to seriously question whether open-source ecosystem neutrality could be guaranteed when effective control of WordPress.org rests in the hands of a commercial company's CEO.

Implications for Automattic and the WordPress Ecosystem

A CEO suspension is a major event for any company, and it is particularly sensitive for Automattic. As the parent company of WordPress.com, WooCommerce, Tumblr, and other well-known products, Automattic's stability directly affects the daily operations of countless merchants, developers, and content creators.

In the short term, what the market and community want most to know is who actually holds the reins, and whether ongoing litigation and product strategy will be affected. Paid leave is typically a transitional arrangement — neither an outright removal nor a maintenance of the status quo — which usually suggests the board is still assessing the situation, or buying time and space for further decisions.

For the broader WordPress user community, the deeper concern is this: when a company's governance is so tightly bound to a single founder, any leadership turbulence can ripple through the underlying open-source infrastructure. This has once again sparked discussion about whether WordPress's open-source governance should be fully separated from commercial entities.

Conclusion

Mullenweg's suspension marks a turning point in which Automattic's internal tensions have moved from simmering undercurrents to open confrontation. Whatever the ultimate outcome — whether he returns to his role or departs permanently — this episode will stand as an important case study in founder power, open-source governance, and corporate accountability in the tech industry.

For the millions of website operators who depend on the WordPress ecosystem, the question that truly deserves attention may not be the fate of any particular executive — but whether the open-source system underpinning nearly half the world's websites can build a governance architecture that is more transparent, independent, and sustainable.