For twenty years, WordPress felt like a safe default partly because it felt neutral: open-source, community-run, not something any single company could pull out from under you. Recent events have complicated that assumption, and if your business depends on the platform, it’s worth understanding why.

What actually happened

In late 2024, a public dispute broke out between Automattic, the company behind WordPress.com and led by WordPress co-founder Matt Mullenweg, and WP Engine, one of the largest WordPress hosts. In the middle of it, WP Engine was temporarily blocked from accessing WordPress.org resources that many sites rely on for plugin and theme updates.

Shortly after, Automattic took over Advanced Custom Fields, a plugin used on a huge number of sites, and continued it from WordPress.org under a new name, Secure Custom Fields, without the original maintainers. Litigation followed, and parts of the community began mirroring plugins and discussing forks in case access couldn’t be relied on.

You don’t need a view on who was right to notice the important thing: decisions that affected millions of sites were made quickly, and centrally.

Why this matters even if you’re not WP Engine

The specifics of that dispute may never touch your site directly. The lesson underneath it does:

The infrastructure a lot of businesses treated as neutral turned out to have a single point of control.
Access to updates, the thing that keeps a WordPress site secure, was shown to be something that can be switched off.
The plugin ecosystem you depend on is governed by relationships that can change without your input.

Platform risk isn’t about whether you like the people in charge. It’s about how much of your business you’ve placed somewhere you don’t control.

Owning your own foundation

None of this makes WordPress unusable. But it’s a good moment to ask a question you should ask of any dependency: what happens to us if the terms change?

An architecture you control answers that question calmly:

Your site is your own code and content, deployed on infrastructure you choose, not gated behind one organisation’s goodwill.
There’s no central update channel that can be revoked, because there’s no sprawling plugin ecosystem to update.
Portability is designed in: you can move hosts without asking anyone’s permission.

That independence is part of what we deliver in a Replatform & Performance Rescue: a foundation that stays yours regardless of who’s fighting whom this quarter.

If recent events made you wonder how much of your platform you actually control, request a fit check: we’ll help you weigh the risk honestly.