Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Automattic and other WordPress-related parties filed a 162-page answer and set of counterclaims against WP Engine on October 23, 2025, in the companies’ ongoing federal lawsuit. They accuse WP Engine of trademark infringement, deceptive branding, false advertising and unfair competition involving WordPress, WooCommerce and Woo. Those are allegations, not findings: WP Engine disputes them and says its references to WordPress describe compatibility with open-source software and qualify as fair use.
The practical question is where a hosting company’s ordinary software-compatibility references end and branding that could imply official affiliation begins. The filing raises that question; it does not, by itself, change customer service availability, require a migration or establish that any customer was misled.
What Automattic filed
The filing was docketed as Document 195 in WP Engine, Inc. v. Automattic Inc. et al., Case No. 3:24-cv-06917-AMO, in the U.S. District Court for the Northern District of California. It combines WP Engine’s answer to the defendants’ allegations and defenses with affirmative defenses and seven claims for relief by the WordPress parties. Its demand seeks damages, profits, enhanced remedies, injunctive relief, attorneys’ fees and other relief; a request is not an award.
The complaint is best understood as an expansion of WP Engine’s existing lawsuit, not a court decision. The case concerns a commercial dispute among distinct organizations, not a lawsuit by “WordPress” as a single entity. The filing is available at Automattic’s counterclaims PDF.
#1 Best Overall
Who is involved
- WP Engine is the managed WordPress hosting company and original plaintiff.
- Automattic is the company behind WordPress.com and other WordPress-related businesses; CEO and WordPress co-founder Matt Mullenweg is also a defendant in the original case.
- The WordPress Foundation is identified in the filing as owner and registrant of the WordPress marks.
- WooCommerce is identified as owner and registrant of the WooCommerce marks. The filing also addresses the Woo mark.
- Silver Lake, WP Engine’s private-equity owner, appears in Automattic’s account of WP Engine’s business strategy. The valuation narrative is an allegation in the filing, not independently established here.
WordPress the open-source software project, WordPress.org, WordPress.com, Automattic and the WordPress Foundation are not interchangeable names for one legal entity.
What branding Automattic challenges
Automattic’s theory is that WP Engine’s use of the marks went beyond neutral descriptions of compatibility and could lead customers to think the company was official, endorsed or more closely affiliated with the WordPress project than it was. The counterclaims point to examples including:
| Example cited in the filing | Automattic’s alleged concern |
|---|---|
| “The WordPress Technology Company” | Could suggest a special or official relationship with WordPress. |
| “Headless WordPress,” “Essential WordPress,” “Core WordPress” and “Enterprise WordPress” | Product branding allegedly trades on the WordPress mark rather than simply identifying supported software. |
| “WordPress Engine,” allegedly used by agency partners | Partner language could reinforce an impression that WP Engine is an official WordPress entity. |
| References to “WooCommerce Hosting” | Use of WooCommerce branding is challenged as part of the alleged broader pattern. |
Automattic characterizes the examples as part of a wider branding and search-marketing strategy. Whether any specific use is confusing depends on its context: a service description, product name, logo, page title, advertisement or partner statement may convey different things. The mere appearance of the word “WordPress” does not automatically establish infringement.
The seven legal claims in plain English
The counterclaims invoke federal, California statutory and common-law theories. Their factual and legal elements differ, and filing them does not mean the court has accepted them.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- Federal trademark infringement under 15 U.S.C. § 1114(1): alleges unauthorized use of registered marks in a way that violates trademark rights.
- False advertising, false designation of origin and unfair competition under 15 U.S.C. § 1125(a): challenges alleged misrepresentations about the source, sponsorship, approval or qualities of services.
- Common-law trademark infringement: asserts related trademark rights under common law.
- Federal trademark dilution: alleges harm to the distinctiveness of the WordPress marks, a theory distinct from ordinary consumer-confusion claims.
- California trademark dilution under California Business and Professions Code § 14247.
- California statutory unfair competition under California Business and Professions Code § 17200 et seq.
- Common-law unfair competition: alleges unfair commercial conduct under state common law.
Trademark disputes commonly examine the marks, the relationship between the services, how and where a mark appears, consumer perception and evidence of confusion. A reference that accurately identifies software a service supports may be treated differently from a company name or presentation that implies sponsorship or authorization. WP Engine’s fair-use position therefore does not settle whether every challenged use was permissible.
What Automattic alleges about contributions and customers
Automattic says WP Engine promoted a commitment to devote 5% of its resources to supporting WordPress but did not meet that commitment, and it characterizes statements about WP Engine’s contributions as misleading. The counterclaims do not turn that accusation into an established fact. The legal significance would depend in part on what was said, who said it, the evidence of actual contributions and whether the statement mattered to customer decisions.
The filing also alleges that WP Engine removed or degraded features, including the ability to restore earlier versions of posts and pages; that this prompted customer confusion or frustration; and that some customers sought technical help from Automattic for WP Engine-related issues. Automattic uses these allegations to argue that WP Engine benefited from the WordPress name while operating independently and harming the WordPress brand. They do not, on their own, prove trademark infringement.
The filing’s allegations about business value
Automattic alleges that WP Engine used WordPress’s reputation to mask business weaknesses and inflate its value ahead of a potential sale. It also claims Silver Lake sought a valuation above $2 billion and attributes WP Engine’s business problems to internal management and cost-cutting rather than Automattic’s conduct. These are Automattic’s assertions and theory of motive in the counterclaims, not verified valuation findings or a court’s conclusion.
Free tools Windows power users keep installed
One-click scans. No signup required.
What WP Engine says in response
WP Engine says its use of the WordPress trademark identifies compatibility with open-source software, reflects longstanding industry practice and is protected by fair-use principles. It called the counterclaims baseless and said it would defend them. Its public response and litigation updates are on WP Engine’s litigation-status page.
Rank #4
That argument addresses the context and purpose of its mark use; it does not mean that every slogan, product name or partner description is necessarily non-confusing. The dispute is over how the challenged uses would be understood, not simply whether WordPress is open source.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How the counterclaims fit into the lawsuit
- October 2024: WP Engine filed the original federal lawsuit against Automattic and Mullenweg.
- December 10, 2024: The court entered a preliminary-injunction order after WP Engine sought relief amid a dispute over access, interference and WordPress-related services.
- October 23, 2025: Automattic and the WordPress parties filed their answer, affirmative defenses and counterclaims.
- October 24, 2025: WP Engine publicly rejected the claims and asserted fair use.
- 2026: Discovery disputes continued, including questions about evidence and the timing of alleged trademark misuse.
The case chronology is listed on the federal docket index. A June 5, 2026 order addressed requests for internal communications held on third-party platforms including Asana, Jiro, Figma and Miro, and required defendants to identify an earliest date for alleged trademark misuse if they intended to rely on alternative dates at trial. See the June 5 discovery order.
WP Engine’s status page said discovery concluded May 14, 2026, hearings on discovery issues occurred in late May, and arguments on motions to dismiss were scheduled for June 25, 2026. The available materials do not establish the outcome of that hearing, so they do not show whether the counterclaims survived or were dismissed. The case remains distinct from a final liability determination.
Best Value
What this means for WordPress users and agencies
The counterclaims do not establish that WP Engine hosting is illegal, technically incompatible, unavailable or unsafe, and they do not themselves require customers to move sites. Nor do they automatically change hosting contracts, plugin access or trademark permissions. The legal dispute concerns alleged branding, advertising and business conduct; the filing alone is not an operational notice to customers.
Businesses choosing a host can treat the lawsuit as one factor in vendor due diligence rather than as proof of a service defect. Relevant practical questions include backup and restore controls, migration assistance, staging, WooCommerce support, agency tools, enterprise commitments, infrastructure and compliance needs, and how easily a site can be moved. Agencies should also distinguish descriptive compatibility language from branding that might imply endorsement when naming or promoting a service.
What happens next depends on the court’s handling of motions and evidence, and potentially settlement, trial or final judgment. The central unresolved issue remains whether WP Engine’s particular uses communicated compatibility or crossed into misleading affiliation, assessed in context.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems
