In a recent podcast interview, WordPress co-founder Matt Mullenweg sought to downplay the ongoing dispute between Automattic, the company he leads, and major WordPress host WP Engine. Mullenweg expressed optimism that the legal and business disagreements will be resolved within a few months, despite heated criticism from segments of the WordPress community.

The dispute centers on licensing and trademark conflicts, with WP Engine accusing Automattic of making unfounded claims regarding proprietary software and branding issues. Mullenweg, however, painted a different picture, suggesting that WP Engine’s legal actions forced him to respond aggressively to defend WordPress’s open-source principles.

During the interview, one of the podcast hosts admitted surprise at how harshly Mullenweg had attacked WP Engine, stating that it seemed out of character for the usually composed WordPress leader. In response, Mullenweg explained that standing up for WordPress sometimes requires a confrontational approach, comparing the situation to standing up to a bully on the playground.

“You kind of have to stand up for yourself,” Mullenweg remarked. “There have been maybe four or five times in the history of WordPress where I had to fight to protect our principles and the sustainability of the project. This isn’t new for me.”

Mullenweg then referenced past controversies in the WordPress community, including the 2005 “Hot Nacho” scandal, the “Easter Theme Massacre,” and a well-known conflict over the Thesis theme. These incidents, he noted, once generated extensive media attention but have since faded from public memory.

“I had the Hot Nacho scandal in the first couple of years of WordPress,” he said. “It used to be like half my Wikipedia page, and now it’s not even mentioned much anymore. I think in five years, maybe this WP Engine issue will just be a sentence—or not even on there at all.”

The Hot Nacho scandal involved SEO-related spam hosted on WordPress.org, resulting in a temporary Google ban and widespread criticism. Reflecting on that formative experience, Mullenweg suggested that it helped him develop a thick skin and a better understanding of crisis management.

Despite the high-profile nature of the WP Engine dispute, Mullenweg downplayed the company’s overall significance in the WordPress ecosystem. He pointed out that WP Engine, while influential, represents a relatively small portion of WordPress installations worldwide.

“They’re probably the sixth or seventh largest WordPress host,” he said. “People have made this into a bigger deal than it is. They probably have around 700,000 or 800,000 sites, which is a small percentage of all WordPress sites globally.”

Mullenweg further emphasized that he expects the conflict to be resolved soon, though he did not provide specific details on how this might happen. “I expect this to resolve in the next few months,” he stated. However, he acknowledged that the situation has generated significant backlash on platforms like Reddit and Twitter, where debates about his leadership have intensified.

Mullenweg characterized WP Engine as the aggressor in the conflict, claiming that the hosting company had been preparing a legal case against Automattic while negotiations were still underway. “Three days after I gave my presentation [at WordCamp], they launched a huge lawsuit with Quinn Emanuel, one of the biggest, nastiest law firms,” he said.

While Mullenweg’s supporters have praised him for defending WordPress’s open-source principles, critics argue that the situation reflects deeper governance and transparency issues within the project. Some members of the WordPress community have called for greater dialogue between Automattic and WP Engine, urging both sides to prioritize the interests of the broader ecosystem.

The podcast hosts noted that they had received numerous questions from WordPress users seeking clarification on key aspects of the dispute. However, many of these questions were not addressed during the interview, which the hosts attributed to a desire to keep the conversation balanced.

Still, the interview offered insights into Mullenweg’s mindset and approach to leadership. He framed the current conflict as part of a broader pattern of defending WordPress from perceived threats and reaffirmed his commitment to the platform’s long-term success.

“Sometimes you have to fight to protect your open-source ideals and your community,” Mullenweg said.

Whether the WP Engine dispute will indeed be resolved within a few months, as Mullenweg predicts, remains uncertain. For now, both sides appear entrenched in their positions, with legal proceedings continuing in the background.

As the WordPress community watches closely, many are hopeful that a resolution can be reached that preserves the integrity of the platform and fosters greater collaboration among its stakeholders. Until then, the dispute serves as a reminder of the challenges inherent in managing one of the world’s most popular open-source projects.