Matt Mullenweg CEO Return Reverses Automattic Board Ouster

Matt Mullenweg regained control of Automattic within three days, turning the Matt Mullenweg CEO return into an extraordinary reversal of a board decision.

Automattic’s board placed its founder on paid leave on September 9, 2026. Chief Financial Officer Mark Davies then became interim CEO with the board’s stated confidence. By September 12, Automattic said Mullenweg was again chairman and CEO, now with the board’s full support.

The short-lived removal matters beyond one executive’s title. It raises a larger question about whether Automattic’s board can independently oversee the founder who controls several institutions central to WordPress. That question carries more weight because the company remains entangled in litigation, internal restructuring, and a prolonged conflict with hosting provider WP Engine.

The Matt Mullenweg CEO Return Took Only Three Days

Automattic officially reversed its leadership change before explaining why the original decision happened.

Mullenweg told employees on September 9 that board members had voted to put him on paid leave. According to the first detailed account of the board decision, he opposed the motion and described it as a conspiracy.

The directors he named included Ann Dunwoody, Toni Schneider, and Sue Decker. He also accused Davies of participating in the effort. Those accusations appeared in an internal Slack message reviewed by reporters, not in a public company filing.

Automattic subsequently confirmed that Mullenweg was on leave. The company said Davies would serve as interim CEO with the board’s full confidence. That statement gave the board action corporate legitimacy, even though Automattic did not disclose its reasoning.

Mullenweg remained a director during the leave. He also retained roles and influence beyond Automattic, including his position as a co-founder of WordPress. The distinction between Automattic, WordPress.org, and the WordPress Foundation is legally important, but their leadership relationships remain closely watched.

The situation changed again early on September 11. Mullenweg posted an internal message saying the board was “back in agreement” and that he controlled Automattic again.

Multiple employees reportedly verified the message. However, Automattic did not immediately confirm the reversal, leaving an unusual gap between Mullenweg’s assertion and the company’s public position.

Reports said Mullenweg removed other administrators from Automattic’s Slack workspace during the confrontation. That detail has not been independently documented through public corporate records. It remains an attributed report based on employee sources.

The uncertainty ended on September 12. An Automattic spokesperson confirmed the leadership reversal and said Mullenweg was chairman and CEO with the board’s full support.

The statement settled who held the job. It did not explain what produced the original vote, what changed during the following days, or whether any governance terms accompanied his return.

That omission is the central tension. A board capable of appointing an interim CEO on Wednesday appeared united behind the displaced founder by Saturday. Automattic has not publicly reconciled those two positions.

Automattic’s Board Now Faces the Hardest Questions

The failed ouster puts more pressure on Automattic’s directors than on the founder they briefly removed.

Corporate boards appoint executives, monitor risk, and intervene when leadership threatens the company’s interests. At Automattic, the board exercised that authority and then reversed itself almost immediately.

The first unresolved question concerns cause. Automattic has not said whether the leave involved litigation, management conduct, workplace concerns, strategic disagreements, or another issue.

Silence can be appropriate when employment or legal matters are involved. Yet the absence of even a general explanation makes it impossible to assess whether the board resolved its concern.

The second question concerns process. Mullenweg reportedly told employees that he received only 50 minutes of notice before the meeting. He also said he lacked adequate time to consult legal counsel.

That account comes from Mullenweg and has not received a detailed public response from the directors. Still, it suggests that the disagreement involved more than a carefully planned executive transition.

The third question concerns enforcement. A board’s formal authority matters only when the company can implement its decisions across operational systems, communications, and leadership structures.

Reports that Mullenweg retained or regained control of internal tools therefore deserve attention. They suggest that practical control might not align neatly with board resolutions inside a founder-led private company.

The fourth question concerns board composition. Reports indicated that Schneider’s position might have changed after the confrontation. Automattic had not publicly provided a complete account of any resulting departures when it confirmed Mullenweg’s return.

