In the intricate world of open-source platforms, WordPress finds itself at the center of a brewing storm, a battle that pits its community-driven foundation against corporate interests. The platform, licensed under the GNU General Public License, allows developers to modify and use it commercially as long as they uphold the same licensing terms. However, the WordPress logo and trademarks are not part of this free-for-all and require permission from the WordPress Foundation.
Matt Mullenweg, the brain behind WordPress, established the WordPress Foundation as a charitable organization. Until recently, it seemed that the abbreviation "WP" was free from the bounds of trademark restrictions. But just two weeks ago, that line in the sand was moved. The Foundation updated its policy to restrict the use of "WP" when it causes confusion, alluding to WP Engine—a key competitor that had previously flown under the radar. WP Engine, a highly successful company backed by private equity giant Silver Lake, profits from hosting WordPress but, in Mullenweg’s view, fails to give back to the ecosystem. WP Engine’s contributions pale in comparison to Automattic, the company that runs wordpress.com and other WordPress-related services, where Mullenweg also serves as CEO.
Automattic's history with WP Engine is as complex as it is fraught. Once an investor and part-owner, Automattic sold its stake in 2018. Since then, tensions have simmered, but they reached a boiling point on September 20th when Automattic sent WP Engine a trademark license agreement, demanding a steep 8% royalty on its gross revenue. This would translate to millions of dollars monthly. Mullenweg’s grievances with WP Engine extend beyond mere profit-sharing: he accuses them of misusing WordPress trademarks, offering payment plans that resemble official WordPress products, and "strip mining" the open-source community by repackaging plugins like WooCommerce without significant contributions to the ecosystem.
When WP Engine refused the terms, things escalated. Just a day later, at the WordCamp US Conference, Mullenweg took to the stage, labeling WP Engine a “cancer to WordPress” and criticizing private equity for its damaging impact on open-source communities. In a dramatic turn, wordpress.org updated its login page with a new checkbox requiring users to declare that they were not affiliated with WP Engine. With a CSS class ominously named “login lawsuit,” the requirement was quickly met with confusion and pushback. WP Engine had to publicly clarify that its customers and users were not affiliates, while many in the WordPress community pondered the future of the platform.
This clash reveals that, in the war between Automattic and WP Engine, there may be no winners—only casualties. Both sides appear motivated by self-interest, leaving WordPress users caught in the crossfire. Whether Mullenweg's actions were driven by principle or profit, and whether WP Engine is a blight on the community or merely an opportunistic player, one thing is clear: this saga is far from over.