Automattic–WP Engine Term Sheet

Perception of the Term Sheet and “8%” Demand

• Many commenters describe the proposed 8% of gross revenue as punitive, “extortionate,” or deliberately unacceptable rather than a serious offer.
• Some see it as an opening bid that might be negotiated down, but others argue that targeting a direct competitor with such terms crosses into coercion.
• The option to instead devote 8% of revenue in staff time directed by WordPress.org is viewed as effectively giving a competitor control over employees.

Audit Rights and Privacy Concerns

• The broad “full audit rights,” including access to revenue breakdowns, employee records, and time tracking, are seen as intrusive.
• Commenters question whether sharing detailed employee data could conflict with privacy norms or health data protections, though others note HIPAA likely doesn’t apply directly.
• Several argue these provisions are structured to make the “time contribution” option unattractive, pushing toward cash payments.

Governance, Trademarks, and “Hidden License”

• There is strong confusion and concern about the relationship between WordPress.org, the WordPress Foundation, and Automattic.
• Commenters highlight that trademarks are formally owned by the Foundation but licensed to Automattic on very favorable terms, undermining earlier public messaging that the trademark was “independent.”
• Learning that WordPress.org is personally controlled by a single individual alarms many, who see it as a personal fiefdom rather than a neutral steward.
• Some describe a de facto “hidden license”: if Automattic decides a company isn’t “giving back,” extra conditions and financial demands appear.

Trademark vs. Open Source Use

• One side argues WP Engine has heavily “piggybacked” on the WordPress brand and should pay for that marketing benefit.
• Others counter that describing services as “WordPress hosting” or using “WP” is explicitly allowed by the published trademark policy and is analogous to “Honda repair shop”–style usage.
• There is debate over whether certain phrases imply official endorsement (“The WordPress X”) versus generic compatibility.

Reputation, Trust, and Community Impact

• Many long‑time users and contributors say this saga has severely damaged their trust in the WordPress ecosystem and leadership.
• Some are considering abandoning WordPress or forking it, stating they no longer feel comfortable contributing to a project that can be used to pressure competitors.
• The behavior is compared to other controversial platform moves (e.g., Unity), and some describe it more as bullying/market distortion than typical trademark enforcement.

Open Source Sustainability and Fairness

• A minority defends the underlying grievance: large commercial users capturing significant value while contributing little back is a long‑standing open source problem.
• Others reply that if different terms were desired, they should have been encoded in the license from the start rather than retroactively enforced through trademarks and infrastructure control.

Specifics Around WP Engine

• Commenters note WP Engine’s role in improving historically weak areas of WordPress (local development, managed hosting), with tools like “Local” praised as what WordPress should have shipped years earlier.
• Some speculate that Automattic is reacting to a competitor’s success in higher‑end hosting and developer tooling, rather than to genuine trademark harm.
• There is disagreement on economics: some argue 8% of gross revenue could wipe out profits; others claim hosting margins are high enough that it would “only” be painful, not fatal.

Role of WordPress.org Infrastructure

• One explanation offered is that Automattic funds WordPress.org services that WP Engine relies on by default for all its customers, and wants compensation for that usage.
• Critics respond that if compensation is owed, it should logically go to the non‑profit Foundation, not directly to Automattic.

HN Meta and Alternatives

• Several users remark that threads on this topic appear to be rapidly buried on HN, possibly due to flags and high comment‑to‑point ratios.
• The drama pushes some to look for non‑headless CMS alternatives with visual editors and page builders, though the thread doesn’t converge on a single clear alternative.