Automattic’s official board page identifies Mullenweg as chairman and CEO. However, a title page cannot answer whether directors can challenge him effectively during another crisis.

These questions do not prove that the board acted improperly. Directors might have received new information, negotiated new safeguards, or concluded that the leave created greater risks than it solved.

Automattic has disclosed none of those possibilities. Readers should avoid treating speculation about a negotiated settlement as fact.

The board’s “full support” language also requires careful interpretation. It establishes Automattic’s public position after the reversal, but it does not reveal whether that support was unanimous or conditional.

For employees, the immediate pressure is organizational clarity. They received one leadership arrangement, watched it collapse, and then received another without a public explanation of the underlying dispute.

For investors and business partners, the issue is predictability. They need to know whether Automattic’s governing body can make durable decisions during legal, financial, or operational stress.

The directors therefore face a difficult credibility test. They must demonstrate that the board remains an oversight body, rather than a temporary coalition unable to enforce its most consequential vote.

Founder Control Beat Formal Oversight

The primary conflict is founder control versus board oversight, and founder control won this round.

Mullenweg is not simply a hired chief executive. He founded Automattic, co-created WordPress, chairs the company’s board, and remains closely associated with WordPress.org.

Those overlapping roles create unusual leverage. A conventional CEO can lose a board vote and surrender corporate systems. A founder connected to the company’s identity, technical infrastructure, and surrounding community occupies a different position.

That does not mean Mullenweg has unlimited legal authority. It means the practical cost of removing him could extend beyond changing the executive listed on an organizational chart.

Automattic operates WordPress.com, WooCommerce, Jetpack, Tumblr, and other services. Its products sit beside the open-source WordPress project, which supports websites operated by businesses, publishers, agencies, and individual creators.

WordPress.org distributes software, themes, plugins, and updates used throughout that wider community. Although Automattic and WordPress.org are not interchangeable, Mullenweg’s roles connect their public narratives.

This structure can work when leadership, corporate strategy, and project governance move together. It becomes harder to understand when the company’s board and its founder openly disagree.

The failed leave exposed that weakness. Directors apparently possessed enough authority to approve a temporary removal, but they did not produce a stable transfer of control.

Mullenweg’s return therefore represents more than personal resilience. It shows that formal board action was insufficient to separate operational control from founder influence.

Supporters can argue that this influence protects long-term commitments. Founders often resist short-term demands and preserve product missions that professional managers might dilute.

WordPress Executive Director Mary Hubbard publicly welcomed Mullenweg’s return, according to reporting on his control claim. Other supporters posted messages that Mullenweg shared through his social accounts.

That support matters because WordPress depends on contributors, businesses, and users who view Mullenweg as a central steward. Removing him without an agreed transition could have produced its own governance crisis.

Critics see the opposite risk. If a board cannot remove a founder without losing control of internal operations, oversight becomes difficult precisely when it matters most.

The concern is not limited to executive succession. It affects legal risk, employee confidence, commercial negotiations, and the perceived independence of decisions involving shared infrastructure.

A plugin developer offers a practical example. That developer might depend on WordPress.org distribution while selling products to customers hosted by several competing companies.

The developer needs stable rules for repository access, security updates, and dispute resolution. Leadership uncertainty becomes a business risk when corporate conflicts appear capable of affecting those shared channels.

Agencies face a similar problem. They recommend hosting, plugins, and maintenance arrangements that must remain dependable for years. They cannot easily explain sudden institutional reversals to clients demanding continuity.

The Matt Mullenweg CEO return resolved the narrow leadership question. It also made the structural question harder to ignore: where does enforceable authority sit when Automattic’s founder and board disagree?

The WP Engine Conflict Raised the Stakes

The attempted removal arrived after two years of disputes that already tested the boundary between corporate competition and open-source stewardship.

Automattic has not said that the WP Engine litigation caused the board vote. Any direct connection remains unverified and should not be presented as the reason for Mullenweg’s leave.

