Matt Mullenweg is back in charge of Automattic — and he wants everyone to know it. The WordPress co-founder has reclaimed his position as CEO of the company behind WordPress.com, WooCommerce, and Tumblr after a remarkable internal power struggle in which the company’s own board reportedly tried to remove him. The episode is one of the most dramatic founder-versus-board confrontations in recent tech memory, and it ended with Mullenweg still holding the keys. For a company that powers roughly a significant share of the global web, the stability — or instability — at the top matters far beyond Silicon Valley gossip.
This is not the first time Mullenweg has found himself at the center of controversy. His public spat with WP Engine in 2024 drew widespread attention across the developer community and raised pointed questions about governance at Automattic, a privately held company valued at around $7.5 billion at its last major funding round. If you followed that earlier chapter, the messy due diligence dynamics that can unravel corporate deals are a useful lens for understanding how quickly internal trust at a tech company can collapse.
The Board Moved, Mullenweg Didn’t Leave
According to the TechCrunch report, the Automattic board made an attempt to oust Mullenweg from his role as CEO. The specifics of what triggered the move have not been fully disclosed publicly, but the attempt failed — and Mullenweg’s reinstatement was confirmed by Automattic itself. The company’s acknowledgment of the attempted ouster is itself notable; most corporations prefer to let these battles resolve quietly behind closed doors, with a sanitized press release issued afterward. Automattic did not get that luxury here.
Mullenweg addressed his return directly in a public announcement on X, making clear he was back and had not stepped aside voluntarily.
What This Means for WordPress and the Open Web
Automattic is not a typical SaaS company. It sits at the intersection of open-source ideology and commercial software, stewarding WordPress.org’s community alongside its own commercial products. That dual role has always made Mullenweg a uniquely complicated figure: simultaneously the spiritual leader of an open-source movement and the operator of a private company with investors and a board expecting returns. The tension between those two identities appears to have reached a breaking point that triggered this confrontation.
The fallout from this episode is unlikely to be clean. Employees watching their founder-CEO survive a board challenge will draw their own conclusions about where real power sits inside the company. Investors, meanwhile, will be asking harder questions about governance structures that allowed this conflict to become public in the first place. The WordPress developer ecosystem — millions of agencies, freelancers, and plugin builders whose livelihoods depend on platform stability — will be watching closely for any signal that internal chaos is affecting product roadmaps or partnership commitments. Mullenweg may have his title back, but the harder work of rebuilding institutional trust has only just started. Whether he can pull that off while the pace AI disruption forces every major platform to reinvent itself will define whether this victory is lasting or merely symbolic.
