- Published
- Updated
- 11 min read

TL;DR: The WP Engine lawsuit against Automattic and Matt Mullenweg is still alive. On September 24, 2026, the judge revived WP Engine's antitrust claims, dismissed its computer extortion claim, and kept most of Automattic's counterclaims. For a business on WordPress, the useful lesson is governance: know who controls your platform, and keep your content, domain and hosting portable.
Correction, October 2026: the first version of this note gave the hearing date as Wednesday, June 4, and quoted market share, valuation, staffing and migration figures we could not trace to a primary source; those are corrected or removed.
If your business runs on WordPress, you have been making a governance bet every day. Most owners never think of it that way. The WP Engine lawsuit is the clearest look we have had at what that bet actually is, because the court record now spells out who owns what.
I am not a lawyer, and this is not a prediction of how the case ends. It is a plain read of what the court has decided so far, what WP Engine alleges, and what any owner on WordPress can check this week.
What is the WP Engine lawsuit about?
WP Engine is one of the larger WordPress hosting companies. Automattic is the company Matt Mullenweg founded, and Mullenweg co-founded WordPress itself. In late 2024 the two companies went from a public argument to federal court, in WPEngine, Inc. v. Automattic Inc., case 4:24-cv-06917 in the Northern District of California.
The short version of the WP Engine lawsuit: WP Engine says Automattic and Mullenweg demanded payment framed as a trademark license, then cut WP Engine off from WordPress.org resources when it refused. Automattic and Mullenweg deny the claims and have filed counterclaims of their own, including trademark claims. Everything below that comes from WP Engine's complaint is an allegation, not a finding.
Who owns the pieces of WordPress?
This is the part most owners never look at. WordPress the software is open source. Its license is "the GPLv2 (or later) from the Free Software Foundation" (WordPress.org (opens in a new tab)). Anyone can run it, copy it and change it.
The website most people think of as "WordPress," wordpress.org, with its plugin and theme directories, is a different thing. In the December 2024 order, the court described Mullenweg, citing his own declaration, as "the individual owner of the domain name wordpress.org, the manager of the wordpress.org website, and a founding director of the WordPress Foundation." The same order notes that "The foundation owns three WordPress trademarks." (U.S. District Court, N.D. Cal., order of December 10, 2024 (opens in a new tab))
Read that slowly. The code is shared. The front door most sites use to get plugins, themes and updates is controlled by one person. That is not a scandal on its own. It is a fact the WP Engine lawsuit made public, and worth knowing before you build a business on top of it.
What did the court order in 2024?
Early in the WP Engine lawsuit, the company asked for a preliminary injunction, and on December 10, 2024 the court granted it. Within 72 hours, Automattic and Mullenweg were ordered to restore WP Engine's access to wordpress.org as it stood on September 20, 2024. The order also required "removing the checkbox at login.wordpress.org that Defendants added on or about October 8, 2024 asking users to confirm that they are 'not affiliated with WP Engine in any way, financially or otherwise'" and returning WP Engine's control of its Advanced Custom Fields plugin listing. (U.S. District Court, N.D. Cal. (opens in a new tab))
That plugin matters to ordinary site owners. In weighing the public interest, the court wrote: "Over two million websites run the ACF plugin Mullenweg allegedly tampered with, and those users rely on the stability of the plugin, and WordPress more broadly, to operate their websites, run their businesses, and go about their day online." (U.S. District Court, N.D. Cal. (opens in a new tab))
What happened to the plugin?
According to WP Engine's declarant, quoted in that order, on October 12, 2024 the plugin's name on wordpress.org was changed from "Advanced Custom Fields" to "Secure Custom Fields," its listed author was changed to "WordPress.org," and many users were switched to the new plugin through an update prompt. Mullenweg's declaration says the WordPress security team found WP Engine's patch for a vulnerability incomplete and forked the plugin to finish it. The court did not decide who was right on the merits; it ordered the listing restored while the case runs.
For an owner, the detail that matters is the mechanism. A plugin your site depends on can change hands through the same update button you press every week.
What did the court decide on September 24, 2026?
The key motions in the WP Engine lawsuit were decided in a written order dated September 24, 2026. Here is what that order did.
The antitrust claims came back
WP Engine claims monopolization, attempted monopolization and illegal tying. The court had dismissed earlier versions of those claims in 2025. This time it wrote: "The Court previously dismissed WPEngine's antitrust claims and departs from its prior order, now finding WPEngine's antitrust claims viable." The motion to dismiss was "DENIED as to Counts 11-14." (U.S. District Court, N.D. Cal., order of September 24, 2026 (opens in a new tab))
The extortion claim did not
WP Engine's claim under the Computer Fraud and Abuse Act, which treated the demands as computer extortion, was "DISMISSED WITHOUT LEAVE TO AMEND." On the other side, WP Engine's motion to dismiss Automattic's counterclaims was denied except for one false advertising portion, and the trademark counterclaims were dismissed only "to the extent Automattic and Mullenweg seek to assert those claims in their own right." (U.S. District Court, N.D. Cal. (opens in a new tab)) Search Engine Journal's summary of the same order agrees: the antitrust claims continue, the computer extortion claim is out, and Automattic's counterclaims survived at least in part (Search Engine Journal (opens in a new tab)).
Surviving a motion to dismiss is not winning. It means the judge found the claims plausible enough to go forward, taking the complaint's allegations as true for now. The WP Engine lawsuit still has evidence, summary judgment and possibly a trial ahead.
What WP Engine alleges about royalties
The order summarizes the complaint in the WP Engine lawsuit, and these are allegations, not findings. WP Engine alleges that "Defendants targeted multi-million-dollar deals with at least 11 competitors," and that internal correspondence states, "if they don't take the carrot we'll give them the stick." It also alleges Mullenweg admitted "the demand for 8% of WPEngine's revenue as purported license royalty was based on WPE[ngine]'s income." (U.S. District Court, N.D. Cal. (opens in a new tab)) Automattic disputes WP Engine's account, and none of it has been proven.
Is WordPress losing market share?
Some, on one well-known measure. W3Techs, which surveys the top sites on the web daily, reports WordPress is "used by 58.2% of all the websites whose content management system we know. This is 39.5% of all websites." (W3Techs, October 31, 2026 (opens in a new tab)) Its yearly history shows WordPress at 43.0% of all websites on January 1, 2026 and 39.5% on October 31, 2026. (W3Techs yearly trends (opens in a new tab))
Two cautions before anyone reads that as a collapse. The same table shows the share of sites with no detectable content management system rising from 28.6% to 32.1% over the same months, so part of the change may be in what the survey can detect. And nothing in the data tells you why sites moved. I would not tie the drop to the WP Engine lawsuit without better evidence. At 39.5%, WordPress is still an enormous install base with no single replacement at that scale.
Why does platform governance matter for a small business?
When you pick a platform, you usually compare features, templates and price. Almost nobody asks who makes the decisions, how they get made, and what happens when the people in charge want something different from you. That is governance, and it is a separate risk from whether the software works.
WordPress is not the first open source fight
The WP Engine lawsuit is not the first fight over who controls open source, though the shape is different. In August 2023, HashiCorp announced "HashiCorp adopts the Business Source License" for Terraform and its other products (HashiCorp (opens in a new tab)). A month later the Linux Foundation announced OpenTofu as an open source alternative built from the earlier license (Linux Foundation (opens in a new tab)). When Redis changed its license in 2024, the Linux Foundation launched Valkey, which "will continue development on Redis 7.2.4" under an open license (Linux Foundation (opens in a new tab)).
The pattern: a company that controls an important open source project changes the terms, and the community forks to keep the old ones. WordPress's situation is different, since the code's license has not changed. What is in dispute is access to the shared infrastructure around it, which is exactly the part one person controls. Our note on open source tools covers how we weigh this when we pick software for clients.
Lock-in lives in the services around the code
This is the real lesson of the WP Engine lawsuit for a business owner. Open source protects your right to run the code. It does not protect your access to the plugin directory, the update channel, a specific plugin's maintainer, or your host. That gap is what vendor lock-in looks like in practice. My wife Amelia, Kief Studio's co-founder and CEO, wrote a good owner's checklist on who owns the site, the host and the login (opens in a new tab), and I covered what the GPL actually allows for commercial use (opens in a new tab) on my own site.
Should you leave WordPress because of the WP Engine lawsuit?
Probably not, and certainly not in a panic. A move has real costs. Google's own guidance on moving a site warns: "Expect temporary fluctuation in site ranking during the move," and says that for medium-sized sites "it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones." (Google Search Central (opens in a new tab))
Staying put through the WP Engine lawsuit has costs too, but they only show up when a governance decision lands on your site. The smart play is to know what you are betting on and to have an exit you could use if you ever had to. We wrote about a related shift in WordPress giving AI the publish button, and about the other side of the trade in website builders that are easy to join and expensive to leave.
Three checks to run this week
- Export your content. In WordPress, Tools, Export creates "an XML file" in the WordPress eXtended RSS format that "will contain your posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies, and users" (WordPress.org documentation (opens in a new tab)). Download it, open it, and confirm your pages are actually in it. Note what is not on that list: plugin settings and theme design have to be rebuilt.
- List the plugins your site cannot live without. For each, write down who maintains it and where its updates come from. The WP Engine lawsuit showed that a plugin's listing can change hands. If a forms or booking plugin vanished tomorrow, you should know which one hurts.
- Separate your hosting from your platform politics. Know who your host is, whether your backups live outside it, and whether your domain is registered in your own name. If one company controls your platform, your hosting and your domain, that is one point of failure.
None of this depends on how the WP Engine lawsuit ends, and none of it requires anything dramatic. It turns a bet you did not know you were making into one you chose.
This article is general information, not legal advice. Kief Studio is not a law firm, and reading it does not create an attorney-client relationship. Laws and regulations change, so check the current text and talk with a licensed Massachusetts attorney about your situation.
Frequently asked questions
What is the WP Engine lawsuit?
WPEngine, Inc. v. Automattic Inc. is a federal case in the Northern District of California. WP Engine claims Automattic and Matt Mullenweg used trademark demands and wordpress.org access against it. Automattic denies this and has counterclaims, including trademark claims.
What did the judge rule in September 2026?
On September 24, 2026, the court let WP Engine's four antitrust claims go forward, dismissed its Computer Fraud and Abuse Act claim without leave to amend, and kept most of Automattic's counterclaims. Nothing has been decided on the merits yet.
Who owns wordpress.org?
The December 2024 order in the WP Engine lawsuit, citing Mullenweg's own declaration, describes him as the individual owner of the wordpress.org domain and manager of the site. The WordPress Foundation owns three WordPress trademarks.
Is my WordPress site at risk because of the lawsuit?
Not directly. The WP Engine lawsuit is a dispute between companies, and the software is GPL licensed and keeps running. The risk is indirect: plugin listings, update channels and host access depend on parties in the dispute. Keep an export, know your key plugins and keep your domain in your name.
How much of the web uses WordPress now?
W3Techs reported 39.5% of all websites and 58.2% of sites with a known CMS on October 31, 2026, down from 43.0% of all websites on January 1, 2026.
Should I move my business off WordPress?
Not because of the WP Engine lawsuit alone; it may run for years. A move costs time and can cause temporary ranking changes. Make your content portable and your hosting separable first, then decide on the merits of your site.
Where we fit
Kief Studio is in Shrewsbury, and the WP Engine lawsuit shows the kind of risk our managed website operations work takes off an owner's desk: we take over hosting, domain and security on dedicated machines, keep the site current, and watch uptime, speed and security. Some of our client relationships go back 13+ years.
When a site is ready to stop depending on someone else's plugin directory, our cloud infrastructure and custom web application work moves it onto dedicated infrastructure written down as code, so the environment can be rebuilt somewhere else and the data stays yours. No shared hosting.
First conversation is free. No commitment.
Tell us what your site runs on and we will help you map your exposure




