Automattic's board of directors has forced company CEO Matt Mullenweg into a leave of absence, according to a report by TechCrunch. Mullenweg himself confirmed the move in a message to staff on the company's internal Slack, stating plainly that the decision was made against his will.
To understand why this matters, it helps to understand what Automattic is and who Mullenweg has been within it. Automattic is the commercial entity behind WordPress.com, WooCommerce, Tumblr, and a constellation of other web products. More significantly, Mullenweg is not merely the company's chief executive — he is, in the minds of most people who follow the open-web ecosystem, synonymous with WordPress itself. He co-created the WordPress open-source project in 2003, and for two decades the distinction between the man, the company, and the software has been deliberately blurry. That blurriness has always been both a source of his authority and, as events have demonstrated, a serious governance problem waiting to surface.
The forced leave did not arrive in a vacuum. Mullenweg spent much of the past year embroiled in a very public and increasingly acrimonious dispute with WP Engine, a major WordPress hosting provider. That conflict drew in the WordPress.org infrastructure — which Mullenweg also controls — and raised hard questions about whether one person should simultaneously hold the keys to a nominally community-owned open-source project and run a for-profit company that competes in the same market. The dispute rattled plugin developers, hosting partners, and enterprise customers who had long treated WordPress as neutral infrastructure. When the person who controls the roads also owns one of the trucking companies, the arrangement invites scrutiny, and that scrutiny arrived in volume.
Mullenweg's conduct during that period was striking even by the standards of a famously outspoken founder. He made public statements that many in the WordPress community found coercive, took actions that restricted WP Engine's access to WordPress.org resources, and at moments seemed to be daring stakeholders to push back. Whether one reads that behavior as principled advocacy for the open-source project or as an abuse of a structurally conflicted position largely depends on which side of the commercial WordPress ecosystem one inhabits. What is harder to dispute is that it created significant reputational and legal exposure for Automattic at a time when the company was already navigating a challenging environment for web publishing businesses.
The board's decision to intervene suggests that, whatever tolerance directors had extended to Mullenweg during the WP Engine confrontation, a threshold has now been crossed. Boards rarely move against founding CEOs without extended deliberation, and the fact that Mullenweg felt compelled to tell employees the leave was against his will is itself revealing. It signals that this was not a mutually agreed pause framed as self-care or strategic reflection — it was a removal in all but name, at least for now. The likely reading is that directors concluded the company's interests required putting distance between the institution and its founder, at least temporarily.
The consequences fan out in several directions. For Automattic employees, the immediate effect is uncertainty about leadership and direction at a company where the founder's vision has historically been the only compass that mattered. For the broader WordPress ecosystem — the agencies, developers, and businesses that have built livelihoods on the platform — the situation raises the already-live question of governance: if Mullenweg steps back or is eventually removed, who speaks for WordPress.org, and under what accountability structure? That question has no clean answer today, and the absence of one is itself a vulnerability. For enterprise customers evaluating WordPress as a long-term platform investment, another chapter of visible instability at the top does little to restore confidence.
There is also a legal dimension worth noting. The dispute with WP Engine has involved litigation, and any change in Automattic's leadership posture could affect the trajectory of that conflict. A board that has just demonstrated willingness to restrain its own CEO may also be signaling a desire to manage legal and reputational risk more carefully going forward.
What to watch for next is relatively clear. The first question is whether this leave becomes permanent — whether the board uses the interval to formalize a transition or whether Mullenweg returns, chastened or otherwise. The second is what happens to the governance of WordPress.org itself, the open-source infrastructure that sits formally outside Automattic but has long operated under Mullenweg's personal authority. Any credible resolution to the community's concerns will eventually have to address that structure, not just the corporate one. And the third is whether major ecosystem partners — hosting companies, enterprise clients, plugin developers — treat this moment as the opening to demand structural reforms they have been reluctant to push for while Mullenweg was unchecked. The board has moved. Now everyone else has to decide what to do with that.
