The WordPress vs. WP Engine Dispute, Explained
The WordPress ecosystem has been roiled by a very public conflict between WordPress co-founder Matt Mullenweg and WP Engine, one of the most prominent WordPress-focused hosting companies. The dispute has escalated from keynote remarks to cease-and-desist letters, trademark accusations, and a WordPress.org ban affecting real users.
For developers and site owners who have watched from the sidelines, the back-and-forth can be hard to follow. Here's a rundown of what has happened and where things stand.
How It Started: WordCamp US 2024
At WordCamp US in Portland, OR on September 20, 2024, Mullenweg used his keynote to take direct aim at WP Engine. His central claim: WP Engine doesn't give back enough to the WordPress open-source project relative to its size.
He pointed to the "Five for the Future" campaign, which tracks how much time organizations pledge to WordPress development. The pages for both companies show a large gap in reported contributions:
Mullenweg framed this as a matter of resources. Both companies are in the neighborhood of $500 million in revenue, he said, so WP Engine should be contributing far more than its reported hours. He name-checked Silver Lake, the private equity firm that owns WP Engine, and publicly encouraged users and developers to take their hosting business elsewhere.
He also suggested he'd provide financial support to any WP Engine employees who face retaliation for speaking up about their employer's participation in WordPress. The implication was clear: WP Engine has the money, so it should pony up.
From Contributions to Conduct
The day after WordCamp US, Mullenweg shifted the argument in a blog post that took direct aim at how WP Engine operates WordPress sites. His allegation: WP Engine intentionally disables WordPress's built-in revision system, which tracks every change to posts and pages.
WordPress is a content management system, and the content is sacred. Every change you make to every page, every post, is tracked in a revision system, just like the Wikipedia... WP Engine turns this off. They disable revisions because it costs them more money to store the history of the changes in the database, and they don't want to spend that to protect your content.
That post framed the dispute as being about more than open-source contributions—it was about WP Engine eroding a core WordPress feature for profit. Mullenweg's argument had moved from numbers to trust.
Legal Maneuvering
WP Engine responded by sending a cease-and-desist letter to Automattic, demanding Mullenweg stop publicly disparaging the company. The letter also contained a significant allegation: that Automattic had been demanding large payments from WP Engine in the days before the WordCamp keynote, threatening a "war" if WP Engine didn't comply.
Mullenweg answered on Automattic's blog with his own cease-and-desist letter, alleging that WP Engine's commercial modifications to WordPress Core constitute trademark abuse. His argument:
WP Engine's business model is based on extensive and unauthorized use of these trademarks in ways that mislead consumers into believing that WP Engine is synonymous with WordPress. It's not. This is trademark abuse, not fair competition.
It also came to light that Automattic had offered WP Engine a term sheet with a royalty rate that reportedly increased over time—7%, then 8%—before being pulled off the table entirely.
The Ban That Hit Real Users
The conflict escalated sharply on September 25 when WordPress.org blocked WP Engine customers from updating and installing plugins and themes through WP Admin. The ban affected WP Engine proper and its subsidiary Flywheel.
WP Engine deployed a workaround to restore functionality for its customers, but WordPress.org soon found and closed that loophole. WP Engine reportedly took steps to distinguish itself from the WordPress brand on its own site during this period.
The direct impact on WP Engine customers—people who had nothing to do with the corporate dispute—was immediate:
Individual site owners on WP Engine suddenly faced an unpleasant reality: their content management system had become a point of control in a corporate fight. No matter which side you sympathize with, this development put real end users in the crossfire.
Plugin Fork and Ownership Revelations
By mid-October, the dispute had expanded into WordPress infrastructure itself. Key developments include:
- Ownership clarity: Matt Mullenweg is the sole owner of WordPress.org, meaning the infrastructure that gates plugin updates is controlled by one side of this dispute.
- ACF hijacked: WordPress.org took over WP Engine's free Advanced Custom Fields plugin, renaming it Secure Custom Fields—ostensibly for security purposes, though the move came without WP Engine's consent.
- Core feature battle: Mullenweg floated the idea of baking custom fields into WordPress Core, a move that would directly impact plugin developers who currently serve that need.
- Community collateral: At least one contributor to WordPress's Fields API work has stepped back from the project, citing concerns about how the disagreement is affecting community collaboration.
Automattic Employee Fallout
Mullenweg has taken unusual steps to address dissent within his own company. He offered what he called the "Alignment Offer": a buyout package of $30,000 or six months of salary, whichever was higher, for employees who disagreed with his approach and wanted to leave. Employees who took the offer would lose access to Automattic that same evening and would not be eligible for rehire.
159 people—8.4% of the company—accepted. A second buyout offer was later made at nine months of pay, up from six. The October departures disproportionately hit Automattic's ecosystem and WordPress-focused divisions.
There have also been allegations about Mullenweg redirecting emails from teamblind.com, the anonymous workplace forum, to himself, raising questions about whether employees could truly speak anonymously about these events.
A Personal Conflict in Open Source
This is no longer a dispute between two equal players in an ecosystem. Automattic—with Mullenweg's name in the company and his hand on WordPress.org—has substantial leverage over WP Engine's ability to serve its customers. The trademark arguments, the patent-infringement filings, and the access controls all point to a coordinated campaign against a company that has been a top WordPress host for years.
Both sides have made legitimate points: companies that profit from open source should contribute back, and infrastructure shouldn't be used as a weapon in commercial disputes. But with end users facing blocked updates and plugins being pulled from the very ecosystem they depend on, the stakes go far beyond two companies trading legal blows.
