Pull to refresh
Logo
Daily Brief
Following
Why Ranks Sign Up
The battle for WordPress: WP Engine vs. Automattic

The battle for WordPress: WP Engine vs. Automattic

Rule Changes

A legal war over trademarks, governance, and the future of the web's most popular platform

February 5th, 2026: Hearing Scheduled on Counterclaims Dismissal Motion

Overview

Silver Lake invested $250 million in WP Engine in 2018, taking majority control of the managed WordPress hosting company. Six years later, WordPress co-founder Matt Mullenweg called WP Engine a cancer to WordPress and banned them from WordPress.org resources. This triggered a legal battle that has split the community powering 43% of the web.

Now WP Engine is acquiring specialized agencies like Big Bite to build enterprise publishing products in-house. It's moving from hosting provider to platform competitor against Automattic's WordPress VIP. The fight is about who controls WordPress's future: the open-source idealists or the private equity-backed pragmatists.

Questions about this story

No questions yet — be the first to ask.

Key Indicators

43.4%
Share of all websites running WordPress
Over 810 million websites depend on the platform at the center of this conflict
$250M
Silver Lake's investment in WP Engine
The 2018 deal that gave private equity control and sparked Mullenweg's ire
159
Automattic employees who quit
Workers who took severance rather than support Mullenweg's WP Engine campaign
8%
Revenue demand from Automattic
Mullenweg wanted 8% of WP Engine's monthly gross revenue for trademark license

Voices

Curated perspectives — historical figures and your fellow readers.

Ever wondered what historical figures would say about today's headlines?

Sign up to generate historical perspectives on this story.

Play

Exploring all sides of a story is often best achieved with Play.

Log in to play. Track your picks, climb the leaderboards. Log in Sign Up
Predict 4 ways this could play out. Contrarian picks score more — points lock when the scenario resolves. Log in to play
Timeline Five events from this story — drag them oldest to newest. Log in to play
Connections Sixteen names from the news. Find the four hidden groups of four. Log in to play

People Involved

Organizations Involved

Timeline

January 2010 February 2026

17 events Latest: February 5th, 2026 · 5 months ago Showing 8 of 17
Tap a bar to jump to that date
  1. WP Engine Acquires Big Bite

    Acquisition

    WP Engine buys enterprise newsroom agency, winds down agency business to build publishing products in-house.

  2. 159 Automattic Employees Quit

    Internal

    Workers took severance rather than support Mullenweg's campaign, 80% from WordPress division.

  3. WordPress.org Bans WP Engine

    Technical

    Mullenweg blocked WP Engine access to WordPress.org, preventing customers from installing plugins or updating themes.

  4. Mullenweg Calls WP Engine 'Cancer to WordPress'

    Statement

    At WordCamp US, Mullenweg publicly attacked WP Engine for profiting without contributing back.

  5. WP Engine Acquires NitroPack

    Acquisition

    WP Engine buys performance optimization platform with 219,000 website installations.

  6. Silver Lake Invests $250M in WP Engine

    Investment

    Private equity firm takes majority stake when WP Engine hits $100M annual recurring revenue.

  7. Heather Brunner Becomes WP Engine CEO

    Leadership

    Brunner promoted from COO to CEO, founder Jason Cohen moved to CTO role.

  8. Big Bite Agency Founded

    Business

    Big Bite established as WordPress agency specializing in newsroom platforms at Teesside University.

  9. WordPress Trademark Transferred to Foundation

    Governance

    Automattic transferred WordPress trademark to nonprofit Foundation, then received exclusive commercial license back.

  10. WP Engine Founded

    Business

    Jason Cohen founded WP Engine to provide managed WordPress hosting for businesses.

Historical Context

3 moments from history that rhyme with this story — and how they unfolded.

2010-2021

Oracle vs. Google: Android Java API Battle

Oracle sued Google for using Java APIs in Android without a license, claiming copyright infringement. The case dragged through courts for a decade, with billions in potential damages at stake. Google argued it had the right to use the APIs under fair use. The Supreme Court ultimately ruled 6-2 in Google's favor in 2021, finding that Google's use of Java APIs was transformative fair use that furthered the development of computer programs.

Then

Google won, avoiding billions in damages and maintaining Android's Java compatibility.

Now

The ruling established important precedent for software interoperability and API usage rights.

Why this matters now

Like WordPress-WP Engine, this was a battle over how much control a platform creator can exert over the commercial ecosystem built on top of it, with massive implications for the tech industry.

2008-2010

MySQL Dual Licensing and Community Fork

When Oracle acquired Sun Microsystems in 2009, it gained control of MySQL, the popular open-source database. The community feared Oracle would restrict MySQL to favor its proprietary database products. Key MySQL developers left to create MariaDB, a fork maintaining true open-source principles. Many major companies switched from MySQL to MariaDB, including Google, Wikipedia, and Red Hat. MySQL continued under Oracle, but MariaDB thrived as a community-driven alternative.

Then

The database ecosystem split, with MariaDB gaining rapid adoption among open-source advocates.

Now

Both MySQL and MariaDB remain viable, proving open-source software can survive corporate control through forking.

Why this matters now

This illustrates what could happen if WP Engine or others fork WordPress—the ecosystem might fragment but both versions could survive, especially if the fork attracts developers frustrated with corporate governance.

2020-2021

Red Hat and CentOS: The Community Linux Betrayal

Red Hat announced it would discontinue CentOS Linux, the free version of its Red Hat Enterprise Linux that developers and small businesses relied on. The company shifted CentOS to an upstream development branch rather than the stable downstream rebuild users depended on. The move was seen as Red Hat pushing users toward paid subscriptions. Community members felt betrayed and created Rocky Linux and AlmaLinux as CentOS replacements. Thousands of organizations migrated away from CentOS.

Then

Community forks rapidly gained traction, undermining Red Hat's strategy to convert free users to paying customers.

Now

Red Hat damaged trust with the open-source community while competitors gained users and goodwill.

Why this matters now

Mullenweg's WordPress.org ban mirrors Red Hat's attempt to leverage control of open-source infrastructure for commercial advantage—both triggered community backlash and alternative platforms.

Sources

(19)