Matt Mullenweg and the History of Public Disputes at Automattic
Matt Mullenweg, the co-founder of WordPress.com and CEO of Automattic, has a long-standing history of engaging in high-profile conflicts with competitors and community members. Rather than relying solely on traditional legal channels, Mullenweg has frequently utilized the "court of public opinion," a strategy he has described as brinksmanship. He has noted that the high costs associated with legal action could potentially place Automattic in a difficult financial position.
These disputes often center on the interpretation of the General Public License (GPL)—the open-source license that governs WordPress—and the boundaries of trademark usage within the web ecosystem.
Key Facts
- Strategic Approach: Mullenweg prefers public disputes over legal battles to avoid high litigation costs.
- Licensing Focus: Many conflicts stem from the GPL, which requires derivative works to remain open source.
- WP Engine Conflict: A major 2024 dispute involving trademark fees, server blocking, and a forced plugin migration.
- Internal Turmoil: Recent leadership tensions led to the disbanding of the WordPress Sustainability team and the departure of over 8% of Automattic's staff.
Early Competitor Conflicts and Licensing Disputes
Mullenweg's tendency to challenge rivals dates back over a decade. In 2008, he labeled a comparison guide published by Six Apart's Movable Type as "desperate and dirty." By 2013, the conflict shifted toward licensing; Mullenweg criticized the marketplace Envato for selling WordPress themes with proprietary CSS and graphics components, leading to a ban on Envato developers speaking at WordPress events.
In 2016, the focus turned to Wix.com. Mullenweg accused the company of using WordPress's mobile text editor code without following GPL terms. Wix's CEO countered that they had open-sourced their version of the component. Eventually, Wix transitioned to a fork of the MIT-licensed text editor, adding a clause to prevent redistribution under other licenses.
More recently, in 2022, Mullenweg publicly criticized GoDaddy, claiming the company failed to reinvest sufficiently into the WordPress project.
The Tumblr Controversy
During a three-month sabbatical starting in February 2024, Mullenweg became embroiled in a personal feud with a transgender Tumblr user. The user had posted a comedic wish for Mullenweg's death following frustrations over Tumblr's handling of transphobic harassment. Mullenweg characterized the post as a death threat, banned the user, and shared the user's private account information publicly.
This response drew sharp criticism from transgender employees at both Tumblr and Automattic. In a staff blog post, they described Mullenweg's actions as "unwarranted and harmful," asserting that the user's post was not a realistic threat of violence.
The WP Engine Legal Battle
One of the most severe disputes began in September 2024, when Mullenweg called for a boycott of WP Engine during WordCamp US 2024. He argued that WP Engine's contributions to WordPress were meager compared to Automattic and criticized its ties to private equity.
Trademark and Financial Allegations
WP Engine responded with a cease and desist, alleging defamation and extortion. They claimed Mullenweg's attacks were motivated by WP Engine's refusal to pay Automattic a trademark licensing fee—specified as 8% of all revenue—which would have also included a clause prohibiting the "forking" (creating a separate version) of the software.
Infrastructure and Plugin Interference
The conflict escalated when WordPress.org blocked WP Engine and its affiliates from accessing essential servers, including security updates and the plugin repository. While access was briefly restored to allow WP Engine to create mirror sites, a further controversy arose regarding the Advanced Custom Fields (ACF) plugin.
WordPress.org replaced the ACF listing with a version called "Secure Custom Fields" (SCF). Because Automattic used the same product slug and update mechanism, millions of users were automatically migrated from the WP Engine-maintained ACF to the Automattic-maintained SCF without warning. This action was described by critics as a supply chain attack and formed the basis of a lawsuit citing the Computer Fraud and Abuse Act (CFAA).
Corporate and Legal Fallout
The internal strain at Automattic resulted in 159 employees (8.4% of the workforce) resigning in exchange for severance packages. Legally, a preliminary injunction was issued on December 10, 2024, ordering Automattic and Mullenweg to stop interfering with WP Engine's access to WordPress.org. Additionally, a class action lawsuit was filed in February 2025 by a WP Engine customer, alleging that the dispute disrupted the security and maintenance of their own websites.
Leadership and Sustainability
Tensions regarding Mullenweg's leadership style peaked on January 9, 2025. Thijs Buijs, a representative of the WordPress Sustainability team, resigned via Slack. Buijs cited a December 2024 Reddit post by Mullenweg titled "What drama should I create in 2025?" as evidence of "unsustainable leadership." In response, Mullenweg disbanded the sustainability team and closed its dedicated Slack channel.
| Opponent/Entity | Primary Issue | Key Outcome/Action |
|---|---|---|
| Wix.com | GPL License Compliance | Wix switched to a modified MIT-licensed editor. |
| Tumblr User | Death threat allegation | User banned; private info shared; staff backlash. |
| WP Engine | Trademarks & Contributions | Lawsuits, server blocking, and forced plugin migration. |
| Sustainability Team | Leadership style | Team disbanded; representative resigned. |
Frequently Asked Questions
What is the GPL and why does it cause disputes?
The General Public License (GPL) is a free software license that requires any software based on GPL code to also be released under the GPL. Disputes arise when companies are accused of using GPL code in proprietary products without releasing their own source code.
What happened with the Advanced Custom Fields (ACF) plugin?
Automattic replaced the ACF plugin on WordPress.org with a version called Secure Custom Fields (SCF). Because they used the same update mechanism, users were automatically switched to the new version without their consent.
Why did Automattic employees resign during the WP Engine dispute?
Approximately 8.4% of the staff resigned after being offered severance packages (either $30,000 or six months of salary) to align the company's stance during the conflict.
What was the court's ruling regarding WP Engine's access to WordPress.org?
On December 10, 2024, a judge issued a preliminary injunction requiring Matt Mullenweg and Automattic to stop blocking or interfering with WP Engine's access to WordPress.org.
How did the WordPress Sustainability team end?
The team was disbanded by Matt Mullenweg after Thijs Buijs resigned, citing concerns over "unsustainable leadership" following a provocative Reddit post by Mullenweg.