Matt Mullenweg

A 2024 peak centered on Matt Mullenweg’s escalating conflict with WP Engine, followed by Automattic layoffs, governance disputes, and debates over AI and open source.

Who they are

Matt Mullenweg is Automattic’s CEO and a WordPress co-creator whose coverage centers on decisions spanning WordPress, WordPress.org, Automattic, and Tumblr. The stories cast him as a leader operating at the intersection of a commercial company and an open-source ecosystem, with public positions on platform governance, moderation, federation, and licensing.

The recent arc

Coverage surged in late 2024 as the dispute with WP Engine moved from access restrictions to a legal fight. Mullenweg said WP Engine no longer had free access to WordPress.org, while WP Engine sought a Northern California injunction to restore repository access; he also said WordPress was forking WP Engine-developed Advanced Custom Fields, which its team said had been taken without consent. The same period included reports that 159 Automattic employees took severance after disagreeing with WordPress’s direction and the handling of WP Engine.

The story then broadened from the WP Engine clash into organizational and community consequences. Mullenweg deactivated accounts of WordPress.org members associated with a proposed fork, and Automattic cut 16% of staff in April 2025, with Mullenweg framing the move as making the company more agile and responsive. A July 2025 Q&A shifted attention toward licensing with AI companies, Tumblr’s paused WordPress backend migration, fediverse issues, and content moderation; by April 2026, he was publicly criticizing Cloudflare-backed EmDash as insufficiently aligned with WordPress’s cross-platform democratization.

The tension

The central tension is control of a major open-source platform versus the expectations of companies and community participants that depend on it. WP Engine’s repository-access litigation and the Advanced Custom Fields fork made that conflict explicit, while account deactivations and employee exits suggested that governance choices also strained the WordPress community and Automattic internally. Mullenweg’s comparisons of WordPress with EmDash, alongside discussions of AI licensing and Tumblr moderation, extend the same question: how open platforms retain their values and authority while competing and commercializing.

Why it matters

If this trajectory continues, Mullenweg’s choices could shape not only Automattic’s operations but the practical boundaries of participation in the WordPress ecosystem for hosts, plugin developers, contributors, and users. The WP Engine case and community-fork activity indicate that control over core infrastructure can become a legal and legitimacy issue, while the AI, federation, and moderation discussions show adjacent pressure to define WordPress’s role as the web platform changes. Whether Automattic can pair a leaner organization with broadly trusted governance remains the key uncertainty in the coverage.

Related: WordPress · Automattic · WP Engine · Tumblr · Mastodon