The software framework running forty percent of the web just had a massive internal crisis.
Automattic, the company behind WordPress, went into a total tailspin after its board of directors tried to kick out founder Matt Mullenweg. They voted to force him onto a paid leave of absence and put Chief Financial Officer Mark Davies in charge as interim CEO. The investors on the board wanted to stop Mullenweg because his aggressive legal battles and public feuds were scaring off big clients and making employees quit.
The board completely miscalculated their actual power. In less than forty eight hours, Mullenweg used his supervoting stock to bypass the board entirely and take back the company. He cut off Davies from internal servers, locked out the board members who went against him, and put himself back in control. Traditional corporate rules do not exactly work when a software founder holds all the keys.
If you manage a WordPress site, this corporate drama is relevant to you. With the board defeated, there are no internal checks left to balance Mullenweg decisions. You can expect a much more aggressive approach to how software licenses are handled, harder restrictions on hosting providers, and an unpredictable future for core code updates.
The biggest risk right now is code fragmentation. Because many big hosting companies and developers are losing trust in Automattic, they are starting to talk about creating a fork. This means they might copy the WordPress code and build a separate, independent version of the software.
If that happens, the plugin and theme market will split. You would have to manage different codebases, and getting basic security patches onto your site could become a logistical mess.
You also need to worry about the centralised WordPress dot org repository. Mullenweg owns this gateway personally, not through Automattic. It is the server that feeds updates, security fixes, and plugins to your website dashboard. Because his control here is absolute, you should expect much stricter, arbitrary audits before you can download or update extensions. For anyone running an enterprise site, relying on a central repository controlled by one person introduces a massive supply chain risk.
The sudden collapse of this coup cuts through the illusion that open source web infrastructure is a stable, neutral utility. The reality is that the code millions of independent businesses rely on is tied to the personal survival and decisions of a single founder, leaving your site exposed to the ongoing fallout of Silicon Valley boardroom fights.
