WP Engine sent “cease and desist” letter to Automattic

Original Article ↗ Hacker News Discussion ↗

Background of the dispute

  • Automattic’s CEO publicly attacked WP Engine (WPE), calling it harmful to WordPress and criticizing its technical choices (e.g., limiting post revisions).
  • WP Engine responded with a cease and desist letter alleging defamation, trademark overreach, and tortious interference, and published it for community consumption.
  • The conflict centers on hosting, branding, and who “gives back” enough to the open‑source WordPress project.

Trademark and licensing arguments

  • Automattic / the WordPress Foundation assert WPE’s marketing (e.g., “#1 WordPress platform/hosting/tech company” and plan names like “Essential WordPress”) improperly implies official status and exceeds the published trademark policy.
  • Others reply that:
    • The policy itself explicitly allows descriptive uses like “world’s best WordPress themes.”
    • Using “WordPress hosting” is likely nominative fair use; you can describe what you actually host.
    • The policy says “WP” is not covered, and that clause existed long before this dispute.
  • There is criticism of structural conflicts of interest: the nonprofit owns the marks, but Automattic holds the exclusive commercial license and is also a direct competitor to WPE.

Allegations of extortion / unfair competition

  • The C&D cites messages where Automattic’s CEO allegedly:
    • Demanded ~8% of WPE revenue (or equivalent in developer time) for a trademark license.
    • Suggested he could change his keynote content depending on whether WPE paid.
  • Some commenters view this as attempted shakedown or “mob boss” behavior; others frame it as enforcing a license on a major commercial beneficiary.
  • Use of the WordPress dashboard news/RSS widget to broadcast a strongly critical post about WPE to WPE‑hosted sites is seen by many as abusive or anti‑competitive.

Community reaction and optics

  • Many call Automattic’s behavior childish, hypocritical, or reputationally damaging, especially given past rhetoric about software freedom and prior investment in WPE.
  • A minority defend Automattic’s right (and duty) to police trademarks and highlight that WPE contributes relatively little to core compared to its revenue.
  • Some expect significant fallout for leadership; others think Automattic still holds most community credibility.

Broader views on WordPress and hosting

  • Long subthreads debate WordPress quality, security, and plugin chaos versus its huge usability and ecosystem advantages.
  • WP Engine is widely described as expensive but valuable for non‑technical teams and overworked IT—“it’s the only reason I still tolerate WP” appears as a theme.
  • Others argue static sites or alternative CMSes (Laravel‑based, Kirby, Drupal, Statamic, Squarespace/Webflow, etc.) are superior but lack WordPress‑level ecosystem and familiarity.