WPEngine, Inc. v. Automattic Inc., et al. 🔗 **Source:** [WPEngine, Inc. v. Automattic Inc., et al.](https://readwise.io/reader/document_raw_content/421377812) > [!note]+ Document Notes > ```yaml > tags: [WordPress, Legal, Antitrust] > author: Quinn Emanuel Urquhart & Sullivan LLP > source: [MISSING] > reference: [https://readwise.io/reader/document_raw_content/421377812] > date created: 2026-02-16 10:00 > > --- > > # 🏷️ Title: WPEngine, Inc. v. Automattic Inc., et al. > <!-- deep-read:sections start --> ## 🧭 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: WP Engine sues Automattic, WooCommerce, and Matt Mullenweg alleging extortion, anticompetitive conduct, and defamation over trademark demands and a campaign to ban WPE from WordPress.org ([example allegations](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_0000b_00000-0009&startLexposition=00000_0000Z&emphasizeText=scheme+to+ban+WPE+from+the+WordPress+community+unless+it+agreed+to+pay+tens+of+millions+of+dollars)). - Why it matters: Challenges control of core WordPress infrastructure and trademark enforcement as potential competition law and governance issues. - Key stakeholders: WP Engine, Automattic/WooCommerce, Matt Mullenweg, WordPress Foundation, hosts, plugin authors, and WordPress users. - Risks and tradeoffs: Platform fragmentation, trust in .org governance, chilled investment vs. stronger trademark control and central coordination. - Bottom line: WPE seeks damages and declaratory relief that its WordPress/WooCommerce references are lawful, and asks the court to curb Automattic’s use of WordPress.org power. ## 📖 Main Content - The complaint alleges Automattic and Mullenweg used sudden trademark demands for terms like “WordPress” and “WooCommerce” as leverage to extract “tens of millions” from WPE, threatening a “nuclear” war and a ban from WordPress.org if WPE refused ([threat description](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_0006x_00005_00000-007V&startLexposition=00000_0006u&emphasizeText=Automattic+CFO+Mark+Davies+told+a+WPE+board+member+that+Automattic+would+%22go+to+war%22+if+WPE+did+not+agree+to+pay)). - WPE claims its use of the marks is nominative fair use consistent with long-standing community practice, and that Automattic had tolerated or endorsed WPE’s branding for over a decade, including through investment and Five for the Future pledges ([historical tolerance](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_00038_0000M-001C&startLexposition=00000_00038&emphasizeText=Defendants+have+known+about+WPE%27s+use+of+the+Challenged+Terms+for+more+than+a+decade)). - The filing describes a public campaign: posts on wordpress.org news, Mullenweg’s personal blog syndicated into WordPress admin dashboards, conference talks, and social posts portraying WPE as a “cheap knock-off,” “cancer,” and a poor community citizen while urging customers to switch to Automattic properties like wordpress.com and Pressable ([defamation allegations](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_0008T_00002-00Az&startLexposition=00000_0008T&emphasizeText=WP+Engine+is+free+to+offer+their+hacked+up%2C+bastardized+simulacra+of+WordPress%27s+GPL+code)). - WPE alleges exclusionary conduct: blocking WPE and some customers from WordPress.org plugin infrastructure and adding a login checkbox asserting “I am not affiliated with WP Engine in any way, financially or otherwise” as a condition of access ([checkbox and blocking](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_000SF_00002-000Q&startLexposition=00000_000SB&emphasizeText=requires+anyone%E2%80%94including+customers%2C+developers%2C+and+web+hosts%E2%80%94logging+into+wordpress.org+to+affirm+%22I+am+not+affiliated+with+WP+Engine+in+any+way%2C+financially+or+otherwise%22)). - On competition, WPE frames WordPress.org and the plugin directory as chokepoints through which Automattic allegedly conditions access on avoiding WPE, and claims this has driven “tens of thousands” of customers away, only partially reversed by a preliminary injunction ([market-impact passage](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_000IF_00000-004f&startLexposition=00000_000ID&emphasizeText=As+Defendants+boasted%2C+their+anticompetitive+conduct+has+caused+%22+tens+of+thousands+of+customers%22+to+leave+WPE)). - Legally, WPE asserts claims including: antitrust (monopolization, tying, exclusive dealing), unfair competition, promissory estoppel (reliance on WordPress openness), declaratory judgment of non-infringement and non-dilution, libel, slander, and related state-law business torts ([declaratory judgment section](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_000ND_00000-00B5&startLexposition=00000_000NB&emphasizeText=WPE%27s+use+of+the+Challenged+Terms+does+not+infringe+any+registered+marks)). ### 🗒️ Notes - WPE portrays a long-standing cooperative relationship: Automattic invested in WPE, WPE sponsored WordCamps, and its use of “WordPress”/“WooCommerce” terminology was visible and, by implication, previously accepted ([prior relationship](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_00038_0000M-001C&startLexposition=00000_00038&emphasizeText=Automattic+made+a+substantial+investment+in+WPE+and+remained+an+investor+until+2018)). - Around September 2024, Automattic leadership allegedly demanded a large revenue share for a trademark license, with threats framed as “go to war,” “scorched earth,” and a ban from the “WP community” if WPE did not agree ([war threat](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_000MP_00000-00Tu&startLexposition=00000_000MP&emphasizeText=threatened+%22banning+WPE%22+from+the+WP+community)). - WPE claims it had no reason to think Automattic could charge for WordPress marks because those are formally held by the WordPress Foundation; it argues its use is nominative fair use and consistent with community norms and the Foundation’s own policy ([fair use claim](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_0006z_00000-00Di&startLexposition=00000_0006x_00007&emphasizeText=WPE%27s+nominative+uses+of+those+marks+to+refer+to+the+open-source+software+platform)). - The complaint highlights statements like “WP Engine is not WordPress,” “hacked up, bastardized simulacra,” and accusations that WPE contributes little back, as allegedly false and commercially motivated, especially where posts were adjacent to “Hosting” links pointing to Automattic-recommended hosts ([commercial framing](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_000Nr_00008-006k&startLexposition=00000_000Nr&emphasizeText=Remember+that+you%2C+the+customer%2C+hold+the+power)). - WPE also emphasizes being described as a “cancer” and the placement of Mullenweg’s blog post into WordPress admin dashboards, reaching users irrespective of host as a powerful reputational blow ([dashboard syndication](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_0008T_00002-00Az&startLexposition=00000_0008T&emphasizeText=caused+a+post+from+his+personal+blog+titled+%22On+WP+Engine%2C%22+containing+these+same+false+and+disparaging+statements%2C+to+be+placed+onto+the+WordPress+admin+dashboard)). - The antitrust sections define narrow markets (e.g., WordPress web hosting, WordPress custom field plugins) and treat WordPress.org plugin distribution as a chokepoint whose control allegedly lets Automattic foreclose rivals like WPE ([chokepoint description](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_000Rl_00002-000Q&startLexposition=00000_000Rf&emphasizeText=chokepoint+for+accessing+uploading+and+downloading+WordPress+plugins)). - WPE argues it relied on public promises that WordPress would remain open and accessible, investing “hundreds of thousands of engineering hours and tens of millions of dollars,” and that the recent conduct betrays those expectations ([reliance passage](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_000Mv_00000-00EC&startLexposition=00000_000Mv&emphasizeText=WPE+has+committed+hundreds+of+thousands+of+engineering+hours+and+tens+of+millions+of+dollars+to+develop+its+software+on+the+WordPress+platform)). - For defamation and trade libel, WPE emphasizes alleged knowledge of falsity, the business context (presentations, .org posts, and calls to “vote with your wallet”), and claimed concrete loss of customers ([inducement to switch](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs?endLexposition=00000_000OW_00000-0072&startLexposition=00000_000OS&emphasizeText=as+you+vote+with+your+dollars%2C+consider+literally+any+other+WordPress+host)). ## 📚 References - WordPress.org News posts mentioned (“WP Engine is not WordPress”; “WP Engine banned from WordPress.org”). - WordPress Foundation Trademark Policy (as archived). - Recordings/interviews cited in the complaint (WordCamp US 2024 keynote; YouTube and X.com interviews). - WordPress.org Five for the Future program pages. - WP Engine public posts about its contributions and products (e.g., ACF, Local, WPGraphQL). ## 🗣️ Paraphrase - Paragraph A: WP Engine claims Automattic and Matt Mullenweg abruptly used trademark threats and control of WordPress.org to coerce massive license payments, then launched a public and technical campaign to damage WPE when it refused. - Paragraph B: WPE argues this behavior is anticompetitive, defamatory, and inconsistent with long-standing community norms and promises of openness, and asks the court to both clear its trademark usage and restrain Automattic’s conduct. ## 📰 Newsletter The past year has shaken assumptions about how “open” the WordPress ecosystem really is. The newly filed *WPEngine, Inc. v. Automattic Inc., et al.* complaint alleges trademark overreach, defamation, and anticompetitive use of WordPress.org infrastructure. For developers and agencies, this is a reminder to understand your platform dependencies and governance models. Keep exploring alternatives and portable architectures: lean on core tools, standard plugins, and reproducible deployments (including non-.org mirrors where appropriate). Stay current via: - WordPress.org community updates - WP Engine and Automattic public statements - Independent analysis from respected WordPress community reporters ## ✅ Action Items #### DevRel - Document hosting-agnostic patterns for WordPress projects (portable stacks, minimal reliance on .org-only infrastructure). - Prepare neutral explainers on WordPress trademarks, GPL, and nominative fair use for developer audiences. - Build sample apps and quickstarts that can migrate between hosts with minimal friction. - Track community sentiment and questions about governance; feed back anonymized concerns to leadership. #### OSPO - Publish clear internal guidance on use of “WordPress,” “WooCommerce,” and related marks in products and marketing. - Ensure all WordPress-related dependencies are inventoried (including plugins like ACF) with alternatives identified. - Coordinate with legal on trademark-risk training for engineering, marketing, and partnerships. - Monitor upstream governance changes to WordPress.org policies that could affect distribution or access. #### Community - Encourage calm, fact-based discussion in community spaces; enforce codes of conduct to avoid pile-ons. - Offer office hours or Q&A sessions about platform risk, hosting choices, and migration strategies. - Support maintainers of critical plugins in diversifying their distribution channels. #### WordPress - Core: keep APIs stable and well-documented so sites can remain portable across hosts and distributions. - Core Performance: ensure performance features (like revisions behavior) are clearly documented to avoid mischaracterization. - Core AI: if AI features depend on centralized services, document failover and export paths. - **Core Program Team:** clarify lines between Foundation, Automattic, and .org operations in public docs where possible. - Mobile: avoid hard dependencies on single commercial services for key features. - Playground: use playground environments to teach host-portable WordPress setups. - Community: refine WordCamp sponsor and keynote disclosure to clearly signal commercial interests. - Training: produce vendor-neutral content on choosing hosts and understanding WordPress governance. - Marketing: avoid messaging that suggests any one host is “official” beyond what’s transparently documented. - Support: maintain FAQs on common legal and governance misunderstandings around WordPress. - Design: emphasize neutrality and clarity in .org UI related to hosts and commercial offerings. - Documentation: document how plugins and hosts interact with update APIs and .org services. - Photos / TV / Polyglots / Accessibility / Meta / CLI / Hosting / Tide / Openverse / Themes / Plugins: - Review policies and tooling to ensure no implicit, undocumented advantages or exclusions for specific hosts without clear, transparent criteria. #### The WPOCC - Consider funding research and neutral guidance on governance for open‑core and open‑infrastructure projects. - Support fellowships for maintainers at risk from platform governance disputes. - Pilot transparent funding to diversify critical WordPress infrastructure beyond any one corporate steward. ### FAIR - Encourage projects to document ownership and control of critical infrastructure (domains, plugin repos, CI/CD). - Promote covenants around non-retaliatory use of trademarks and platform controls. - Develop reusable governance artifacts (charters, MoUs) that clarify relationships between nonprofits and commercial entities. ## 🧪 Hypotheses - H1: Centralized control of a key open-source distribution channel (like WordPress.org plugins) increases the risk of anticompetitive exclusion of rival hosts. - H2: Sudden, aggressive trademark enforcement after long periods of tolerance significantly erodes ecosystem trust and investment. - H3: Syndicating opinionated posts into core admin interfaces measurably shifts customer behavior toward the author’s commercial offerings. - H4: Public governance transparency (clear separation of .org/.com/foundation roles) reduces the likelihood and impact of disputes like WPE vs. Automattic. ### 📊 Methodology - For H1/H2: Comparative case studies of other ecosystems (e.g., npm, PyPI) plus econometric analysis of host/plugin market shares before/after policy shifts. - For H3: A/B-test style analysis using traffic and conversion metrics around the time admin-dashboard messages appear (where ethically and legally possible). - For H4: Survey WordPress developers, agencies, and hosts on perceived risk and trust vs. measured governance transparency indicators. ### ❓ Questions - How should open-source communities govern commercial use of their trademarks without weaponizing them? - What safeguards should exist when a dominant commercial actor also operates core community infrastructure? - How portable should WordPress sites and plugins be to keep market competition healthy? ### 🔮 Future Research - Models for shared governance of plugin repositories that balance security, quality, and competition. - Legal-analysis comparisons of nominative fair use patterns across major open-source brands. - Best practices for conflict-of-interest management when foundation leaders also run competing businesses. ### 💡 Implications - Practice: Agencies and product teams may need “platform risk” sections in their architectural and vendor decisions. - Policy: Regulators may look more closely at vertically integrated open-source ecosystems. - Security: Central chokepoints can be exploited not only technically but also economically. - Education: Developer training should include basic IP and governance literacy. - Funding: Diversified funding of shared infrastructure can mitigate single-actor capture. ### 🧠 Learning Styles Assessment - Reading level: Approx. college/advanced professional (legal complaint, dense syntax; e.g., Flesch-Kincaid likely > grade 14). #### 👀 Visual learners - Present: Legal headings, structured numbering, some screenshots referenced via exhibits. - Improve: Flow diagrams of relationships (WPE–Automattic–Foundation–.org), timelines of events, market-structure charts. #### 🔊 Aural learners - Present: Recorded talks and interviews cited, but not embedded here. - Improve: 2–5 minute neutral audio summary of the dispute and claims. #### 🗣️ Verbal learners - Present: Detailed narrative, defined claims, extensive quotations. - Improve: Plain-language callouts summarizing each cause of action and its stakes. #### 🧩 Kinesthetic learners - Present: None directly. - Improve: Hands-on exercises like mapping your own WordPress dependencies and simulating migrations. #### 🧠 Logical learners - Present: Formal legal argumentation, structured claims, market definitions. - Improve: Explicit argument maps, decision trees about governance choices. #### 🧑‍🤝‍🧑 Social learners - Present: Community discussions and conferences as context. - Improve: Guided discussion prompts for meetups or internal teams. #### 🧘‍♀️ Solitary learners - Present: Long-form text suitable for individual deep reading. - Improve: Reflection questions at section ends and short self-check quizzes about key ideas. #### 🌿 Naturalistic learners - Present: Limited; mostly organizational/political. - Improve: Analogies to ecosystems (resilience, monocultures) and sustainability framing for governance. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Legal headings and numbering that roughly map to structure. - Improve: Clear HTML headings and landmarks if presented on the web, descriptive alt text for any exhibits. #### Keyboard navigation - Present: Not applicable to static PDF text. - Improve: If published on the web, ensure all interactive elements and citations are keyboard-accessible. #### Contrast and readability - Present: Standard black-on-white legal formatting. - Improve: Increase line spacing and paragraph breaks in any web summary for easier reading. #### Text resizing and reflow - Present: PDF may not reflow well on small screens. - Improve: Provide HTML and ePub versions with responsive layout. #### Media and captions - Present: References to videos and streams without transcripts in this text. - Improve: Link or embed transcripts and captions for all cited media. #### Forms and interactions - Present: N/A for the complaint itself. - Improve: For related sites (WordPress.org, etc.), ensure accessible forms and error messages. #### Standards reference - Map web presentations of this material to WCAG 2.2 AA, especially 1.4.x (contrast), 1.2.x (captions), 2.1.x (keyboard), 2.4.x (navigation). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Primarily US-legal and WordPress-community context. - Improve: Acknowledge global WordPress usage and differing legal regimes. #### Inclusive language - Present: Formal legal language; relatively neutral but dense. - Improve: Supplement with plain-language summaries, avoid metaphors that stigmatize (e.g., “cancer”). #### Neurodiversity support - Present: Consistent structure but very dense. - Improve: More headings, summaries, and bulleting in any derivative explanations. #### Representation - Present: Focus on corporations and named executives. - Improve: Surface perspectives of smaller agencies, freelancers, and underrepresented contributors impacted by governance. #### Psychological safety - Present: Content includes hostile characterizations (“nuclear war,” “cancer”). - Improve: Content warnings and moderated forums for community discussion. ### ✅ Logical Validity #### Strong reasoning - Market-power arguments: The complaint clearly links control of WordPress.org plugin distribution to potential foreclosure of competing hosts by defining a “chokepoint” and describing specific exclusionary acts. - Trademark defenses: It systematically lays out doctrines like nominative fair use, laches, estoppel, and acquiescence, tying them to years of tolerated use and explicit acknowledgments. #### Fallacies - Some rhetoric (e.g., describing conduct as “nuclear war,” “cancer”) risks emotional coloring that could be seen as loaded language rather than evidence; tightening to documented facts and quantified impacts would strengthen credibility. #### Tone of voice - Tone is adversarial, formal, and accusatory, as expected in a complaint, with charged descriptions of Automattic’s conduct and emphasis on harm to WPE and the broader community. ### 🛡️ DARVO Analysis - Deny: WPE emphatically denies that it needs a trademark license or that it misuses WordPress/WooCommerce marks, asserting its uses are lawful and long accepted. - Attack: The complaint portrays Automattic/Mullenweg as extortionate, vindictive, and anticompetitive, emphasizing inflammatory quotes and alleged misuse of community trust. - Reverse victim/offender: WPE frames itself as the true victim of governance abuse and market exclusion, suggesting Automattic projected wrongdoing onto WPE to mask its own overreach. ## 🎯 Conclusion The complaint paints a picture of a dominant ecosystem actor allegedly leveraging trademarks and control of WordPress.org infrastructure to punish and exclude a major competitor. Whatever the court ultimately decides, this case underscores how much technical, commercial, and governance power is concentrated around WordPress—and why developers, hosts, and agencies should understand, and plan for, the legal and governance assumptions underlying the platforms they build on. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] 5–10-word present-tense claim > [!quote] [WPEngine, Inc. v. Automattic Inc., et al.](https://readwise.io/reader/document_raw_content/421377812) by [[Quinn Emanuel Urquhart & Sullivan LLP]] via an unnamed author. Published 2026-02-09. > “Defendants have prevented WPE from accessing a host of functionality typically available to the WordPress community on wordpress.org.” Two lines: context and use. Cite data if relevant. [view highlight](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [WPEngine, Inc. v. Automattic Inc., et al.](https://readwise.io/reader/document_raw_content/421377812) > “Defendants have installed a prominent ‘checkbox’ on wordpress.org which requires anyone logging in to affirm non-affiliation with WP Engine.” Two lines: context and use. [view highlight](https://read.readwise.io/read/01khh9zwy8c702nj9nja2074xs#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] WordPress.org control shapes competition among hosts - When a dominant host operator also controls plugin distribution, its policy choices can exclude or weaken rivals. - Pointer to market-power discussion in the complaint. - Links: [[Platform-Governance]] [[Antitrust-in-Open-Source]] #### [Z2] Long-tolerated trademark uses change enforcement equities - Years of tolerated nominative use can support defenses like laches and acquiescence against sudden strict enforcement. - Pointer to history-of-use passages. - Links: [[Trademark-Law]] [[Open-Source-Brands]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Map all my WordPress projects’ dependencies on WordPress.org infrastructure/hosts — context/https://readwise.io/reader/document_raw_content/421377812 #fleeting #inbox - [F2] Draft a neutral explainer on WordPress trademarks and nominative fair use — context/https://readwise.io/reader/document_raw_content/421377812 #fleeting #inbox - [F3] Explore governance models where a nonprofit owns brand/infrastructure but multiple vendors compete fairly — context/https://readwise.io/reader/document_raw_content/421377812 #fleeting #inbox --- <!-- deep-read:sections end -->