Matt Mullenweg says Automattic has “been attempting to make a licensing deal” with WP Engine “for a very long time, and all they have done is string us along”
I've been writing and talking about WP Engine a lot in the last week, but I want to be crystal clear about the core issue at play. In short, WP Engine is violating WordPress' trademarks. Moreover, they have been doing so for years. … X: Matt Mullenweg / @photomatt : I tried to summarize the @wpengine and WordPress issue: https://ma.tt/... @wpengine : Matt Mullenweg, CEO of Automattic, has misused his control of WordPress to interfere with WP Engine customers' access to https://wordpress.org/, asserting that he did so because WP Engine filed litigation against https://wordpress.org/. This simply is not true. Our Cease & Forums: Hacker News : Open Source, Trademarks, and WP Engine
Context & Ripple Effects
This is the licensing-and-trademark rationale offered by Automattic’s co-founder in its dispute with a major WordPress hosting provider. The disagreement quickly moved beyond commercial negotiations when WP Engine’s access to WordPress.org was cut off.
The conflict subsequently entered court through WP Engine’s California lawsuit, while later coverage raised conflict-of-interest concerns around control of WordPress infrastructure. The key issue is whether trademark licensing and access to shared project resources can be treated as separate matters.
First-order effects
- Automattic publicly frames WP Engine as a trademark-license holdout, increasing pressure on WP Engine to rebut the allegation and defend its use of WordPress branding.
- WP Engine customers and partners face a dispute in which the platform’s commercial operator and a major service provider give incompatible accounts of responsibility and access.
Second-order effects
- A licensing dispute can become an operational one when a provider depends on WordPress.org resources, making continuity of updates and support a central customer concern rather than a back-office legal issue.
- Other WordPress businesses may reassess how closely their branding, services, and technical dependencies are tied to project-controlled infrastructure.
Third-order effects
- If this pattern persists, the WordPress ecosystem may face stronger pressure to distinguish neutral open-source project governance from the commercial interests of companies with influence over core infrastructure.
- The court fight could clarify, or leave contested, the limits on using trademark and infrastructure control in disputes with ecosystem businesses.
The trend: This is one data point in a broader struggle over how open-source brands and shared infrastructure are governed when commercial service providers scale around them.