Automattic Accuses WP Engine of Misleading Practices ![rw-book-cover](https://www.techzine.eu/wp-content/uploads/2025/10/shutterstock_788198215.jpg) ## Metadata - Author: [[Mels Dees]] - Full Title: Automattic Accuses WP Engine of Misleading Practices - Category: #articles - Document Note: --- tags: [WordPress, Automattic, WP Engine] author: Mels Dees source: Techzine Europe reference: [https://www.techzine.eu/news/applications/135751/automattic-accuses-wp-engine-of-misleading-practices/] date created: 2025-10-27 00:00 --- # 🏷️ Title: Automattic accuses WP Engine of misleading practices ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: Automattic filed new counterclaims alleging WP Engine inflated its value via “prolonged trademark infringement and misleading branding,” and that Silver Lake-enabled practices undermined WordPress trust. - Why it matters: It tests boundaries of fair use around “WordPress/WooCommerce” branding and open-source stewardship. - Key stakeholders: Automattic, WP Engine, Silver Lake, WordPress.org volunteers/users. - Risks and tradeoffs: Brand confusion, community fragmentation, hosting feature regressions vs. hosts’ marketing latitude and fair use. - Bottom line: Automattic seeks to bar certain WordPress-related terms, damages, and a jury trial; WP Engine previously said it acts within fair use. ## 📖 Main Content - Core arguments: Automattic alleges WP Engine misused WordPress/WooCommerce marks, exaggerated contributions, and reduced hosting quality (e.g., removing page-restore features), harming users and the brand. It also targets Silver Lake’s post-2018 influence and fees. - Context: Dispute escalated since Sept 2024 after public criticism from Matt Mullenweg; WordPress.org then restricted WP Engine access and sponsorships, prompting community division. - Terms: - Trademark infringement/unfair competition: Using protected marks in ways that mislead consumers. - Fair use: Limited descriptive use of marks without implying endorsement. - Uncertainties: Court outcome, scope of restricted terms, and measured impact on users. ### 🗒️ Notes - “Automattic has filed new counterclaims… over the use of the WordPress and WooCommerce brands.” - Allegations: “artificially inflated the value… through prolonged trademark infringement and misleading branding.” - Community fallout: bans on WP Engine sponsorships; volunteer speech limits controversy. - Automattic claims removed features (e.g., page-restore) harmed users. - Seeks: findings of infringement, unfair competition, injunction on terms, damages, jury trial. - WP Engine response pending in this round; prior stance: fair use and support for open source. ## 📚 References - Techzine article (source): https://www.techzine.eu/news/applications/135751/automattic-accuses-wp-engine-of-misleading-practices/ - Background context from The Register reporting on responses. - WordPress.org project home: https://wordpress.org - Silver Lake (firm overview): https://www.silverlake.com ## 🗣️ Paraphrase - Paragraph A: Automattic escalated its legal fight with WP Engine, alleging trademark misuse and deceptive branding tied to Silver Lake’s ownership. - Paragraph B: The clash split the community after policy changes; Automattic now seeks to overturn an earlier WP Engine court win with detailed claims on contributions and service quality. ## 📰 Newsletter WordPress legal drama heats up: Automattic’s new counterclaims say WP Engine’s branding crosses the line, even as WP Engine cites fair use. Expect ripple effects on event sponsorships, plugin access, and how hosts message “WordPress” compatibility. For builders: review your trademark usage, clarify support policies, and double-check rollback/restore capabilities. Helpful reads: WordPress trademark policy, community guidelines, and host comparison checklists. ## ✅ Action Items #### DevRel - Publish guidance on correct WordPress/WooCommerce mark usage with examples. - Run office hours on “brand, forks, and fair use” for agencies. - Sample repos: trademark-safe README badges; environment restore demos. #### OSPO - Update trademark/fair use compliance training and pre-release reviews. - Define incident comms playbook for brand disputes and injunctions. #### Community - Host governance clinics on sponsor policies and volunteer speech norms. - Maintain transparent funding and conflict-of-interest disclosures. #### WordPress - Core: audit rollback/restore UX; document host-facing APIs. - Performance: publish restore-related performance/space benchmarks. - Community/Marketing: refresh event sponsorship and social guidance. - Documentation: clarify brand usage and compatibility language patterns. #### The WPCC - Offer microgrants for documentation sprints on brand/legal hygiene. - Fund maintainer time for governance tooling and policy explainers. ### FAIR - Ship signed release artifacts; provenance for hosted builds. - Standardize operator agreements and scorecards for hosts. ## 🧪 Hypotheses - Clearer trademark guidance reduces misleading host marketing within 6 months. - Restoring robust rollback features decreases user churn for affected hosts. - Community sponsorship restrictions increase contributor attrition in the short term. - Public disputes reduce plugin adoption growth among WP Engine users. ### 📊 Methodology - Pre/post policy-change audits of host marketing pages (labeling accuracy scores). - Survival analysis on site churn vs. presence of restore features. - Contributor activity time series around sponsorship rule changes. - Cohort analysis of plugin adoption across host segments. ### ❓ Questions - Which specific terms would the court enjoin, and how enforced? - What measurable harm did feature removals cause? - How should open-source projects police mark usage without chilling speech? ### 🔮 Future Research - Comparative study of trademark enforcement across open-source ecosystems. - Best-practice playbooks for host-mark branding and disclosures. ### 💡 Implications - Practice: tighter brand-safe language in docs/marketing. - Policy: clearer event and sponsorship rules with appeals. - Security: ensure rollback/restore for incident recovery. - Education: maintainers’ legal literacy modules. ### 🧠 Learning Styles Assessment - Reading level: Flesch-Kincaid Grade ≈ 10–11. #### 👀 Visual learners - Improve: flowchart of “permissible vs. restricted” mark usage. #### 🔊 Aural learners - Improve: 3-minute audio explainer on fair use. #### 🗣️ Verbal learners - Present: definitions, examples; add glossary. #### 🧩 Kinesthetic learners - Improve: checklist-lab to audit a landing page for compliance. #### 🧠 Logical learners - Improve: decision tree for brand language approvals. #### 🧑‍🤝‍🧑 Social learners - Improve: moderated Q&A with legal/OSPO experts. #### 🧘‍♀️ Solitary learners - Improve: self-check quiz on scenarios. #### 🌿 Naturalistic learners - Improve: ecosystem health analogy for brand governance. ### 📊 Accessibility Assessment #### Screen reader semantics - Improve: add descriptive alt text to brand examples. #### Keyboard navigation - Improve: ensure tab order in policy pages. #### Contrast and readability - Improve: maintain 4.5:1 in example badges. #### Text resizing and reflow - Improve: support reduced motion on policy sites. #### Media and captions - Improve: captions for policy explainer videos. #### Forms and interactions - Improve: inline validation for trademark request forms. #### Standards reference - Map to WCAG 2.2 AA: 1.4.x, 2.4.x, 3.3.x. ### 🌍 DEIB Assessment #### Cultural breadth - Improve: global case studies; translation of policies. #### Inclusive language - Present: mostly neutral; add plain-language summaries. #### Neurodiversity support - Improve: consistent icon+ - Summary: Automattic has filed new counterclaims against hosting company WP Engine in a long-running dispute over the use of the WordPress and WooCommerce brands. - URL: https://www.techzine.eu/news/applications/135751/automattic-accuses-wp-engine-of-misleading-practices/ ![Automattic accuses WP Engine of misleading practices](https://www.techzine.eu/wp-content/uploads/2025/10/shutterstock_788198215.jpg) **Automattic has filed new [counterclaims](https://automattic.com/2025/10/24/counterclaims/) against hosting company WP Engine in a long-running dispute over the use of the WordPress and WooCommerce brands. Automattic** **manages** **WordPress.com and WooCommerce, among other things**. **It is also closely linked to the development of WordPress.** Automattic claims that since being acquired by investment firm Silver Lake, WP Engine has [undermined](https://www.techzine.eu/news/applications/127693/automattic-drastically-scales-back-contributions-to-wordpress-core/) the trust that has been built up over decades around WordPress and the open-source community. In the legal documents, Automattic alleges that WP Engine has artificially inflated the value of its business. WP Engine achieved this through prolonged trademark infringement and misleading branding. The [conflict](https://www.techzine.eu/news/privacy-compliance/129007/wordpress-conflict-escalates-due-to-new-lawsuit/) has been ongoing since September 2024, when Matt Mullenweg, co-founder of WordPress and CEO of Automattic, publicly criticized WP Engine. He felt that the company was profiting too much from WordPress without contributing proportionally to the open-source project. Shortly thereafter, WordPress.org, led by Mullenweg, restricted WP Engine’s access to parts of the platform, which affected the use of plugins and add-ons by WP Engine customers. #### Division within the WordPress community This approach led to division within the WordPress community. Several volunteers and developers expressed their dissatisfaction when WordPress.org introduced new rules prohibiting WP Engine sponsorship at local events and restricting what volunteers could say on social media. Earlier in the dispute, WP Engine won a victory in court. Automattic is now attempting to overturn that earlier ruling with the new counterclaims. In the 162-page complaint, the company alleges that WP Engine exaggerated its contributions to the WordPress codebase, lowered the quality of its hosting services, and removed essential features, such as the ability for users to restore previous versions of pages. According to Automattic, these choices harmed users and undermined trust in the WordPress brand. Automattic is also targeting Silver Lake. The investor allegedly used WP Engine after its 2018 acquisition to collect management fees and hide mistakes by inflating the company’s value. Automattic is asking the court to find WP Engine guilty of trademark infringement and unfair competition. The company wants the court to prohibit WP Engine from using certain WordPress-related terms and to award damages. Automattic is also requesting that the case be heard by a jury. According to [The Register](https://www.theregister.com/2025/10/27/automattic_wp_engine_counterclaim/), WP Engine has not yet responded to the new complaint. In previous statements, the company has indicated that it operates within the bounds of fair use and supports the open-source principles of WordPress., Automattic Accuses WP Engine of Misleading Practices, Mels Dees, 01k8jt2cnys6v7c358atfhx4pm.