At the height of the WordPress-WP Engine controversy in late 2024 and early 2025, coverage was relentless. Every new lawsuit, every account deactivation, every public statement by Matt Mullenweg has created another wave of comments. Tech journalists, WordPress developers, bloggers, hosting companies and plugin authors all had something to say. The conflict had staff, graphics and stakes affecting hundreds of thousands of websites.
By mid-2026, the noise has subsided. No more viral open letters. A flurry of Twitter threads and blog posts from agitated WordPress contributors calmed down. Mullenweg is still CEO of Automattic. The lawsuit is still pending. And the structural problems that make the whole debate possible still remain entirely unresolved.
Silence is not decisive. It is fatigue.
What actually happened, briefly
The controversy began in September 2024 when Mullenweg publicly criticized WP Engine, one of the largest hosting companies powered by WordPress, for profiting from the WordPress brand and ecosystem without contributing commensurately to the open source project. Claimed automatically That WP Engine artificially inflates its business value and confuses customers about its relationship with WordPress. WP Engine denied the claims and filed a personal lawsuit against Automattic and Mullenweg in October 2024, alleging extortion, defamation, unfair competition, and tortious interference with its business.
What followed was an escalation that shocked even those accustomed to open source governance disputes. Automattic blocked WP Engine’s access to the WordPress.org plugin and theme update infrastructure, affecting more than 200,000 websites. California federal judge given WP Engine Preliminary ruling in December 2025 ordering Automattic to restore access within 72 hours. Automattic also took control of the Advanced Custom Fields plugin, one of the most used plugins in the WordPress ecosystem, citing security concerns – a move by WP Engine and seen by many in the community as an act of revenge.
The case is still working its way through the courts, with a motion to adjourn the hearing scheduled, with WP Engine filing a third amended complaint with newly disclosed details in February 2026, and both sides’ arguments on the motion to dismiss set for June 4, 2026. marketing. Nobody won. No one has solved it.
The ever-present management challenge
The legal dispute is real and consequential. But the underlying problem it exposes is older than the lawsuit and will continue regardless of the verdict.
WordPress is at once an open source software project, a commercial ecosystem, and an infrastructure managed by entities with intertwined but distinct interests. WordPress.org – the infrastructure that hosts plugin and theme distribution for the entire ecosystem – is run as Matt Mullenweg’s personal project, with no formal governance structure, no oversight board, and no mechanism for the wider community to challenge decisions made about access or resource allocation. Automattic, a commercial company led by Mullenweg, has an exclusive commercial license to the WordPress trademark, which is held by the WordPress Foundation.
This arrangement worked for more or less two decades. It worked because the incentives were broadly aligned and because no one tested what would happen if they didn’t. The WP Engine controversy was a test, and its response was harsh: a single individual could, without community approval or formal process, block a major commercial actor’s access to shared infrastructure, seize control of a widely used plugin, and wage an open campaign against a competitor.
Repository community response report Prominent community members deactivated WordPress.org accounts, including longtime contributors Joost de Valk, founder of Yoast SEO, and Karim Marucchi, CEO of Crowd Favorite, who have described a “culture of fear” critical of Mullenweg’s decisions, after proposing reforms. Several senior participants told reporters they feared professional retaliation for speaking out. The executive director of the WordPress project has resigned. Naoko Takano, who worked at Automattic for fourteen years, quit in protest.
None of these people returned. The governance structure that allowed them to go is unchanged.
What market share data actually shows
Meanwhile, W3Techs shows the data WordPress’ share of all websites fell from 43.2% in December 2025 to 41.9% by the end of May 2026 – a six-month straight decline after a period of steady growth. For context, WordPress still powers about 59.4% of all websites running a known CMS, and its closest competitor, Shopify, accounts for about 5.2% of all websites. This is not a collapse. However, this is the first sustained contraction in years, and the direction is more important than any data point.
It’s not Wix or Squarespace that’s gaining category share — both grew by just fractions of a point. A growing segment are generally detectable non-CMS sites: sites built with static generators, frontend frameworks, and artificial intelligence that don’t need the infrastructure that WordPress provides. The platform does not lose to the competitor. It follows that a portion of its potential audience bypasses the CMS category altogether.
TechnologyChecker data It shows that the number of active WordPress domains reached 5.8 million at the beginning of 2025 and has seen its first steady decline since then. The controversy didn’t cause it—those structural changes predated it—but it almost certainly precipitated a rethink among bloggers and publishers who are considering platform options and looking to 2024 and 2025 to see the ecosystem’s single point of control demonstrate how it can be used.
Where the Mullenweg stops
Calls for Mullenweg’s resignation intensified through late 2024 and early 2025, and have since become background noise rather than an active campaign. In an interview with TechCrunchMullenweg has announced that he has no intention of resigning, rejecting the idea of handing over leadership to a committee, and ultimately intends to find a successor to continue to run Automattic and the WordPress project. It has described its actions throughout the dispute as necessary to protect the integrity of WordPress from commercial actors who benefit from its brand without continuing its development.
Whether this framework is persuasive depends almost entirely on whether Mullenweg accepts the proposition that his judgments constitute a fair contribution to WordPress is the relevant standard—the governance structure, as currently constructed, does not require him to justify anyone.
What silence really means for bloggers and publishers
For the blogging and publishing community, the WordPress controversy has raised a question that the ensuing lull has left unanswered: What does it mean to build a platform whose governance depends on the continued goodwill of its founder?
The answer most publishers have come up with is not to abandon WordPress – the platform is too deeply embedded in independent internet infrastructure for mass migration to be practical or necessary. It is to maintain the addiction more consciously than before. The controversy made clear one thing that has always been structurally true: an open source license guarantees access to the code. It does not guarantee access to the infrastructure, community resources, or ecosystem connections that make WordPress functional at scale.
This is not a reason to give up on WordPress. It’s a reason to understand what you’re actually relying on when you trust it, and make platform decisions, plugin dependencies, and hosting choices with a clearer picture of where the structural risks actually lie. The debate may subside. The subject of the debate has not moved an inch.
