Mullenweg says “WordPress.org just belongs to me personally”, as his WP Engine feud blurs the lines between WordPress.org, WordPress Foundation, and Automattic
The lines between the WordPress open-source project, the nonprofit backing it, and the commercial arm owned by Automattic are blurring.
Context & Ripple Effects
The dispute had already moved beyond rhetoric: Mullenweg publicly accused WP Engine of benefiting from confusion between the WordPress project and commercial services, while saying Automattic had long sought a licensing arrangement with the host. The ownership claim makes the governance boundary at the center of that dispute more consequential.
Related coverage subsequently reported that WordPress was forking WP Engine-developed Advanced Custom Fields, with its team saying the plugin was taken without consent. That escalation turns a disagreement between companies into a test of how control over project infrastructure can affect ecosystem participants.
First-order effects
- WP Engine, plugin developers, and WordPress users must now assess whether decisions presented through WordPress.org are separable from Automattic's commercial dispute with WP Engine.
- The stated personal control of WordPress.org sharpens the apparent overlap among the project site, the Foundation, and Automattic, raising an immediate governance and conflict-of-interest question for the community.
Second-order effects
- Hosting and plugin businesses that depend on WordPress distribution or project-controlled services face greater uncertainty about whether commercial disputes can affect access, branding, or software stewardship.
- The Advanced Custom Fields fork shows the dispute can reach product-level choices, increasing the incentive for developers and customers to scrutinize who controls critical plugins and distribution channels.
Third-order effects
- If project governance and commercial enforcement continue to converge, WordPress's ecosystem may place more weight on formal accountability, independent governance, and forkability rather than informal trust in stewardship.
- The conflict could make control of open-source infrastructure itself a more visible competitive variable: nominally shared project assets can become leverage when ownership and commercial interests are not clearly separated.
The trend: This is part of a broader open-source governance trend in which commercial dependence on shared infrastructure is exposing the importance of clear control, accountability, and neutral stewardship.