The Verge has reported that Matt Mullenweg, CEO of Automattic — the company behind WordPress.com — has been placed on paid leave, a development first surfaced by 404 Media. According to an internal message cited by The Verge, Mullenweg himself described the situation in pointed terms, alleging that Automattic's chief financial officer Mark Davies conspired with board members to engineer the move against him.
To understand why this matters, it helps to understand what Mullenweg represents within the web infrastructure world — and how unusual his position has always been. Automattic is the commercial entity he co-founded, but Mullenweg has also long served as the steward of WordPress itself, the open-source content management system that by most estimates powers a significant share of all websites on the internet. That dual role — part corporate executive, part guardian of an open-source commons — has always created tension, and that tension became dramatically public in the months leading up to this development.
Mullenweg had been at the center of a prolonged and increasingly bitter public dispute with WP Engine, a major managed WordPress hosting company. He had argued, loudly and persistently, that WP Engine was profiting from the WordPress ecosystem without contributing sufficiently back to it. The conflict escalated well beyond a philosophical disagreement about open-source stewardship. Mullenweg moved to block WP Engine's access to WordPress.org resources, a significant practical blow to a business whose entire product rests on the WordPress foundation. Legal filings followed. The dispute drew in developers, plugin maintainers, and longtime members of the WordPress community, many of whom felt caught between two powerful forces both claiming to act in the project's best interests. Others were simply alarmed by what looked like one man using control of a nominally community-owned infrastructure as a weapon in a commercial dispute.
That backdrop is essential context here. A CEO placed on leave by a board is not, on its face, a shocking event in the technology industry. Boards remove or sideline executives regularly. What makes this particular situation unusual is that Mullenweg's authority was never purely corporate. His influence over WordPress — the open-source project, not just the Automattic business — flows from his role as the project's founding developer and its self-appointed lead. Automattic the company and WordPress the project are legally and structurally separate, but in practice Mullenweg has long functioned as the connective tissue between them. Removing him from the Automattic executive chair does not automatically remove him from his position atop the open-source project, which means the governance questions raised by this episode are considerably more complicated than a standard CEO transition would be.
The internal message Mullenweg appears to have sent, as reported by The Verge and 404 Media, is itself telling. Characterizing his own CFO and board members as having conspired against him is the language of someone who did not see this coming through normal channels, or who wants that perception to be on record. It suggests — and this is reasoning rather than reported fact — that whatever disagreements had been building inside Automattic had not been resolved through the usual executive back-and-forth before they reached a formal, structural conclusion. Whether that reflects a board that moved decisively or a CEO who had become difficult to manage through conventional means is something only those inside the company are positioned to know.
The consequences will ripple in several directions. For Automattic's employees and commercial operations, a leadership vacuum at the top of a privately held company of that scale is disorienting, particularly when the departure is contested rather than planned. For the broader WordPress ecosystem — the developers, agencies, hosting companies, and publishers whose livelihoods depend on the platform — the more pressing question is what happens to the open-source project's governance. If Mullenweg retains his role as WordPress project lead while on leave from Automattic, the already strained separation between the two entities becomes even harder to parse. If the board has ambitions to rationalize that structure, they will encounter significant resistance from a community that has always been skeptical of Automattic's influence over ostensibly shared infrastructure.
For WP Engine and others who clashed with Mullenweg, there may be a temptation to read this as vindication, or at least as an opening. The legal and commercial disputes that were underway do not resolve themselves because one party's CEO has been sidelined, but the tone and direction of any eventual settlement could shift considerably depending on who holds authority at Automattic going forward.
The immediate things to watch are whether Automattic names an interim executive and how quickly, whether Mullenweg responds further and in what forum, and perhaps most consequentially, whether the WordPress project's own governance structures begin to move. The community has long debated whether too much power was concentrated in a single individual. That debate is unlikely to remain abstract for much longer.
