In late September, Automattic CEO and WordPress cofounder Matt Mullenweg started a public dispute with the hosting provider WP Engine, calling the company “a cancer to WordPress.” He accused WP Engine of not contributing enough to the WordPress ecosystem and profiting off of trademark confusion. As a result, WP Engine was blocked from accessing WordPress.org’s servers.
Automattic has since sent a cease and desist order to WP Engine to stop it from using its trademarks, while WP Engine has followed up with a lawsuit that accuses Automattic and Mullenweg of extortion.
The series of events set off a public battle that calls into question the boundaries between WordPress.com host Automattic, the WordPress open-source project, and the nonprofit that’s behind it.
Here’s all the latest news so far.
Nov 7
WordPress.com’s owner launched a tracker for sites leaving WP Engine.As spotted by @DuaneStorey on X, the “WP Engine Tracker” says more than 16,000 sites stopped using WP Engine since late September, which is when WordPress.com parent company Automattic started its public campaign against the third-party hosting service.
Meanwhile, Automattic’s response to WP Engine’s lawsuit claimed the company “failed to plausibly allege specific financial harm.”
Oct 31
WordPress cofounder asks court to dismiss WP Engine’s lawsuit
WordPress cofounder Matt Mullenweg and his company Automattic have asked a court to dismiss WP Engine’s lawsuit accusing them of libel and extortion. In a filing on Wednesday, Mullenweg argues that WP Engine is conjuring claims “out of legal thin air,” while alleging it continues to use the WordPress trademark “in unauthorized ways.”
Read Article >Earlier this month, the third-party WordPress hosting service WP Engine filed a lawsuit against Automattic and Mullenweg after the executive embarked on a “scorched earth nuclear” campaign against it. In addition to accusing WP Engine of trademark infringement, Mullenweg claimed the service doesn’t contribute enough to the open-source WordPress.org project, which Mullenweg also controls. WordPress.org also cut off WP Engine’s access to its resources and later took over one of its most popular plugins.
Oct 29
WordPress reportedly asks WordCamp organizers to delete posts that “don’t align” with its views.Screenshots shared on X show emails from WordPress.com parent company Automattic asking the owners of WordCamp Sydney — a community-organized WordPress conference — to remove posts related to WP Engine.
Meanwhile, a separate email from the company requests that event organizers share “all active social media accounts” login credentials with Automattic to ensure “safe storage for all future events.”
Oct 23
“WordPress.org is not WordPress.”The attorneys for WordPress co-founder Matt Mullenweg make that very clear in a legal response to WP Engine’s lawsuit. The response also blames WP Engine for relying on WordPress.org, “a website owned and run by Defendant Matt Mullenweg individually:”
WP Engine, a private equity-backed company, made the unilateral decision, at its own risk, to build a multi-billion dollar business around Mr. Mullenweg’s website. In doing so, WP Engine gambled for the sake of profit that Mr. Mullenweg would continue to maintain open access to his website for free. That was their choice.
Oct 18
WP Engine asks court to stop Matt Mullenweg from blocking access to WordPress resources
WP Engine is asking a court to put a stop to Automattic CEO Matt Mullenweg’s public campaign against the company. In a motion for a preliminary injunction filed against Automattic and Mullenweg on Friday, the third-party hosting platform requests that the court restore its access to WordPress resources and allow it to regain control of its plugin that had been taken over.
Read Article >In the filing, WP Engine claims it’s facing “multiple forms of immediate irreparable harm” as a result of Mullenweg and Automattic’s actions, including “loss of customers, market share and goodwill.” The company also says it saw a 14 percent increase in cancellation requests from September 26th to the 30th — just days after Mullenweg called WP Engine a “cancer” to the WordPress community.
Oct 17
Automattic offered employees another chance to quit over WordPress drama
Automattic CEO Matt Mullenweg offered a second buyout round to employees who don’t agree with his actions, according to a report from 404 Media. In a message to employees seen by the outlet, Mullenweg gave employees until October 17th to decide whether they would resign in exchange for nine months of pay.
Read Article >“New alignment offer: I guess some people were sad they missed the last window. Some have been leaking to the press and ex-employees,” Mullenweg wrote in the message seen by 404 Media. “You have until 00:00 UTC Oct 17 (-4 hours) to DM me the words, ‘I resign and would like to take the 9-month buy-out offer’ You don’t have to say any reason, or anything else. I will reply ‘Thank you.’ Automattic will accept your resignation.”
Oct 14
Matt Mullenweg responds to David Heinemeier Hansson in their “respectful debate.”I used quotes there because Mullenweg’s new blog (post deleted, so here’s an archive) includes statements like:
David, perhaps it would be good to explore with a therapist or coach why you keep having these great ideas but cannot scale them beyond a handful of niche customers. I will give full credit and respect. 37signals inspired tons of what Automattic does! We’re now half a billion in revenue. Why are you still so small?
DHH posted on X in reply: “Maybe I’m supposed to get mad at this, but instead I just get sad.”
Update: Added archive link to deleted blog post.
Response to DHH[Matt Mullenweg]
Oct 12
WordPress.org’s latest move involves taking control of a WP Engine plugin
WordPress.org has taken over a popular WP Engine plugin in order “to remove commercial upsells and fix a security problem,” WordPress cofounder and Automattic CEO Matt Mullenweg announced today. This “minimal” update, which he labels a fork of the Advanced Custom Fields (ACF) plugin, is now called “Secure Custom Fields.”
Read Article >It’s not clear what security problem Mullenweg is referring to in the post. He writes that he’s “invoking point 18 of the plugin directory guidelines,” in which the WordPress team reserves several rights, including removing a plugin, or changing it “without developer consent.” Mullenweg explains that the move has to do with WP Engine’s recently-filed lawsuit against him and Automattic.
Oct 10
“Automattic is completely out of line, and the potential damage to the open source world extends far beyond WordPress,”writes David Heinemeier Hansson, the CTO at 37signals and creator of the open-source framework Ruby on Rails.
DHH says it “occasionally irks” him to see companies failing to contribute to Ruby on Rails, but that’s the rules:
None of the major licenses, however, say anything close to “it’s free but only until the project owners deem you too successful and then you’ll have to pay 8% of your revenues to support the project”. That’s a completely bonkers and arbitrary standard based in the rule of spite, not law.
Automattic is doing open source dirty[world.hey.com]
Oct 9
The latest volley in the WordPress beef:WordPress.org’s contributor login page now requires users to certify that they are “not affiliated with WP Engine in any way, financially or otherwise.” 404 Media spotted the new checkbox.
Oct 4
Matt Mullenweg: ‘WordPress.org just belongs to me’
Over the past several weeks, WordPress cofounder Matt Mullenweg has made one thing exceedingly clear: he’s in charge of WordPress’ future.
Read Article >Mullenweg heads up WordPress.com and its parent company, Automattic. He owns the WordPress.org project, and he even leads the nonprofit foundation that controls the WordPress trademark. To the outside observer, these might appear to be independent organizations, all separately designed around the WordPress open-source project. But as he wages a battle against WP Engine, a third-party WordPress hosting service, Mullenweg has muddied the boundaries between three essential entities that lead a sprawling ecosystem powering almost half of the web.
Oct 4
WordPress cofounder is paying employees to leave if they disagree with him
Automattic CEO Matt Mullenweg offered employees $30,000, or six months of salary (whichever is higher), to leave the company if they didn’t agree with his battle against WP Engine. In an update on Thursday night, Mullenweg said 159 people, making up 8.4 percent of the company, took the offer.
Read Article >Automattic, which is in charge of WordPress.com and its commercial services, has been involved in a public dispute with WP Engine after Mullenweg called the third-party hosting service a “cancer” to the WordPress community and banned it from accessing WordPress.org.
Oct 3
The ‘WordPress’ fight is now a lawsuit
The WP Engine web hosting service is suing WordPress co-founder Matt Mullenweg and Automattic for alleged libel and attempted extortion, following a public spat over the WordPress trademark and open-source project. In the federal lawsuit filed on Wednesday, WP Engine accuses both Automattic and its CEO Mullenweg of “abuse of power, extortion, and greed,” and said it seeks to prevent them from inflicting further harm against WP Engine and the WordPress community.
Read Article >WP Engine is a major rival to WordPress.com, with more than 200,000 websites using the service. Mullenweg runs Automattic, which owns WordPress.com, a company that sells a hosted version of the open-source WordPress software — just like WP Engine.
Oct 2
Automattic demanded a cut of WP Engine’s revenue before starting WordPress battle
Automattic, the parent company of WordPress.com, asked rival hosting service WP Engine to hand over 8 percent of its revenue each month before igniting a very public battle over what you can and can’t do with an open-source project.
Read Article >On Wednesday, Automattic published the proposed deal that it sent to WP Engine on September 20th. The proposal lays out a seven-year agreement that gives WP Engine the right to use the WordPress trademark in exchange for a hefty payment. The 8 percent cut could either be paid as a royalty fee to Automattic or as salaries for WP Engine employees who would contribute to the WordPress.org open-source project.
Sep 27
The messy WordPress drama, explained
WordPress is essentially internet infrastructure. It’s widely used, generally stable, and doesn’t tend to generate many splashy headlines as a result.
Read Article >But over the last week, the WordPress community has swept up into a battle over the ethos of the platform. Last week, WordPress cofounder Matt Mullenweg came out with a harsh attack on WP Engine, a major WordPress hosting provider, calling the company a “cancer” to the community. The statement has cracked open a public debate surrounding how profit-driven companies can and can’t use open-source software — and if they’re obligated to contribute something to the projects they use in return.
Sep 23
WordPress co-founder Matt Mullenweg calls WP Engine a “cancer.”In a post on his blog, Mullenweg called out the rival hosting service — which is built on WordPress — for “strip-mining the WordPress ecosystem” by disabling certain features like revisions. “What WP Engine gives you is not WordPress,” he says.
WP Engine has since responded the post, saying “recent attacks against us are unfair and untrue and clearly designed to harm our business.”