In a sudden shakeup that has sent shockwaves across the web development industry, Automattic has placed co-founder and long-time chief executive officer Matt Mullenweg on paid administrative leave. The decision, executed by the company board of directors, effectively strips Mullenweg of his day-to-day operational control at the commercial helm of WordPress.
The move marks a historic rupture for an organization long identified almost entirely with its vocal founder. While Automattic manages critical commercial infrastructure, Mullenweg also sits at the center of the broader open-source project that powers over forty percent of the web. This sudden intervention by investors and directors represents the most significant corporate governance crisis in the history of Automattic.
Breaking Down Matt Mullenweg’s Ouster at Automattic
Automattic board members took formal action to sideline Mullenweg following months of rising internal friction and external legal chaos. The decision to place him on leave stops short of a permanent termination on paper, but in corporate terms, it functions as a clear removal from the steering wheel.
A few core details define the current situation:
- The board placed Mullenweg on paid leave, removing his executive decision-making authority over Automattic operations.
- The move follows intense pressure regarding corporate stability, executive conduct, and ongoing litigation.
- An interim leadership arrangement is taking shape to stabilize relations with corporate partners and reassure commercial clients.
- The decision directly challenges Mullenweg’s dual position as both a commercial software executive and the primary steward of the open-source platform.
The intervention signals that major stakeholders felt compelled to step in after standard internal reviews failed to de-escalate ongoing tensions. By benching Mullenweg, the board is seeking an immediate firewall between Automattic business operations and the personal battles of its founder.
The Backdrop: Public Feuds, WP Engine, and Escalating Turmoil
This boardroom action did not happen in a vacuum. It follows months of bitter, high-profile conflicts that culminated in a full-scale legal war between Automattic and managed hosting giant WP Engine.
What began as disputes over open-source contributions and trademark usage rapidly devolved into public broadsides, lawsuits, and retaliatory technical measures. The situation escalated dramatically when access to WordPress.org resources was disrupted for external platforms, drawing sharp condemnation from developers who rely on open web infrastructure.
The aggressive strategy triggered unprecedented pushback:
- WP Engine initiated federal legal action alleging extortion, unfair competition, and intentional interference with contractual relations.
- Internal employees voiced intense frustration, leading to high-profile buyouts and waves of resignations among staff who disagreed with the executive strategy.
- Enterprise customers, agencies, and independent creators began questioning the operational safety and reliability of relying on Automattic services.
For major investment groups backing Automattic, the prolonged feud created significant enterprise liability and reputational damage. The legal battle exposed corporate vulnerabilities and caused deep alarm among institutional partners who preferred calm market stability over high-stakes ecosystem warfare.
Inside the Conspiracy Claims: Mullenweg Speaks Out
Rather than stepping aside quietly, Mullenweg has openly pushed back against the board decision. In public statements and communications, he framed his removal not as a standard governance correction, but as a coordinated internal conspiracy.
Mullenweg claims that a faction of investors, working alongside internal actors, orchestrated a quiet campaign to seize control of the open-source platform. According to his account, outside financial interests have long wanted to monetize aspects of the software that were deliberately kept free, open, and governed by community norms.
In his defense, Mullenweg argued that his aggressive actions against commercial competitors were designed to protect the integrity of the ecosystem. He contends that outside investors are prioritizing short-term financial returns and enterprise margins over the long-term health of the open-source mission. The claims have divided observers, leaving some developers sympathetic to his preservationist message, while others view the allegations as a distraction from genuine governance failures.
What This Leadership Shakeup Means for the WordPress Community
The sudden absence of Mullenweg creates a major leadership vacuum at the center of the WordPress universe. For more than two decades, the line between the non-profit WordPress Foundation, the commercial operations of Automattic, and the open-source WordPress.org repository remained blurry, largely because Mullenweg held ultimate authority across all three.
The community now faces critical questions regarding stability and future direction:
- Developer trust: Engineers and agency owners want clear guarantees that open-source code repositories, plugin directories, and core infrastructure will remain free from political or commercial retaliation.
- Governance reform: The split between Automattic corporate interests and the open-source WordPress.org asset will likely require strict structural separation and formal legal boundaries.
- Legal resolution: Sidelining Mullenweg opens the door for potential settlements in the costly litigation with WP Engine and other aggrieved ecosystem partners.
- Foundation autonomy: Contributors are pushing for independent board oversight at the non-profit level to ensure that commercial investors cannot unilaterally dictate the trajectory of open web tools.
For thousands of businesses built on this software ecosystem, the priority is continuity. While the corporate fight inside Automattic is far from over, the board decisive move proves that institutional stakeholders are finally willing to step in when the stability of the platform is on the line.
