Automattic demanded an 8% cut of WP Engine's monthly revenue to use the WordPress trademark in a seven-year deal proposed on September 20; WP Engine declined
Automattic, the parent company of WordPress.com, asked rival hosting service WP Engine to hand over 8 percent of its revenue each month …
Context & Ripple Effects
The proposed license surfaced amid an escalating trademark dispute: Automattic had already sent WP Engine a cease-and-desist over alleged unauthorized WordPress trademark use, while Matt Mullenweg said the companies had discussed licensing for a long time.
The rejected terms put a concrete price on that disagreement. Related coverage then records WP Engine's California lawsuit against Automattic and Mullenweg, making the failed commercial path central to the conflict's legal framing.
First-order effects
- WP Engine declined a seven-year arrangement that would have made an 8% monthly-revenue payment a condition of trademark use, leaving no negotiated license in place.
- Automattic's trademark dispute with a major WordPress host remained unresolved and became less likely to be settled through the disclosed commercial proposal.
Second-order effects
- The disclosed revenue-based term gives both sides a sharper reference point in litigation and public arguments: WP Engine can characterize it as leverage, while Automattic can continue to frame the issue as trademark licensing and enforcement.
- Other businesses built around WordPress branding may face greater uncertainty over where ordinary ecosystem use ends and paid trademark licensing begins, even though this report establishes terms only for WP Engine.
Third-order effects
- If trademark enforcement is increasingly paired with revenue-linked licensing, open-source projects with commercially valuable brands could face deeper tension between broad ecosystem adoption and centralized control of brand rights.
- The dispute also shows how governance conflicts can divert resources from project stewardship: Automattic later said it would reduce WordPress contributions because of the litigation, including a plan to focus mostly on security and critical updates.
The trend: This is one data point in the growing tension between open-source ecosystems' shared infrastructure and the commercial owners' ability to monetize or enforce associated trademarks.