Official confirmation
An Automattic spokesperson confirmed to TechCrunch[3] that Matt Mullenweg is once again chair of the board and chief executive. The statement also says he has the board's full support. [1 · TechCrunch]
The confirmation followed public signs of his return: WordPress executive director Mary Hubbard told the team that Mullenweg had been reinstated, and the project's official account shared the message. [1 · TechCrunch] [2 · The Verge]
What happened before the return
Automattic's board had previously placed Mullenweg on paid leave and appointed chief financial officer Mark Davies as interim CEO. The company's new statement means that this transitional arrangement has ended. [1 · TechCrunch] [2 · The Verge]
The reasons for the conflict and the current composition of the board have not been fully disclosed. What is confirmed is therefore Mullenweg's return and the stated support of the board, while the broader picture of corporate governance remains unclear. [1 · TechCrunch] [2 · The Verge]
Sources
- TechCrunch — Automattic confirms Mullenweg’s return — September 12, 2026
- The Verge — initial reports of Mullenweg’s return — September 11, 2026
- Automattic — the company and its activities — Primary source; checked September 13, 2026
- WordPress — license and user freedoms — Primary source from the project
- Lerner and Tirole — Some Simple Economics of Open Source — The Journal of Industrial Economics, 2002; economic interpretation
Expert commentary
Mullenweg's return removes uncertainty about Automattic's leader. I would assess the next stage by the company's ability to make consistent decisions after the conflict. Restoring the previous leadership may accelerate work, but does not explain how new disagreements will be resolved. Predictable authority, accountability and procedures matter more to partners than one side's personal victory. Governance stability therefore remains a question that will require further observation. [1 · TechCrunch]
The event's market impact should be considered through the structure of the whole ecosystem. Automattic conducts commercial business around open products, while the WordPress license gives users the freedom to use and modify the software. My conclusion follows: a governance crisis at one company does not mean the disappearance of the technology. But access to source code is no substitute for maintenance teams, extension compatibility or convenient services. These are the connections where consequences that customers can feel may arise. [3 · Automattic] [4 · WordPress]
Lerner and Tirole's work on the economics of open-source software provides a scholarly basis for this assessment. It explains developer participation partly through professional and career incentives. Applied to this news, my hypothesis is that predictable rules for collaboration will influence outside specialists' willingness to invest time in the ecosystem. A potential loss of trust is dangerous because it can gradually weaken participation; that effect could emerge after public discussion of the leadership changes has ended. [5 · Lerner and Tirole]
For an online store owner, the practical risk concerns continuity of sales. I would check which critical functions depend on a single provider, whether the site can be restored from a backup and who will support payments or integrations if service terms change. This is a dependency assessment, not a recommendation to move a site urgently. An open license creates options, but configuration, data and the availability of competent service providers determine the actual cost of switching. [4 · WordPress]
For the global digital environment, the issue extends beyond one company. Automattic connects its activities with making publishing and commerce accessible to people in different countries. If commercial participants and independent developers retain the ability to collaborate, this model can support a diversity of suppliers and tools. If disagreements lead to incompatible forks, formal freedom of choice could be accompanied by higher maintenance costs. These are possible paths, not consequences of the founder's return that have already occurred. [3 · Automattic] [5 · Lerner and Tirole]
I would suggest assessing the restoration of trust through three groups of signals: stability of the leadership team, release regularity and participation by external developers. Customers would also benefit from watching support timelines and changes in commercial terms. An increase in code changes alone is insufficient: it could reflect the work of a small team. A more convincing sign of resilience is distributed participation, clear decision-making rules and the absence of sudden barriers to compatible third-party products. [5 · Lerner and Tirole] [4 · WordPress]