Matt Mullenweg Reclaims Control of Automattic Just 48 Hours After Board-Mandated Leave of Absence Amid Ongoing Leadership Turmoil

In an astonishing corporate turnaround that has sent shockwaves through the technology and open-source communities, Matt Mullenweg has resumed control as the chief executive officer of Automattic, the driving commercial force behind WordPress. The rapid reversal of fortune occurred less than 48 hours after the company’s board of directors abruptly placed him on a leave of absence. The chaotic sequence of events culminated late Thursday evening, September 12, 2026, when Mullenweg announced to employees via internal Slack channels that the board had rescinded its decision and restored him to his leadership position.

The high-stakes corporate drama unfolded in plain view of the company’s workforce through internal messaging platforms, highlighting deep-seated tensions at the upper echelons of Automattic. According to leaked screenshots obtained by digital media outlet 404 Media, Mullenweg signaled his return by posting the message, "Don’t call it a comeback," accompanied by a hyperlink to LL Cool J’s iconic hip-hop music video, "Mama Said Knock You Out." At the time of the announcement, Mullenweg’s internal Slack profile picture was updated to depict him wearing a pirate hat and an eyepatch—a subtle nod to the rebellious, unorthodox corporate culture he has long fostered, yet deeply symbolic of the combative nature of his tenure.

"Happy to announce the board is back in agreement, and I’m in control of Automattic," Mullenweg wrote in the company-wide announcements channel. He further addressed the tumultuous preceding 48 hours, noting that there were pressing internal matters to sort through while expressing hope that the abrupt friction stemmed largely from misunderstandings. "Because I have huge respect and regard for those involved," he added, attempting to smooth over the fracturing relationships among top executives.

The Chronology of a 48-Hour Corporate Crisis

The breathtaking speed at which Mullenweg was ousted and subsequently reinstated represents an extraordinary anomaly in corporate governance. The timeline of the crisis highlights the volatile dynamics between the WordPress co-creator, the corporate board of directors, and the executive suite.

The crisis began earlier in the week when Automattic’s board of directors, reacting to mounting pressure and years of controversial strategic decisions, voted to place Mullenweg on a mandatory leave of absence. In the immediate aftermath of that decision, the board designated Mark Davies, Automattic’s Chief Financial Officer, to step in as interim CEO to stabilize the company and steer its day-to-day operations. Davies’ ascension was viewed by many corporate observers as a signal that the board was preparing to assert greater institutional independence from its charismatic, polarizing founder.

However, Davies’ tenure at the helm proved remarkably short-lived. By Friday, September 11, multiple sources reported that Davies’ corporate Slack account had been deactivated. Simultaneously, Mullenweg initiated his counter-offensive, rallying internal support and negotiating directly with board members. By Thursday night, Mullenweg had successfully persuaded enough stakeholders to alter course, forcing a realignment of the board and neutralizing Davies’ brief interim leadership.

As of late Friday, neither Mullenweg, Davies, nor Automattic’s corporate communications team had responded to multiple requests for comment from major tech publications, though reports indicated that a formal blog post from Mullenweg was imminent. True to form, Mullenweg published a post titled "Major Life Announcement" on his personal blog on Friday morning. Bizarrely, rather than addressing the existential corporate power struggle that had just transpired, Mullenweg’s post focused primarily on a personal anecdote regarding his decision to purchase a tugboat.

"Anybody who’s founded a company and had to find good stewards knows that no one will love a thing quite like the original owner, but sometimes you can find the perfect person to carry the torch," Mullenweg wrote, drawing a philosophical parallel between marine stewardship and corporate governance, while leaving industry analysts to parse the hidden meanings behind his nautical metaphor.

Background Context: Years of Escalating Tensions

To understand the suddenness of Mullenweg’s ouster and his aggressive reclamation of power, one must examine the protracted period of instability that has plagued Automattic and the broader WordPress ecosystem over recent years. The company’s recent history has been characterized by intense legal battles, significant workforce reductions, high-profile executive and employee departures, and aggressive strategic pivots that alienated segments of the developer community.

Foremost among these controversies has been Mullenweg’s scorched-earth legal and public relations war against WP Engine, a major WordPress hosting provider. The dispute erupted into public view when Mullenweg publicly branded WP Engine as a "cancer" to the WordPress community, accusing the company of profiting off open-source software while contributing insufficiently to its core development. This public feud quickly escalated into sprawling litigation, featuring intellectual property claims, counterclaims, and widespread industry alarm.

The collateral damage of the WP Engine conflict extended deep into Automattic’s internal operations. Critics inside and outside the company questioned Mullenweg’s abrasive public posture, arguing that his combative rhetoric was damaging the brand equity of WordPress—a platform that powers over forty percent of all websites on the internet.

Compounding these strategic disputes, Automattic underwent significant turbulence regarding its internal workforce. In early 2025, the company implemented waves of layoffs that rattled employee morale. The friction deepened when remaining employees discovered that internal documents contained tracking watermarks designed to catch corporate leakers—a move that intensified an atmosphere of surveillance and paranoia within the remote-first organization.

The friction reached a boiling point in late 2024 when an estimated 159 employees chose to accept buyout packages and leave Automattic rather than continue operating under Mullenweg’s polarizing leadership style. Furthermore, regulatory and investigative reporting in early 2026 revealed internal plans indicating that Mullenweg and Automattic allegedly contemplated shaking down other major hosting companies for mandatory WordPress royalties, further alienating industry partners and corporate stakeholders who felt the platform’s foundational open-source ethos was being compromised for commercial leverage.

Implications and Broader Industry Impact

The dramatic standoff and Mullenweg’s subsequent reinstatement carry profound implications for Automattic, WordPress, and the broader open-source software landscape.

From a corporate governance perspective, the episode exposes deep fractures between visionary founders and institutional boards. When a founder holds outsized ideological and operational control over a company—particularly one inextricably linked to their personal identity, such as Mullenweg and WordPress—traditional corporate checks and balances often fail. The board’s inability to sustain its suspension of Mullenweg for even 48 hours suggests that Mullenweg retains immense structural leverage, likely protected by voting shares, loyal internal factions, or the sheer reality that replacing a founder of his stature presents insurmountable operational risks.

However, the pyrrhic nature of this victory cannot be ignored. By flexing his muscles and reasserting control via internal channels with pirate-themed bravado, Mullenweg has demonstrated that he remains firmly in charge, but he has also laid bare the instability of Automattic’s leadership structure. Institutional investors, enterprise clients, and the vast global community of WordPress developers are left to navigate an environment of profound uncertainty.

The open-source community relies heavily on stability, predictability, and collaborative goodwill. The ongoing litigation with WP Engine, combined with internal purges, employee exoduses, and erratic executive theater, threatens to fracture the WordPress ecosystem permanently. Already, rival content management systems and fork projects have sought to capitalize on the turbulence, positioning themselves as stable alternatives for developers exhausted by the perpetual controversy surrounding Automattic’s leadership.

As Mullenweg returns to his desk—perhaps casting an eye toward his newly acquired tugboat—the fundamental challenges facing Automattic remain entirely unresolved. The company must still navigate its complex legal battles, repair its fractured relationship with the developer community, restore internal morale among a traumatized workforce, and prove that a company driven by fierce ideological battles can sustainably manage a commercial empire. For now, the captain has retaken the wheel, but the waters ahead remain treacherous.