WordPress, one of the most widely used open-source technologies for building and hosting websites, powers over 40% of the internet. Its flexibility allows users to either host their own WordPress instances or rely on services like Automattic, the company behind WordPress, or third-party providers like WP Engine.
However, a major controversy has erupted between WordPress founder Matt Mullenweg, who also leads Automattic, and WP Engine, sparking a legal and public dispute that has shaken the WordPress ecosystem.
The Dispute
The conflict began in mid-September 2024, when Mullenweg published a blog post harshly criticizing WP Engine, a company that hosts websites built on WordPress. He accused WP Engine of disabling a key feature that tracks revision history for posts, something he considers central to WordPress’ promise of safeguarding user data. He alleged WP Engine disables this to cut costs. Mullenweg also took aim at WP Engine’s investor, Silver Lake, accusing them of not contributing to the open-source WordPress project, and criticized WP Engine for using the “WP” brand, arguing it confuses users into thinking it is officially part of WordPress.
Legal Battle Heats Up
In response, WP Engine issued a cease-and-desist letter, demanding that Mullenweg retract his statements and arguing that their use of the WordPress trademark falls under fair use. WP Engine also alleged that Mullenweg had threatened a “scorched earth” approach unless they paid a substantial portion of their revenues for a trademark license.
Automattic quickly countered with its own cease-and-desist letter, accusing WP Engine of violating WordPress and WooCommerce trademark policies. The WordPress Foundation even updated its trademark policy to address the issue, specifically calling out WP Engine’s use of “WP” and its potential to confuse users into believing the company is affiliated with WordPress.
Ban and Fallout
The conflict escalated when Mullenweg blocked WP Engine’s access to WordPress.org resources, preventing WP Engine customers from updating plug-ins and themes—a move that left many websites vulnerable to cybersecurity threats and upset small businesses relying on these services. This decision provoked backlash within the WordPress community, leading WP Engine to accuse Mullenweg of abusing his power to interfere with their operations.
While the ban was temporarily lifted on September 27, allowing WP Engine access until October 1, the damage to the community and trust in WordPress governance had already been done. WP Engine responded by adjusting its website, removing any mention of WordPress-affiliated terms, and renaming its plans to avoid further trademark disputes.
Community Concerns and Lawsuit
The controversy has sent ripples through the WordPress community. Many developers are now concerned about potential overreach by Automattic, particularly if WordPress trademarks such as “Managed WordPress” and “Hosted WordPress” are granted, which could impose additional restrictions on companies offering WordPress-related services. Some fear that reliance on WordPress might be risky, given how quickly access to resources can be revoked.
Notable figures in the tech world, like Ghost’s founder John O’Nolan and Ruby on Rails creator David Heinemeier Hansson, criticized Mullenweg’s handling of the situation, raising concerns about centralizing control over such a significant portion of the web.
On October 3, WP Engine escalated the situation further by filing a lawsuit against Automattic and Mullenweg, accusing them of abuse of power and violating open-source principles. WP Engine claims that Mullenweg’s actions have jeopardized trust in the WordPress ecosystem. In response, Automattic dismissed the lawsuit as meritless, with their legal team stating they were confident the case would not hold up in court.
Organizational Shifts and Aftermath
The controversy has also led to significant internal changes at Automattic. On October 3, 159 employees, most from the company’s WordPress division, resigned in protest over Mullenweg’s leadership, taking severance packages. This marked a substantial shift in the company, particularly after former executive director Josepha Haden Chomphosy also departed. The following week, Mary Hubbard, previously head of governance at TikTok U.S., was announced as her replacement.
While WP Engine has deployed its own solution to address the plug-in and theme update issues, the broader WordPress community continues to grapple with the fallout. Developers are calling for clearer guidelines on the use of WordPress trademarks, and many fear that this dispute may lead to stricter controls on WordPress-based businesses in the future.
