Automattic

A 12-story peak in 2024Q4 was driven by Automattic’s escalating WP Engine dispute, while recent coverage shifts to WordPress.com AI and restoring WordPress contributions.

Who they are

Automattic is the company behind WordPress.com and owner of Tumblr and Beeper, appearing in coverage both as a product operator and as a consequential participant in the wider WordPress ecosystem. CEO Matt Mullenweg is central to that coverage, particularly where Automattic’s commercial business intersects with WordPress.org and the open-source project.

The recent arc

Coverage peaked in 2024Q4 as the conflict with managed-hosting company WP Engine turned a business dispute into a governance story about the WordPress ecosystem. Reports covered Mullenweg cutting WP Engine’s free WordPress.org access, the forking of WP Engine-developed Advanced Custom Fields, and his statement that WordPress.org belonged to him personally; the latter sharpened scrutiny of the boundaries among WordPress.org, the WordPress Foundation, and Automattic. The dispute also coincided with reports that 159 Automattic employees accepted severance after disagreeing with WordPress’s direction and handling of WP Engine.

In 2025 and early 2026, attention broadened from confrontation to operational retrenchment and product development. Automattic laid off 16% of staff in April 2025, paused then resumed contributions to WordPress project components including Core, Gutenberg, Playground, and Openverse, and filed counterclaims against WP Engine alleging trademark abuse. Separately, Beeper relaunched with a paid plan, Tumblr’s backend migration to WordPress was put on hold, and the latest reports center on a WordPress.com AI assistant for natural-language sitewide layout and style changes.

The tension

The defining tension is Automattic’s dual position: it is a commercial WordPress.com operator led by a figure with unusual influence over WordPress.org, while WP Engine is both a major WordPress business and an adversary in litigation and access disputes. Coverage also raises a related question of stewardship: pauses in Automattic’s project contributions, account deactivations involving prospective fork advocates, and the Advanced Custom Fields fight have made open-source governance inseparable from the company’s commercial conflict.

Why it matters

If this trajectory continues, Automattic’s choices could shape not only WordPress.com features but the perceived independence and practical governance of infrastructure used across the WordPress ecosystem. The return to project contributions may ease some pressure, while the WP Engine case and disputes over access, trademarks, and plugin control remain tests of whether commercial competition can be separated from stewardship of shared open-source assets. AI features on WordPress.com and AI-related licensing discussions add another strategic layer, but the corpus does not establish how broadly those efforts will alter the business.

Related: WordPress · Matt Mullenweg · WordPress.com · WP Engine · WordPress.org · Tumblr