Argues that every prior pushback against Mullenweg came from courts, ex-employees, or hosting customers — never from Automattic itself. The board finally acting represents a structural check on a CEO who had accumulated overlapping roles (Automattic CEO, WordPress.org controller, Foundation figurehead) that stopped being tenable once he weaponized .org infrastructure in a commercial dispute.
By submitting the TechCrunch story with a headline framing the board as 'forcing' Mullenweg out, the submitter foregrounds the governance angle — that this is Automattic's own board finally imposing consequences rather than external legal or community pressure doing the work.
Points out that ~40% of the web runs on WordPress, yet the plugin update channel, theme directory, and trademark license all flow through infrastructure a single individual can weaponize. The ecosystem never built a fallback because 'Matt wouldn't do that' was treated as a safe baseline assumption — and the WP Engine feud proved that assumption wrong. The community is now retroactively pricing risk it should have priced years ago.
Traces a year-long chain of escalations: the lawsuit, the disavowal checkbox on WordPress.org logins, the hostile takeover of ACF via the Secure Custom Fields fork, and the mass severance-package exodus of Automattic employees. Frames the board's action as the culmination of accumulated damage rather than a sudden decision, meaning the conflict of interest between Mullenweg's roles stopped being theoretical the moment .org was used as a weapon.
Automattic's board has forced Matt Mullenweg into a leave of absence, according to a TechCrunch report on September 9. The specifics of who signed off and what triggered the final push aren't fully public yet, but the arc leading here has been visible for a solid year: the WP Engine lawsuit, the checkbox on WordPress.org login pages requiring users to disavow WP Engine, the redirection of the ACF plugin under the Automattic-controlled 'Secure Custom Fields' fork, and the mass exodus of Automattic employees who took the severance package rather than stay through the escalation.
Mullenweg has been simultaneously CEO of Automattic (the for-profit), controller of the WordPress.org infrastructure (nominally a personal fiefdom he ran on the side), and the public face of the WordPress Foundation. That triple-hat setup was tenable when the three roles pulled in the same direction. Once he started using .org's plugin directory as a weapon in a commercial dispute against WP Engine, the conflict of interest stopped being theoretical.
The board's action is the first meaningful institutional check on Mullenweg since the WP Engine feud started — every prior response came from courts, ex-employees, or angry hosting customers, not from the entity that actually pays him. It's a small structural move with enormous implications for the roughly 40% of the web that runs on WordPress.
The surface-level story is a governance dispute at one company. The deeper story is that WordPress's entire distribution model depends on infrastructure that a single person can weaponize on a whim, and the ecosystem never built a fallback because 'Matt wouldn't do that' was the assumed base rate. He did do that. Now everyone is retroactively pricing the risk.
Consider what .org actually provides: the plugin update channel, the theme directory, the trademark license, the volunteer contributor coordination, and — through Mullenweg's personal control — the ability to delist, fork, or gate access to any of it. When Automattic forked ACF, it wasn't a normal open-source fork. It was a takeover of the update endpoint that millions of sites were already pointing at. The plugin on your server changed vendors without you clicking anything. That's not a fork; that's a supply-chain compromise executed with the maintainer's blessing, and the fact that it was legal under the GPL doesn't make it safe to build on.
The community reaction has calcified into three camps. WP Engine and its allies want a neutral foundation controlling .org. Automattic loyalists argue Mullenweg built the thing and can run it how he wants. And a growing pragmatist camp — mostly agencies and product companies with real revenue on the line — has quietly started evaluating ClassicPress, migrating to headless setups, or standing up private plugin mirrors. FreeBSD ports mirrors and Debian's package infrastructure exist precisely because distros learned this lesson in the 90s. WordPress is learning it in 2026.
There's also a labor angle worth naming. When Automattic offered the 'alignment' severance package last fall, roughly 8% of the company took it — a startling number for a company that had cultivated a strong internal culture for years. The people who left included senior contributors to core WordPress, meaning the .org side lost institutional knowledge at exactly the moment governance questions got hardest. A board that lets its CEO trigger a voluntary layoff of its most tenured people has been asleep for a while; the question isn't why they acted now, it's what took them a year.
If you ship on WordPress, the practical calculus has changed. Not because the code got worse — it didn't — but because the governance risk is now a real line item. Concretely:
Pin your plugin sources. If you're pulling updates directly from .org for anything mission-critical, mirror them. Composer + Satis, a private plugin repo, or even a nightly cron that pulls and caches the zip. The ACF-to-SCF handoff broke sites that were auto-updating; a mirror would have caught it. This is the same discipline you'd apply to any upstream dependency you don't control — and you don't control .org, no matter how comfortable that arrangement has felt.
Reassess the trademark exposure. Anything you've published that uses the WordPress mark — service names, agency branding, plugin titles — is licensed at Mullenweg's discretion via the Foundation. The WP Engine case established that he'll pull that license as leverage. If your business name has 'WP' in it, you're a potential hostage.
Have a headless escape hatch scoped, even if you don't take it. The migration cost from WordPress-as-monolith to WordPress-as-headless-CMS-behind-a-Next-or-Astro-frontend is the cheapest insurance policy available against 'what if .org changes the rules again.' You keep the editorial UX your clients like; you decouple from the plugin directory and the update channel. Several large publishers made this move quietly in Q1-Q2 and haven't looked back.
The board action doesn't resolve anything structural — Mullenweg still personally owns the WordPress.org domain, and the Foundation's governance charter still lets him operate it as he sees fit. A leave of absence is a pause button, not a fix. The real question over the next quarter is whether Automattic's board (and, more importantly, its investors) push for a permanent separation of .org from Mullenweg's personal control, or whether this ends with a public apology, a return, and the same structure intact. If it's the latter, the pragmatist camp's quiet migrations will get louder, and by this time next year the phrase 'WordPress ecosystem' will mean something meaningfully more federated than it does today.
> One person speculated that the timing may have something to do with Mullenweg’s annual trip to the Burning Man festival, after which he tends to return “with ideas.”This line is so perfectly on the nose it could be in a McSweeney's article and yet here it is in reality. We are truly on the
Unfortunately, this is for the best. WordPress powers a large percentage of the internet, and I'm not sure what's going on with Matt (who I've always liked) but something turned the past few years.He's been behind unforced error after unforced error as CEO, and I hope a break hel
I think it is easy to underestimate how big of a deal this is. Matt has a stranglehold on Automattic and Wordpress, it is not possible to remove his control over the ecosystem and he is volatile. Ousting him as CEO is almost certain to cause a major reaction from Matt, so, for Automattic to make thi
He's really tweeting through it today: https://xcancel.com/photomatt/with_repliesFrom a quick scan of his recent tweets, https://www.therepository.email/matt-mullenwegs-messages-wen... might answer the "why now?" of this.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
> “And the biggest news: I won't be able to make the ELT tomorrow,” Matt wrote in an Announcement Slack. He continued, writing that Mark Davies, current Automattic Chief Financial Officer, has “conspired” with Automattic Board of Directors members Ann Dunwoody, Toni Schneider, and Sue Decker