The WordPress community was shaken this week by a pointed critique from Matt Mullenweg, co-creator of WordPress and CEO of Automattic. During his keynote at WordCamp US 2024, Mullenweg pulled no punches, branding WP Engine—a major player in managed WordPress hosting—as a "cancer to WordPress." His accusations focused on WP Engine’s profit-driven approach, which he claims undermines the open-source ethos at the heart of WordPress.
WP Engine: Profits Over Contributions?
Founded in 2010, WP Engine has grown into one of the largest managed WordPress hosting providers, with close to $300 million in funding. Yet, Mullenweg argues that the company’s success has come at a steep cost to the WordPress ecosystem. In his speech, he detailed how WP Engine, despite benefiting immensely from the open-source platform, contributes only a fraction back compared to companies like Automattic. He revealed that while Automattic contributes 3,900 hours weekly to WordPress development, WP Engine offers just 40 hours—a stark contrast for two companies with similar revenue levels.
"WP Engine is leveraging WordPress’s open-source infrastructure to build their business while giving very little in return," Mullenweg stated. This disparity highlights a broader issue within the WordPress ecosystem, where companies capitalize on the platform without investing significantly in its future.
A History of WordPress Hosting Investment
Interestingly, Automattic has a history of investing in hosting companies, including WP Engine itself back in 2011. Automattic also holds a majority stake in Pressable, another WordPress hosting service, and has invested in GridPane, which provides managed WordPress solutions. This context makes Mullenweg’s criticism all the more significant, signaling a shift in how Automattic views its competitors in the hosting space.
However, WP Engine’s ties to Silver Lake, a private equity firm managing $102 billion in assets, seems to have been a tipping point for Mullenweg. "Silver Lake doesn’t care about open-source ideals; they care about return on capital," he said, urging the WordPress community to reconsider supporting a company more interested in profits than the platform’s future.
The Core of the Issue: Disabling Key WordPress Features
Mullenweg’s most stinging criticism of WP Engine revolves around their decision to disable a key WordPress feature: post revisions. WordPress, by default, saves every change made to a post, allowing users to revert to previous versions if necessary—a feature that helps maintain the integrity of users' content. WP Engine, however, disables revisions across its 1.5 million WordPress installs to save on database costs.
Customers can request revisions be enabled, but only up to three, which are then automatically deleted after 60 days. For those needing extensive revision management, WP Engine recommends using third-party editing systems. Mullenweg contends this policy breaks a fundamental promise of WordPress: protecting users’ data. "They disable revisions because it costs them more money to store the history of the changes, and they don’t want to spend that to protect your content," he argued.
This, Mullenweg emphasized, "strikes to the very heart of what WordPress does." The decision compromises users’ ability to manage their content effectively, leaving them vulnerable to mistakes they cannot undo.
“Vote with Your Wallets”
Mullenweg’s call to action was clear: he encouraged users to reconsider their hosting provider when their WP Engine contracts come up for renewal. He highlighted several alternatives, including Thexyz, Bluehost, and Host Papa, urging users to "vote with their wallets" and support companies that contribute meaningfully to WordPress.
"There are plenty of other hosts out there that would love to have your business, and you might even get better performance by switching," Mullenweg said. He also pointed out how easy it is to migrate WordPress sites, making the switch far less daunting than it might seem.
WP Engine’s Response: A Legal Battle?
Unsurprisingly, WP Engine hasn’t taken these accusations lightly. Shortly after Mullenweg’s speech and subsequent blog post, WP Engine’s legal team issued a cease-and-desist letter to Automattic, refuting his claims and demanding a retraction. The legal back-and-forth may just be beginning, but it’s clear that this public rift has already made waves in the WordPress community.
The Broader Impact
This isn’t the first time Mullenweg has criticized a major web host. In the past, he’s leveled similar accusations at GoDaddy, referring to the company as a "parasitic" threat to WordPress. His core complaint remains the same: large hosting providers profit off WordPress’s open-source nature without giving enough back to the project. As more companies look to commercialize WordPress, Mullenweg’s concern is that they could set damaging precedents that weaken the platform's future.
Mullenweg’s recent remarks should serve as a wake-up call for the community. His message was clear—hosting providers that exploit WordPress for profit without investing in its future are a threat to the ecosystem. It’s up to users to decide whether they will support companies that prioritize profits or those committed to nourishing the platform for years to come.
Conclusion: Rethinking WordPress Hosting
Mullenweg’s critique of WP Engine, calling them a "cancer to WordPress," is a strong reminder of the importance of supporting companies that contribute to the open-source community. As WordPress continues to power over 40% of the web, users have a responsibility to consider which hosting providers align with their values.
While WP Engine may offer convenience, the trade-offs in terms of content protection, platform integrity, and ecosystem contributions may not be worth it. As the WordPress community evolves, choosing a host that supports the future of the platform—rather than exploiting it—will be more important than ever.
0 Comments