The conflict still forms essential context. It shows the legal and reputational environment in which Automattic’s directors attempted to change leadership.

The dispute became public in September 2024. Mullenweg accused WP Engine of benefiting from WordPress without contributing enough to the open-source project.

Automattic also challenged WP Engine’s use of WordPress-related trademarks. WP Engine denied wrongdoing and sued Automattic, Mullenweg, and related parties.

A federal judge later issued a preliminary injunction limiting interference with WP Engine’s access to WordPress.org resources. A preliminary injunction preserves conditions during litigation and does not represent a final judgment on every claim.

The injunction order showed that courts were willing to scrutinize decisions affecting access to infrastructure used by a commercial rival.

The litigation continued through discovery in 2026. Discovery is the court-supervised exchange of evidence before trial, including documents, messages, and testimony.

In June, the court ordered production related to several workplace platforms and addressed multiple discovery disputes. Those proceedings kept attention on Automattic’s internal decision-making and document practices.

Automattic has rejected WP Engine’s allegations. In August 2026, the company said it had reviewed more than 1.5 million documents and forensically imaged five of Mullenweg’s devices.

Those figures come from Automattic’s litigation response, rather than an independent audit. WP Engine has presented a sharply different interpretation of the discovery record.

That conflict gives Automattic’s board a demanding risk-management assignment. Directors must oversee the company while litigation examines decisions closely associated with its founder and CEO.

The board also must separate three questions that public debate often merges. Who controls Automattic, who governs WordPress.org, and who represents the broader WordPress community are not identical issues.

WP Engine is the relevant opposing commercial force, but it is not the primary opponent in this leadership story. The decisive struggle occurred between Mullenweg’s founder power and Automattic’s board authority.

The lawsuit nevertheless magnifies the consequences. Another unilateral action affecting a rival, contributor, or shared resource could create new legal or reputational exposure.

Supporters of Mullenweg argue that aggressive defense protects the WordPress name and encourages companies to contribute more. That position treats commercial enforcement as part of sustaining open source.

Critics argue that concentrated control lets one leader combine community authority with corporate leverage. They worry that participants lack an independent appeal route when disputes involve Mullenweg or Automattic.

Neither position resolves the current governance problem. Even a justified corporate strategy needs a board capable of reviewing it, challenging it, and changing it when necessary.

If Automattic’s directors believed leadership intervention was required, their reversal demands an explanation. If they concluded the intervention was mistaken, the original vote demands one too.

Employees and WordPress Businesses Need Stability

The largest near-term cost is uncertainty for people who must make decisions before Automattic explains what happened.

Automattic entered this episode after a significant workforce reduction. In April 2025, the company announced that it would cut approximately 16 percent of its employees.

The company said revenue continued to grow, while productivity and profitability required improvement. Its restructuring announcement described a global workforce operating across 90 countries.

Leadership instability can compound the effects of such restructuring. Employees asked to work across a distributed organization depend heavily on clear written decisions, access controls, and trusted management channels.

A public confrontation inside Slack undermines those mechanisms. It turns an internal collaboration system into the visible arena for a dispute over corporate authority.

Employees then face practical questions. They need to know whose instructions remain valid, who controls personnel decisions, and whether leadership messages reflect durable board policy.

Some employees reportedly expressed relief after the initial leave. Other executives and WordPress figures publicly supported Mullenweg’s return. Those reactions show division, but they do not establish how the broader workforce feels.

Anonymous employee comments deserve caution. Workers often need anonymity during executive conflicts, yet outsiders cannot independently measure how representative those comments are.

The responsible conclusion is narrower. Automattic’s workforce received contradictory leadership signals during a period lasting roughly three days.

Commercial users also need stability, even if the executive dispute never interrupts a product. Enterprises assess vendor risk through continuity, security practices, contractual accountability, and succession planning.

A company can maintain service availability while its governance weakens. Customers might not see an immediate outage, but they can still adjust procurement decisions or demand stronger contractual protections.

