The ongoing legal and ideological conflict between Automattic (the company behind WordPress.com) and WP Engine has escalated into one of the most significant disputes in the WordPress ecosystem. At the center of this controversy is Matt Mullenweg, co-founder of WordPress and CEO of Automattic, who has publicly criticized WP Engine, calling it a “cancer to WordPress” and urging the community to switch providers (TechCrunch).
Background: The Roots of the Conflict
The dispute traces back to Automattic’s allegations that WP Engine was infringing upon WordPress trademarks and not contributing adequately to the open-source project. In response, Automattic demanded that WP Engine pay an 8% royalty fee, equating to approximately $10 million annually, for the use of WordPress.org resources and branding (Medium).
Mullenweg’s criticism intensified when he accused WP Engine of exploiting the WordPress brand without contributing to its development, labeling the company a “cancer to WordPress” and urging users to migrate to other hosting providers (TechCrunch).
Legal Battles: WP Engine’s Lawsuit
In October 2024, WP Engine filed a federal lawsuit against Automattic and Mullenweg, alleging extortion, abuse of power, and trademark infringement. The lawsuit claims that Automattic’s actions, including cutting off WP Engine’s access to WordPress.org resources and taking over a popular WP Engine plugin, were detrimental to both WP Engine and the broader WordPress community (The Verge).
Automattic has denied these allegations, asserting that WP Engine was profiting from WordPress without contributing to its development. The legal proceedings are ongoing, with a court hearing scheduled for March 2026 (The Verge).
Community Impact and Internal Turmoil
The dispute has led to significant internal and community repercussions. In response to the escalating tensions, 159 employees left Automattic, with nearly 80% of them working in the WordPress division. This exodus reflects internal disagreements over Mullenweg’s approach to the conflict (BE3Designs).
Additionally, a proposed class-action lawsuit has been filed, accusing Mullenweg and Automattic of abusing their control over the WordPress ecosystem to harm WP Engine and its customers (Silicon Prairie News).
Looking Ahead: The Future of WordPress
The outcome of this conflict could have lasting implications for the WordPress ecosystem. WP Engine’s lawsuit seeks to restore its access to WordPress resources and return control of its plugin, which Automattic took over. The court’s decision in March 2026 will likely set a precedent for how third-party companies interact with the WordPress project and its governing entities (The Verge).
As the legal proceedings unfold, the WordPress community remains divided, with some supporting Mullenweg’s vision for the project’s future and others advocating for a more inclusive and collaborative approach. The resolution of this conflict will shape the direction of WordPress and its role in the broader open-source landscape.
WP Engine vs. Automattic: Mullenweg’s Strategic Return Shakes Up WordPress — Full Case Studies
The escalating legal and ideological conflict between Automattic (the company behind WordPress.com) and WP Engine has become a pivotal moment in the WordPress ecosystem. At the heart of this dispute is Matt Mullenweg, co-founder of WordPress and CEO of Automattic, whose actions have significantly impacted both companies and the broader community.
Case Study 1: Automattic’s Alleged Abuse of Power
Background: In September 2024, Matt Mullenweg publicly criticized WP Engine, calling it a “cancer to WordPress” and accusing the company of profiting from the open-source project without adequate contribution. This led to Automattic demanding an 8% royalty fee from WP Engine for using WordPress.org resources.
Actions Taken:
- Trademark Enforcement: Automattic alleged that WP Engine was infringing upon WordPress trademarks and demanded licensing fees.
- Resource Restriction: WP Engine-affiliated developers were blocked from updating plugins on WordPress.org, affecting popular plugins like ACF.
Legal Response: WP Engine filed a federal lawsuit against Automattic and Mullenweg, alleging extortion, abuse of power, and trademark infringement. The lawsuit claims that Automattic’s actions harmed both WP Engine and the broader WordPress community.
Case Study 2: WP Engine’s Counterattack and Community Backlash
Background: In response to Automattic’s actions, WP Engine initiated legal proceedings, accusing Mullenweg and Automattic of attempting to monopolize the WordPress ecosystem.
Actions Taken:
- Lawsuit Filing: WP Engine filed a complaint alleging that Automattic and Mullenweg violated the Computer Fraud and Abuse Act by threatening to block access to WordPress.org and demanding licensing fees.
- Community Mobilization: The lawsuit has garnered support from various community members who view Automattic’s actions as detrimental to the open-source nature of WordPress.
Legal Developments: A federal court is considering Automattic’s bid to dismiss most of WP Engine’s lawsuit, following a hearing that probed monopoly claims and Mullenweg’s public attacks on the company.
Case Study 3: Internal Turmoil at Automattic
Background: The ongoing conflict has led to significant internal repercussions at Automattic.
Actions Taken:
- Employee Buyouts: In October 2024, Mullenweg offered employees a buyout package, providing $30,000 or six months’ salary—whichever was greater—for those who voluntarily resigned amid internal disagreements linked to the dispute with WP Engine.
- Subsequent Layoffs: In April 2025, Automattic announced the layoff of 16% of its workforce, equating to approximately 279 employees, citing the need to improve productivity, profitability, and adaptability amidst a competitive market and rapid technological change.
Community Impact: The internal turmoil has raised concerns about the stability and direction of Automattic, with some community members questioning the company’s commitment to the open-source ethos of WordPress.
Case Study 4: Proposed Class Action Lawsuit
Background: A proposed class action lawsuit has been filed, accusing Mullenweg and Automattic of abusing their control over the WordPress ecosystem to harm WP Engine and its customers.
Claims:
- Access Disruption: The lawsuit alleges that Mullenweg used his control over WordPress.org to block WP Engine from accessing plugin updates, security patches, and other infrastructure between September 24 and December 10, 2024.
- Customer Harm: The plaintiffs claim that these actions led to disruptions for WP Engine customers, including potential security risks and loss of service reliability.
Legal Proceedings: The court is currently evaluating the merits of the class action, which could have significant implications for how third-party companies interact with the WordPress project and its governing entities.
Conclusion
The conflict between WP Engine and Automattic, spearheaded by Matt Mullenweg, has profound implications for the WordPress ecosystem. As legal proceedings continue, the community watches closely, recognizing that the outcomes will shape the future of WordPress and its open-source principles.