The WordPress vs WP Engine situation: what it means for you
The public dispute between Automattic and WP Engine has shaken the WordPress community. Here's a measured take on what happened and what you should do.
Have you been following the WordPress drama? Unless you've been completely off the internet for the past few weeks, you'll have seen the very public fallout between Matt Mullenweg (Automattic, WordPress.org) and WP Engine. It's been messy, legal threats, blocked plugin access, accusations of profiteering, a community divided. I want to give you my honest take on what happened and, more importantly, what it means if you're running a WordPress site.
The short version: Matt Mullenweg accused WP Engine of profiting from the WordPress ecosystem without contributing enough back, particularly around trademark usage and contributions to WordPress core development. He called WP Engine "a cancer to WordPress" at WordCamp US. Whatever you think of WP Engine, that's not how a steward of an open-source project should behave. Automattic then blocked WP Engine's access to WordPress.org, which meant WP Engine customers couldn't update plugins or themes through the normal channels. WP Engine filed a lawsuit. Automattic filed a counter-suit. It escalated rapidly and publicly. So what does this mean for you?
Why it matters beyond the drama.
The real issue, as I see it, underneath the personalities and legal filings is about WordPress's governance. WordPress.org, the repository of plugins and themes that every WordPress site depends on, is effectively controlled by one person. When that person decides to block a major hosting provider's access, there's no independent body to intervene, no appeals process, no governance structure to prevent it. That's a significant concentration of power over a platform used by 40% of the web.
For WP Engine customers specifically, the plugin update block was resolved relatively quickly, but it exposed a real dependency. Your website's ability to receive security updates was, briefly, subject to a business dispute you had no part in.
What should you do?
If you're a WP Engine customer: don't panic. The immediate technical issues have been resolved. But this is a good moment to evaluate whether you're comfortable with your hosting provider's relationship with WordPress.org. WP Engine is a good host technically, and the dispute is unlikely to affect your day-to-day operations in the long term. But the precedent has been set.
If you're on WordPress generally: the platform itself is fine. WordPress is open-source software, and no business dispute changes the code or its licence. But this situation has highlighted governance risks that the community will need to address. If you're building a new site and this has given you pause about WordPress's long-term stability, that's a reasonable concern to factor into your platform decision.
If you're considering alternatives: this isn't a reason to panic-migrate off WordPress. Migrations are expensive, risky, and time-consuming, and a hasty move will cause more problems than it solves. So what should you actually do? But if you were already considering a move, because of performance, editorial experience, or technical limitations, this might be the context that tips the balance.
My take
I've been diversifying away from WordPress for my own projects for a couple of years now, not because of this drama (which nobody predicted) but because headless CMS platforms give us a better development and editorial experience for the types of projects I build. I still have clients on WordPress, I still maintain WordPress sites, and I still think it's the right choice for many use cases. But I'm glad I'm not solely dependent on it.
Look, the WordPress community is resilient, and the ecosystem will adapt. But the governance question needs answering. How it gets resolved will shape WordPress for the next decade, and right now, I don't think anyone knows how that's going to play out.
If this has prompted questions about your own WordPress setup or you want to explore alternatives, I'm here to help, get in touch.
Chris Ryan
Managing Director
17+ years in full-stack web development, most of it leading teams agency-side across e-commerce, CMS platforms, and bespoke applications. Specialises in infrastructure, system integration, and data privacy, with hands-on experience as a Data Protection Officer. Founded Innatus Digital in 2020 to offer the kind of honest, technically-led partnership that he felt was missing from the agency world.