If your business runs on WordPress, you've been making a governance bet every single day. You just didn't know it.
On Wednesday, June 4, a California courtroom will hear Automattic's motion to dismiss WP Engine's antitrust claims. Monopolization. Attempted monopolization. Tying. Extortion under the Computer Fraud and Abuse Act. If the motion fails, this whole thing heads to a jury trial in September 2027.
Two days later, Matt Mullenweg -- who controls 84% of the WordPress Foundation's board voting power -- delivers the closing address at WordCamp Europe in Krakow to 3,000+ attendees.
That timing tells you everything about the tension here.
This Isn't New Drama. It's a Pattern.
Let me back up. If you haven't been following this, the short version: Automattic (the company behind WordPress.com) and WP Engine (one of the largest WordPress hosting providers) have been in an escalating legal fight since late 2024. Automattic blocked WP Engine from accessing WordPress.org resources, forcibly forked a plugin with 2 million active installations without developer consent, and added a mandatory loyalty checkbox to the WordPress.org login.
When a court ordered the checkbox removed in December 2024, Mullenweg replaced it with a pledge about pineapple on pizza. Technically compliant. Structurally the same gate.
But here's the part most coverage misses: unsealed discovery from February 2026 alleges Automattic planned to hit at least 10 competing hosting providers with 8% royalty demands on monthly gross revenue. Internal correspondence allegedly includes phrases like "if they don't take the carrot, we'll give them the stick" and plans to "steal every single WP site" from non-compliant hosts. One major hosting conglomerate is allegedly already paying.
This isn't a spat between two companies. It's a governance structure being stress-tested, and the results aren't encouraging.
The Numbers Say Something Is Already Shifting
WordPress dropped from 43.2% market share in December 2025 to 41.9% in May 2026. That's a 1.3-point decline in six months -- double the pace of all of 2025. Active domains contracted 19% between April and August of last year.
Meanwhile, competing website builders grew 9-29% over the same period. Net migration shows over 5,000 more companies leaving WordPress for one specific competitor than the reverse.
Automattic's own valuation dropped 63.5%. BlackRock marked shares down from $85 to $31. Around 440 employees left in six months -- roughly 23% of the workforce, including over 100 from the e-commerce division.
And 48.8% of WordPress plugin companies reported worsening sales in 2025.
I'm not saying WordPress is dying. 42% of the web is an enormous install base with no real replacement at scale. But for the first time in a decade, the trajectory reversed. And the timing correlates directly with governance decisions, not technical ones.
Your Platform Choice Is a Governance Bet
Here's what I actually want you to understand.
When you pick a platform for your business, you're usually thinking about features. Templates. Pricing. Maybe performance. Almost nobody thinks about governance -- who controls the project, how decisions get made, what happens when the controlling entity's interests diverge from yours.
WordPress is open source. That sounds like it should mean distributed control. But the WordPress Foundation's role is, by the admission of 20+ core contributors who signed an open letter, "largely administrative" with no real community oversight. One person holds 84% of board voting power. The contributors called out "the volatility of the self-governing BDFL model" and cited "a major breakdown in trust."
Compare that to something like PostgreSQL, where distributed ownership across thousands of contributors makes unilateral license changes structurally impossible. That's the difference between a technology risk and a governance risk.
This pattern repeats. MongoDB in 2018. Elasticsearch in 2021. Terraform in 2023. Redis in 2024. Every time, a company controlling an open-source project made unilateral changes that fractured the ecosystem. Every time, forks emerged and gained real traction. The Redis fork hit 50 contributing companies in its first year.
WordPress hasn't forked yet. But 20+ of its own core contributors are publicly saying the structure that would prevent one doesn't exist.
Migration Isn't Free Either
Before anyone reads this as "leave WordPress tomorrow" -- that's not the point.
The average business loses $315,000 per platform migration project according to 2025 industry data. Even a typical B2B site migration runs $7,000-$15,000 and takes 4-10 weeks. Enterprise? $30,000 to $150,000+. And 80% of migration projects run over time or budget.
Those are real costs. Staying on WordPress has costs too, but they're harder to measure until a governance decision directly affects your site. Like, say, a plugin you depend on getting forcibly forked overnight without your consent.
The smart play isn't "migrate now." It's understanding what you're actually betting on and having an exit plan you never need to use.
What This Means for Your Business
Three things worth thinking about before Wednesday.
Your content should be portable. If your posts, pages, and customer data can't export cleanly into a standard format, that's a problem regardless of what platform you're on. Check this now, not during a crisis.
Your hosting should be separable from your CMS. If one company controls both your platform and your hosting relationship -- or can dictate terms to your host -- you have a single point of governance failure. That's not a technology problem. It's a vendor concentration problem.
Your performance baseline matters more than your platform loyalty. WordPress sites average 3.4-second load times in HTTPArchive benchmarks. Modern frameworks hit under a second. With search engines weighting performance, this compounds over time. Know your numbers.
None of this requires you to do anything dramatic right now. But if you're running a business on a platform where one person can fork a plugin out from under 2 million sites, block a major hosting provider, and gate access behind loyalty pledges -- you should at least know that's the bet you're making.
Where We Come In
We manage long-term hosting and infrastructure for clients across multiple industries -- some of those relationships go back 13+ years. We've watched platform governance cycles play out before, and we help businesses build infrastructure that doesn't depend on any single vendor's goodwill.
If you want to talk through your platform exposure, first conversation is always free. No pitch, no commitment. Just an honest look at where you stand.
Hit us at kief.studio/contact.