WP-Engine Banned From WordPress.org

In a recent blog post, Matt Mullenweg, the co-founder of WordPress, addressed issues faced by WP Engine customers, advising them to contact WP Engine support directly for assistance. Mullenweg touched on the widespread disruptions caused by WP Engine’s actions, which affected thousands of customer sites in what he describes as a poorly executed attempt to manipulate WordPress’s core functionality for profit.

Rather than delving into all the details, Mullenweg focused on the key issue: WP Engine is no longer allowed free access to WordPress.org’s resources. This decision comes after WP Engine’s decision to lock down and disable an essential WordPress feature, which has sparked legal disputes between WP Engine and WordPress.org.

Mullenweg argued that WP Engine’s attempts to control the WordPress experience come with significant responsibilities. If WP Engine wants to maintain control, it must independently manage user login systems, update servers, plugin and theme directories, security protocols, and other essential services—tasks that WordPress.org had previously supported. WP Engine will now need to replicate the security research that WordPress.org has developed over the years, a task that will no longer benefit from the collaborative efforts of the larger WordPress community.

Mullenweg questioned why WordPress.org should continue to provide these services for free, given WP Engine’s antagonistic actions against the platform. He made it clear that WP Engine customers are essentially left with a “hacked up, bastardized version” of WordPress that no longer aligns with the open-source, community-driven philosophy that WordPress was built upon.

In closing, Mullenweg urged users who want the authentic WordPress experience to seek hosting services elsewhere. According to him, WP Engine is no longer representative of the true WordPress platform and should not be mistaken for the broader WordPress community.