By Dan Davies 
Introduction
The WordPress community has been buzzing with controversy over a major dispute between Matt Mullenweg, the co-creator of WordPress and CEO of Automattic, and WP Engine, a popular WordPress hosting provider. Some are now calling it, the WordPress vs WP Engine battle.
What started as a disagreement over trademark usage and contributions to the open-source project has escalated into legal battles, bans, and resignations.
This blog post will break down this ongoing feud, explain the legal and community impacts, and discuss what it means for the future of WordPress and open-source projects.
The WordPress vs WP Engine Legal Battle Begins
In mid-September 2024, Matt Mullenweg publicly criticised WP Engine, calling it a “cancer to WordPress.” He accused the company of:
- Not contributing enough to the WordPress open-source project.
- Misusing the “WP” brand and confusing users into thinking it’s officially associated with WordPress.
- Profiting from WordPress without giving back to the community.
WP Engine responded by sending a cease-and-desist letter to Mullenweg and Automattic, claiming that their use of “WP” was covered under fair use. (Let’s hope Matt doesn’t come after us next!)
Meanwhile, Mullenweg and Automattic:
- Sent their own cease-and-desist letter accusing WP Engine of violating trademark policies
- Updated the WordPress Foundation’s Trademark Policy to reinforce their claims
This dispute quickly escalated into legal action from both sides.
The WP Engine Ban & Its Consequences
One of Mullenweg’s boldest moves was banning WP Engine from accessing WordPress.org resources. This decision:
- Broke many websites by preventing updates to plugins and themes
- Left some open to security vulnerabilities
- Angered the WordPress community, which felt smaller websites were unfairly impacted
WP Engine responded by accusing Mullenweg of abusing his control over WordPress.org to harm their business.
Mullenweg later clarified that the issue was only about trademarks, but the damage to trust within the community was already done.
WP Engine Strikes Back with a Lawsuit
Feeling pressured, WP Engine filed a lawsuit on October 3, 2024, accusing Mullenweg and Automattic of:
- Extortion and abuse of power
- Interfering with their business
- Breaking their commitment to open-source principles
WP Engine stated that Mullenweg’s actions exposed conflicts of interest that could “destroy the trust” in WordPress.
Automattic dismissed the lawsuit as “meritless.”
Automattic Employee Exodus
As tensions grew, 159 employees at Automattic resigned, including key contributors from the WordPress ecosystem division.
- Many left because they disagreed with Mullenweg’s leadership and direction for WordPress
- Automattic later appointed Mary Hubbard (formerly at TikTok) as the new Executive Director of WordPress
This mass resignation signaled deeper issues within Automattic’s governance and decision-making.
How This Affects the WordPress Community
The battle between Automattic and WP Engine (WordPress vs WP Engine) has raised serious concerns for the WordPress open-source community:
1. Unclear Trademark Guidelines
Many developers and businesses are uncertain about how they can legally use “WordPress” branding and whether they could face similar legal issues.
2. Trust Issues with Open Source Governance
Developers worry that relying on open-source projects controlled by commercial entities (like Automattic) could put their own businesses at risk.
3. Potential Trademark Restrictions
The WordPress Foundation has filed to trademark “Managed WordPress” and “Hosted WordPress,” which could restrict third-party hosting companies from using those terms.
Open-source advocates, including Ruby on Rails creator David Heinemeier Hansson, have criticised Automattic’s behavior, arguing that it violates open-source principles.
What’s Next for WordPress?
With ongoing lawsuits and leadership changes, these are some possibilities for the future of WordPress:
- Clarity on trademark usage—Will the WordPress Foundation provide clear rules?
- Stronger community governance—Will power shift away from Automattic to prevent future conflicts?
- Potential WordPress forks—Some developers might create an alternative version of WordPress to escape these disputes.
One key development to watch is Automattic reducing its contributions to WordPress’s “Five for the Future” project in response to WP Engine’s smaller contributions.
FAQs
What is the dispute between WordPress and WP Engine about?
The dispute centers around WP Engine’s use of the “WP” brand, their contributions (or lack thereof) to WordPress, and trademark issues. It has led to legal battles, bans, and community turmoil which many are now labelling as WordPress vs WP Engine.
Did WP Engine break WordPress rules?
WP Engine claims its use of “WP” falls under fair use, but Mullenweg and Automattic argue it confuses users. The issue is now being fought in court.
Why did Automattic ban WP Engine from WordPress.org?
Mullenweg restricted WP Engine’s access to WordPress.org’s plugin and theme updates, affecting many websites. Critics say it was an unfair power move.
Is the WordPress open-source community at risk?
Many believe the conflict challenges the trust in WordPress governance and open-source software. Some developers fear tighter control from Automattic.
What is WP Odyssey?
WP Odyssey is a resource for staying updated on WordPress trends, plugins, hosting solutions, and controversies like this one.
How does WP Odyssey cover WordPress news?
We provide detailed breakdowns of major WordPress updates, business disputes, and open-source governance issues, helping developers and businesses stay informed.
Where can I get unbiased WordPress news?
Follow WP Odyssey for accurate, unbiased insights into WordPress developments, hosting conflicts, and best practices.
Final Thoughts
The WordPress vs. WP Engine battle is more than just a legal fight—it raises serious questions about open-source governance, trademarks, and community trust.
As this controversy unfolds, WordPress users, developers, and business owners must stay informed to protect their websites and businesses.
What are your thoughts on this conflict? Share in the comments! 🚀