A reported 33-hour attempt by Automattic directors to remove WordPress co-founder Matt Mullenweg briefly put the company’s leadership in question. The episode unfolded amid an escalating legal fight with hosting provider WP Engine, internal staff departures and concerns about preserving evidence. For website owners, it is a reminder that a stable site depends on more than its publishing platform.
Key takeaways
- Automattic directors placed Mullenweg on paid leave and named CFO Mark Davies interim CEO, but Mullenweg was back in control by 12 September.
- The dispute reflects deeper divisions over Automattic’s campaign against WP Engine and the risks of the ongoing lawsuit.
- WordPress site owners can reduce day-to-day uncertainty with a clear maintenance plan covering updates, backups and security.
A boardroom move that did not last
According to Fortune, a three-member board committee voted to put Mullenweg on paid leave and appoint Davies as interim chief executive. Mullenweg, who has said he holds about 84% of Automattic’s voting power, regained control within days. Directors Sue Decker and Toni Schneider resigned, Ann Dunwoody was removed, and Davies and legal officer Andy Missan were dismissed. Mullenweg later appointed a new board.
The directors’ reasons for acting have not been fully explained publicly. The report says even some investors were left unclear about how Mullenweg reversed the decision. He subsequently joked on social media that founders should expect a coup attempt every few years.
The WP Engine dispute behind the tension
The leadership crisis emerged from a conflict over how companies that build businesses on WordPress should contribute to the open-source project. Mullenweg criticised WP Engine’s contribution and its use of WordPress branding, while WP Engine sued Automattic and Mullenweg, alleging attempted extortion and other misconduct. Automattic denies wrongdoing and has brought its own trademark claims. Both sides dispute the other’s allegations.
The litigation has also raised questions about electronic messages sought during evidence-gathering. WP Engine says relevant messages were not properly preserved and has asked the court to dismiss Automattic’s claims as a penalty. Automattic denies wrongdoing. At an October hearing, the judge reportedly questioned whether the evidence justified a finding that messages had been deliberately destroyed, while also criticising claims about preservation steps. The matter remains unresolved.
What WordPress site owners can do
The boardroom turmoil does not mean WordPress itself is going away: the open-source software is used across a large share of the web. But platform-wide news can be a useful prompt to check that your own website has dependable day-to-day care.
A WordPress maintenance plan or care plan can help keep software and extensions updated, backups current and security checks regular. It is also worth knowing who will respond if an update causes a problem. These practical safeguards cannot prevent corporate disputes, but they can make your site easier to manage when the wider WordPress ecosystem is in the headlines.