WordPress agencies operate across an even wider dependency chain. Their clients use hosting companies, payment systems, security products, themes, and plugins maintained by separate organizations.

When disputes affect the institutions coordinating that network, agencies absorb the communication burden. They must explain which developments are operationally relevant and which remain executive drama.

Open-source contributors face a different calculation. Many contribute because they trust the project’s norms, not because they have a commercial contract with Automattic.

Their confidence depends on predictable decision-making and credible separation between community stewardship and corporate conflict. Confusion between those roles can discourage participation without producing an easily measured event.

The skeptical view should not overreach. There is no verified evidence that the three-day leadership fight disrupted WordPress.com service, plugin updates, or WooCommerce transactions.

There is also no public evidence that customers left because of it. Claims about mass departures, immediate product damage, or a collapse in contributor activity would be premature.

The risk lies in accumulated uncertainty. Litigation, layoffs, ecosystem disputes, and a failed board intervention can reinforce each other in stakeholder decisions.

One controversy rarely determines whether a developer, agency, or enterprise leaves a platform. A pattern of unpredictable governance can influence the next renewal, migration, or contribution decision.

Automattic can reduce that risk through specific disclosures. It can clarify the board’s composition, describe any updated governance process, and explain who can authorize decisions affecting shared WordPress infrastructure.

Without such steps, stakeholders must infer stability from the same board that changed its position within three days.

What the Matt Mullenweg CEO Return Leaves Unresolved

The next evidence must come from governance changes, leadership continuity, and observable confidence across the WordPress economy.

The first signal to watch is Automattic’s board composition. Any resignation, appointment, or revised committee structure would show how the company absorbed the failed removal.

This signal matters because directors initiated the leave. A substantially changed board would strengthen the conclusion that Mullenweg consolidated control after defeating an internal challenge.

A stable board with clearly described safeguards would point elsewhere. It would suggest that the parties negotiated a working arrangement, even if Automattic never releases every private detail.

The second signal is the status of Davies and other senior executives involved in the transition. Davies briefly received the interim CEO role and the board’s declared confidence.

His continued service would indicate that Automattic retained at least part of the leadership team associated with the intervention. A departure would deepen questions about whether the reversal removed internal checks.

The same test applies to other directors and executives linked to the vote. Titles alone will not settle the issue, but a series of departures would reveal more than a generic unity statement.

The third signal is how Automattic behaves during its continuing legal and ecosystem disputes. Stakeholders should watch decisions involving WP Engine, WordPress.org access, trademarks, plugins, and community governance.

A more documented and institutionally reviewed process would weaken concerns about concentrated founder authority. Another public confrontation driven through personal accounts or shared infrastructure would strengthen them.

Court filings can also provide evidence. They might reveal changes in decision-making, document retention, settlement strategy, or the division between Mullenweg’s personal roles and Automattic’s corporate interests.

None of these signals requires access to private deliberations. Board disclosures, executive changes, court records, and public operational decisions can establish whether the company adopted meaningful checks.

The Matt Mullenweg CEO return is therefore not the end of the story. It is the point at which a temporary leadership dispute becomes a continuing governance test.

Mullenweg demonstrated that his influence extends beyond a title conferred by directors. Automattic’s board must now demonstrate that its oversight extends beyond statements issued after a reversal.

For WordPress users, the most useful response is neither panic nor indifference. Businesses should review operational dependencies, update contingency plans, and distinguish Automattic services from community infrastructure.

Developers should watch whether repository rules and enforcement decisions become clearer. Agencies should track changes that affect client hosting, plugin distribution, or long-term platform commitments.

The final judgment should rest on what Automattic does next. Will it document stable authority, preserve independent oversight, and reduce conflicts across its corporate and open-source roles?

Those actions will determine whether the three-day fight becomes a contained board dispute or evidence of a deeper weakness in WordPress governance.