
Matt Mullenweg Placed on Leave as Automattic CEO
Automattic CEO Matt Mullenweg has been placed on paid leave amid an alleged board dispute. Here's what we know about the WordPress leadership shake-up.
Matt Mullenweg Placed on Leave as Automattic CEO
Matt Mullenweg Placed on Leave from Automattic
Automattic, the company behind WordPress.com and one of the most influential forces in the global web publishing industry, has placed its chief executive officer Matt Mullenweg on a paid leave of absence. The development, first reported by 404 Media and later confirmed by The Verge, marks a significant rupture at the top of a company whose software underpins roughly 43 percent of all websites on the internet, according to data tracked by W3Techs.
The Matt Mullenweg leave of absence arrives without a formal public statement from Automattic explaining the circumstances or timeline. What is known comes primarily from an internal message Mullenweg himself reportedly sent to company staff, in which he characterized the situation in pointed terms. The company has not publicly disputed the existence of that message or the leave arrangement.
Paid leaves of absence at the executive level are rarely routine administrative decisions. When a sitting CEO — particularly a co-founder — is placed on leave by a board, it typically signals either a formal internal investigation, an irreconcilable governance conflict, or a negotiated pause ahead of a larger structural change. The specific circumstances at Automattic remain publicly unclear, though Mullenweg's own account provides a partial picture.
Mullenweg's Allegations Against CFO and Board
According to the internal message reported by 404 Media, Mullenweg did not accept the leave quietly. In the communication to employees, he alleged that Automattic's chief financial officer, Mark Davies, had "conspired" with board members to orchestrate his removal from day-to-day leadership. The framing is notable: a sitting CEO characterizing a board action as a conspiracy rather than a governance decision is unusual, and it suggests the leave did not come through a negotiated or amicable process.
The quote attributed to Mullenweg — "They voted to put me on a paid" — trails off in the reported summary, leaving the full context of his message incomplete. What the fragment does confirm is that a formal board vote took place, and that Mullenweg was aware of it and chose to address it directly with employees rather than accept the standard corporate posture of silence.
Allegations of boardroom maneuvering against a founder-CEO are serious. They can damage internal morale, unsettle investors, and — particularly for a company as embedded in open-source infrastructure as Automattic — create uncertainty among the thousands of plugin developers, theme designers, and hosting partners who depend on its stability. At this stage, the claims are Mullenweg's alone; neither Davies nor the Automattic board has offered a public response to the characterization.
Who Is Matt Mullenweg and Why This Matters
Matt Mullenweg co-created WordPress in 2003, when he was nineteen years old. The project grew from a fork of b2/cafelog into the most widely adopted content management system in the world. Automattic, the company he founded to build commercial products around WordPress, now employs more than 1,700 people across roughly 100 countries and operates a portfolio that includes WordPress.com, WooCommerce, Tumblr, Jetpack, and Akismet, among other properties.
Because Mullenweg serves simultaneously as CEO of Automattic and as a leading steward of the WordPress open-source project — through his position with the WordPress Foundation and his role as lead developer — his influence extends far beyond any single company. His removal, even temporarily, from executive leadership raises questions that affect not just Automattic shareholders but the broader ecosystem of developers and publishers who rely on WordPress as a neutral, foundation-backed platform.
That dual role has also been a source of ongoing controversy. Over the past year, Mullenweg engaged in a highly public and at times acrimonious dispute with WP Engine, a major WordPress hosting provider, over licensing fees and the use of the WordPress trademark. The conflict drew wide attention in the open-source community and prompted debate about whether Mullenweg was exercising his influence over the WordPress project in ways that benefited Automattic commercially. Whether that dispute contributed to the current board action is not established by the reporting, but the backdrop is difficult to ignore.
Implications for WordPress and the Open-Source Ecosystem
WordPress runs on hundreds of millions of websites. Its plugins marketplace lists more than 60,000 free tools. Its themes, blocks, and Gutenberg editor shape how a significant fraction of the internet presents information to readers. Automattic is not the only steward of this ecosystem, but it is the largest commercial stakeholder, and Mullenweg has been its most visible and authoritative voice.
Leadership instability at Automattic does not automatically translate into instability for WordPress.org, which operates as a separate open-source project. The WordPress Foundation holds the trademarks, and the codebase has hundreds of contributors. Still, the practical reality is that Mullenweg's personal authority has long blurred the line between the two entities. Decisions about core software direction, trademark enforcement, and community governance have frequently reflected his individual judgment.
A sustained Matt Mullenweg leave of absence — or a permanent departure — would force the WordPress ecosystem to confront questions about succession and decentralization it has largely deferred. Who speaks for WordPress in disputes with commercial hosts? Who arbitrates conflicts within the contributor community? These are not hypothetical concerns. They are governance gaps that become immediately visible when a founder-leader steps back.
Corporate Governance and Founder-Led Companies Under Pressure
The tension between visionary founders and the boards they ultimately answer to is not new, and Automattic is not the first high-profile case. In 2022, Twitter's board forced out Parag Agrawal after Elon Musk's acquisition process created irreconcilable uncertainty — a transaction that itself reflected the difficulty of separating a platform's identity from the will of its dominant personality. Earlier, WeWork's board removed Adam Neumann as CEO in 2019 following governance concerns and a failed IPO attempt, illustrating how quickly a board can move against even an iconic founder when confidence collapses.
Corporate governance experts have long pointed to founder-led companies as structurally prone to these conflicts. Founders often hold disproportionate voting rights, cultivate deep loyalty among employees, and resist the kind of institutional oversight that professional managers accept as standard. When a board does move against a founder, it usually requires months of deliberation and a coalition of investors who conclude that the risks of inaction outweigh the costs of confrontation.
The fact that Mullenweg's leave is reportedly paid suggests the board is not yet treating this as a termination. Paid administrative leave in a corporate context typically preserves legal options on both sides — it avoids the triggers that an immediate firing might create under employment contracts while allowing the organization to function without the executive in question. That framing, however, can change rapidly depending on what any internal review finds.
For the open-source community specifically, this moment carries a particular weight. Governance analysts who study foundation-backed software projects have noted that the informal authority of a founding technologist rarely survives institutional challenge intact. Once a board demonstrates it can override a founder, the founder's practical power diminishes even if they eventually return to their role.
What Happens Next for Automattic
As of the reporting by The Verge and 404 Media, there is no named interim CEO and no disclosed timeline for the leave. Automattic has not announced a succession plan, and no independent board statement has addressed Mullenweg's allegations against Davies.
The coming weeks will likely clarify several things. If Automattic moves to install an interim executive, it would signal that the leave is expected to be extended or that a formal transition is underway. If Mullenweg returns quickly and without further public conflict, the episode may be contained — though the internal message he reportedly sent will make full reconciliation with the board difficult to stage convincingly.
For the 1,700-plus employees spread across dozens of time zones, the uncertainty is acutely uncomfortable. Automattic has operated with an unusually distributed, trust-based culture, and its leadership transitions have historically been quiet. A board vote against the founding CEO, followed by the CEO's public allegations against the CFO, is not a quiet transition.
WordPress is not going anywhere. The software will continue to run. Plugins will still function. WooCommerce stores will still process transactions. But the question of who steers Automattic — and by extension, who holds informal authority over the most-used CMS on the planet — is now openly in dispute. That is a question the technology industry, and the millions of businesses that depend on WordPress, will watch closely in the weeks ahead.
Source: [The Verge](https://www.theverge.com/tech/993022/wordpress-automattic-ceo-matt-mullenweg-leave-of-absence)
Related Stories
Jensen Huang: Why Nvidia Will Grow 70% Next Year
TechnologySpirit Airlines Bankruptcy: Google's Data Buy Sparks Panic
Comments
No comments yet. Be the first.