 | |
| Company type | Private |
|---|---|
| Industry | Web hosting |
| Founded | 2010 |
| Founder | Jason Cohen |
| Headquarters | Austin, Texas |
Key people | Heather Brunner (CEO), Jason Cohen (CIO) |
| Owner | Silver Lake [1] |
| Website | wpengine |
WP Engine is an American hosting company that provides hosting services for websites built on the open-source content management system WordPress. [2] It was founded by Jason Cohen in 2010 and is headquartered in Austin, Texas. [3] [4] [5] [6]
WP Engine's main function is allowing businesses and organizations to build, host, and manage websites powered by WordPress. [4] [7] [8] [9]
WP Engine was founded by Jason Cohen and Ben Metcalfe in 2010. [3] [5] [6] Prior to founding WP Engine, Cohen was the founder of the software company SmartBear Software. [3] In May 2013, WP Engine hired former Bazaarvoice COO Heather Brunner as its COO. [10] [11] Brunner was eventually appointed the company's CEO in October 2013, with Cohen assuming the position of CTO. [11] WP Engine hired Lee McClendon, formerly of SolarWinds, as its first Senior Vice President of Global Engineering in 2017. [12]
WP Engine expanded into Europe in 2016, establishing offices in Limerick, Ireland. [13] [14] [15] In 2019, the company expanded its offices into The Domain, a mixed-use development in Austin, Texas. [16] In addition, WP Engine also expanded its offices into the Limerick city centre in 2023. [17]
In 2018, WP Engine sold majority of its stakes to Silver Lake for investing $250 million. [18] At the time they had 75,000 customers. [19]
In 2021, the company reorganized its business into three service lines: enterprise-size business, small to medium-size business and international business. [4]
In 2022, WP Engine announced that it was ending support for the website managing tool .htaccess. [20] WP Engine also announced the launch of Atlas, its headless WordPress solution, in the same year. [21] The Atlas platform includes Atlas Blueprints, which provides developers with free website templates designed by professionals, and Atlas Sandbox, which allows users to create prototype headless WordPress projects. [21] In March 2024, WP Engine Introduced AI-Powered Search for WordPress Sites. [22]
WP Engine launched its platform on Microsoft Azure in 2022. [23]
WP Engine formed a partnership with digital agency Granite Digital to expand its presence in Ireland in 2023. [24]
Annually, WP Engine holds WP Engine DE{CODE}, a developer conference centered around sharing technical knowledge with the WordPress community. [25]
In November 2017, it became the first WordPress solution to be certified in Amazon Web Services' Competency Program. [19] In a 2023 study conducted by StatusGator, WP Engine was named one of the most reliable WordPress hosting providers based on downtime data. [26] WP Engine has been ranked as one of the top 10 most popular hosting companies by several publications. [27] [28] [29]
During the week preceding September 22, 2024, Matt Mullenweg—founder of WordPress.com—began speaking negatively about rival WP Engine. Mullenweg gave a speech at WordCamp US 2024 that argued that WP Engine had made meager contributions to WordPress compared to Automattic, criticized WP Engine's significant ties to private equity, and called for a boycott, sparking internet controversy. [30] In response, WP Engine issued a cease and desist against what it characterized as defamation and extortion, attributing his attacks to WP Engine's refusal to pay Automattic "a significant percentage of its gross revenues – tens of millions of dollars in fact – on an ongoing basis" for what it claimed were necessary trademark licensing fees (later clarified as 8% of all revenue, payable in gross or in salaries for its own employees working under WordPress.org's direction, combined with a clause that would've prohibited forking [31] ) for the "WordPress" name. [32] Automattic responded by sending its own cease and desist the next day, citing the trademark issue. [33] On October 2, 2024, WP Engine sued Automattic and Mullenweg for extortion and abuse of power, which the defendants denied. [31]
As a result of the dispute, WordPress.org blocked WP Engine and affiliates from accessing its servers—which include security updates, the plugin and theme repository, and more—on September 25, 2024. This was a day after its trademark policy was updated [34] to ask against usage of WP "in a way that confuses people", listing WP Engine as an example. [35] Following backlash, access to WordPress.org was temporarily restored until October 1 to allow WP Engine to build its own mirror sites two days later, [36] [37] which the company did. [35] On the 12th, WordPress.org replaced the listing of WP Engine's Advanced Custom Fields (ACF) plugin on the WordPress.org plugin directory with a fork called "Secure Custom Fields" citing a guideline that empowers the foundation to "make changes to a plugin, without developer consent, in the interest of public safety". [38]
On October 7, 2024, to align the company's stance, Mullenweg announced that 159 employees—8.4% of Automattic—had quit in exchange for a severance package of $30,000 or six months of salary, whichever is higher, with the condition that the resigned would not be able to return. [39] The next week concluded another offer of nine months' salary to attempt to placate those who could not quit for financial reasons, [40] though with only four hours to respond and the added term of being excluded from the WordPress.org community. [35]
On December 10, 2024, a preliminary injunction was issued by judge Araceli Martínez-Olguín of the District Court for the Northern District of California stating that Automattic and Matt Mullenweg must cease blocking, disabling, and interfering with WP Engine and its associates’ access to WordPress.org. [41]
In February 2025, a class action lawsuit was filed by a WP Engine customer, accusing Automattic and Mullenweg of "deliberately abusing their power and control over the WordPress ecosystem to purposefully, deliberately, and repeatedly disrupt contracts", stating that the company's interference with WP Engine's operations caused disruptions in the maintenance and security of customer's own websites. [42] [43]
