The world of website hosting and content management has been shaken by the ongoing legal dispute between WordPress, the leading open-source CMS, and WP Engine, a popular managed WordPress hosting provider.

While many are busting out the popcorn as they watch the drama unfold, this battle isn’t just about a petty disagreement between the two tech giants. The outcome could have a tangible ripple effect across the IT industry, especially for Managed Service Providers (MSPs) who rely on both platforms to sustain their online presence as well as deliver reliable website management solutions for their clients.

The magnitude is significant: About 40% of all websites today are powered by WordPress.

Video: Advanced Custom Fields Free Fork (or Hostile Takeover?)

The Dispute: What’s Going On?

The conflict is messy and complicated. At the heart of it is the interpretation of the GPL (General Public License), which governs WordPress as open-source software.

WordPress accuses WP Engine of violating certain aspects of the license, especially around proprietary enhancements and access to premium plugins and features. WP Engine, on the other hand, claims that its services and innovations are built in compliance with the GPL, providing value-added services to clients who rely on their robust infrastructure and support.

This legal drama highlights the often-tenuous relationship between open-source software and commercial service providers who build profitable business models around it. Staff members from both sides are drawing their lines in the sand.

Why MSPs Should Care

MSPs that provide WordPress-based services to their clients could face several challenges as this legal situation unfolds:

  1. Uncertainty in Pricing and Licensing Models
    Should WordPress win, WP Engine may be forced to alter its pricing, licensing, or service structure, which could directly impact MSPs who rely on WP Engine’s platform for their managed WordPress services. This may lead to higher costs or reduced access to premium features, affecting profitability.
  2. Reliability of Managed Hosting Providers
    If the dispute escalates, there’s the potential for disruptions in WP Engine’s services. MSPs that manage multiple client websites hosted on WP Engine could face service outages, delays, or policy changes that might disrupt their operations.
  3. Increased Legal Scrutiny
    This case might spark greater scrutiny on other hosting providers and managed services offering proprietary enhancements on top of open-source platforms. MSPs might need to review their own partnerships and service offerings to ensure they aren’t exposed to similar legal risks.
  4. The Push for Alternative Solutions
    As the landscape changes, MSPs may begin to explore alternative CMS platforms or hosting providers. Diversifying the platforms you offer to clients could be a smart way to mitigate risk and avoid dependency on a single provider like WP Engine.

Preparing for What’s Next

For MSPs, staying ahead of potential disruptions is key. Here are a few steps you can take to ensure you’re prepared:

  • Don’t Panic
    It is at least as likely that this legal drama won’t have a direct impact on your website or your business. Let it serve as a reminder to do your due diligence whenever possible.
  • Review your WordPress Plugins
    If you are using ACF created by WP Engine, and you are NOT also on their hosting platform, you’ll no longer be able to receive updates for the ACF plugin from WordPress.org. You can access a complete list of WP Engine plugins here. Cross-check to see if the plugins you use are on the list. In particular, if you’re using the free version of Advanced Custom Fields (ACF), which is owned by WP Engine, be aware that updating this plugin via the WordPress plugin manager will convert it to Secure Custom Fields (SCF), which is owned by WordPress. In order to get ACF updates from WPEngine you must perform a 1-time download of the latest genuine version. (If you’re using the paid version of ACF, no need to worry—they’ll continue to maintain the paid version.)
  • Consider Your Current Hosting Contracts
    Take a closer look at your agreements with WP Engine or any other hosting provider. Ensure there are clauses for service disruption and consider building in contingencies to protect your clients and your business.
  • Explore Diversification
    If you currently rely heavily on WP Engine, now might be the time to explore alternative platforms or hosting providers. There are several managed hosting services for WordPress (such as Kinsta, SiteGround, and Flywheel) that might offer better security against future legal risks.

The Takeaway

While the dispute between WordPress and WP Engine is still playing out, it serves as a reminder for all of us to regularly assess our vendor relationships and the legal environments they operate within.

By staying informed and proactive, you can continue amplifying your brand identity and delivering top-tier website services for your clients without disruption—no matter the outcome of this legal drama.

The CharTec team will be keeping tabs on this case as new developments roll out. We will post relevant updates as they come.

Sign up to receive our newsletter to get the latest news and tips straight to your inbox.