Round Two: WP-Engine vs. WordPress

The tension between WordPress’s founding father, Matt Mullenweg, and WP Engine has reached new heights, marking another chapter in the saga that’s dividing the WordPress community. It all began with Mullenweg’s explosive comments during WordCamp US, where he called WP Engine a “cancer to WordPress,” criticizing the company for monetizing the open-source platform without giving back enough.

In response, WP Engine quickly issued a cease-and-desist letter, demanding that Mullenweg retract his statements, claiming his remarks were not only damaging but also false. According to WP Engine, the remarks were the culmination of a behind-the-scenes dispute, where Mullenweg allegedly demanded millions of dollars in trademark licensing fees. WP Engine insists they have contributed significantly to WordPress, including millions in sponsorships and community resources.

The real fight here? It’s not just legal. It’s philosophical. Mullenweg’s rallying cry to protect the WordPress ecosystem’s open-source ethos is resonating with some, as he contrasts Automattic’s reported 3,900 hours contributed weekly to open-source with WP Engine’s 47 hours. Yet, WP Engine has defended itself, emphasizing its fair use of the WordPress trademark and highlighting its investment in the community.

With Automattic’s official response still pending, this conflict threatens to set a precedent for how open-source companies balance profit with contribution. As both parties dig in, the broader WordPress community watches closely. The question looming over everyone’s head: What’s next? One thing is clear — this battle is far from over, and its resolution could reshape the future dynamics of open-source collaboration.

For the WordPress ecosystem, the next round is about more than just business. It’s about the future of open-source integrity.