Pressable and the Automattic-WP Engine Lawsuit: What Happens to Your Site If the Owner Picks Sides

Q: Does Automattic own Pressable?

Yes. Automattic acquired Pressable in 2015. Pressable runs on Automattic's WP Cloud platform, the same infrastructure behind WordPress.com and WordPress VIP. Matt Mullenweg, CEO of Automattic, also personally controls WordPress.org, which hosts the plugin directory, theme directory, and update API that every WordPress site depends on. Pressable has not issued any independent public statement about the WP Engine lawsuit. All communication comes through Automattic's corporate channels.

Q: Did Pressable benefit from the WP Engine ban?

One day after Automattic banned WP Engine from WordPress.org on September 25, 2024, Pressable launched marketing ads targeting WP Engine customers who could no longer update their plugins. Pressable offered $100 per migrated site (capped at $10,000) plus free migration services and contract credit matching. WordPress.org published a promotions page listing Automattic's own three hosting brands (WordPress.com, Pressable, WordPress VIP) as WP Engine alternatives. A class action lawsuit specifically alleges that Automattic publicly pressured WP Engine customers to leave while its own hosting brands directly solicited them with migration incentives.

Q: Is Pressable safe to use?

Technically, Pressable was never disrupted during the WP Engine conflict. The hosting product itself continued operating normally. The risk is structural: you are hosting on a platform whose parent company demonstrated willingness to cut off a competitor's access to core WordPress infrastructure, seize a plugin with over 2 million active installs (Advanced Custom Fields), and allegedly plan trademark royalty demands for 10 other hosting competitors. For most users this is abstract. For anyone who values platform neutrality or worries about governance concentration, it is a concrete concern. Your WordPress content, themes, and standard plugins are portable regardless.

Q: Can I migrate away from Pressable easily?

Yes. Pressable supports standard WordPress export (WXR), database export via phpMyAdmin, and file access via SFTP and WP-CLI. All-in-One WP Migration, Duplicator, and similar migration plugins work normally. Competitor hosts including Kinsta, Cloudways, and Rocket.net offer free managed migration from Pressable. The portability risk is not WordPress itself but the Automattic ecosystem: if you also use Jetpack, WooCommerce, Akismet, and Pressable-specific caching and CDN integrations, untangling those dependencies takes more work.

By Daniel Brooks · Updated 2026 · WordPress developer tracking managed hosting

Affiliate disclosure: some links below are affiliate links. Lawsuit details are sourced from court filings, TechCrunch reporting, and The Repository. Pressable pricing is from their official website.

Pressable is owned by Automattic. Automattic employs the CEO of WordPress.org. When Automattic banned WP Engine from WordPress.org on September 25, 2024, WP Engine's customers could not install or update plugins. The next day, Pressable ran ads targeting those stranded customers. Within weeks, Automattic seized control of the Advanced Custom Fields plugin (2 million+ active installs), renamed it, and pushed the replacement to every site running ACF. A court eventually ordered Automattic to restore access. The question that matters for Pressable customers is not whether this will happen again, but what it means that your host and your platform's gatekeeper are the same company.

The ownership chain

Pressable was founded in 2010 and acquired by Automattic in 2015. It runs on WP Cloud, Automattic's proprietary hosting infrastructure that also powers WordPress.com and WordPress VIP.

Automattic is a private company. Its CEO, Matt Mullenweg, is also the co-creator of WordPress. During court proceedings in October 2024, Automattic's legal team stated that WordPress.org is Mullenweg's "personal property." The WordPress.org infrastructure includes:

The plugin directory (where every WordPress plugin is hosted and updated from)
The theme directory
The core update API (how WordPress checks for and downloads updates)
The translation system

When you host on Pressable, your WordPress site depends on WordPress.org for plugin updates, theme updates, and core WordPress updates. The entity controlling that infrastructure is the same entity that owns your host. No other managed WordPress host has this structural relationship. WP Engine, Kinsta, Cloudways, and SiteGround all depend on WordPress.org, but none of them are owned by the company that controls it.

What happened in 2024-2026

The conflict started as a trademark and revenue dispute and escalated into a governance crisis for the WordPress ecosystem.

September 2024: Mullenweg called WP Engine "a cancer to WordPress" at WordCamp US. He demanded 8% of WP Engine's monthly gross revenue (estimated at $32 million per year) as a trademark royalty. When WP Engine did not agree within 24 hours, Automattic banned them from WordPress.org. WP Engine's customers lost access to plugin and theme updates.

October 2024: Automattic seized the Advanced Custom Fields plugin, owned by WP Engine, from the WordPress.org plugin directory. They renamed it "Secure Custom Fields" and pushed an automatic update to every ACF user. The plugin's product manager called it "an extraordinary abuse of trust." WP Engine filed a lawsuit with 20 claims including monopoly abuse, extortion, and cyberattacks. 159 Automattic employees (8.4% of the company) accepted voluntary severance.

December 2024: A U.S. District Court granted a preliminary injunction, ordering Automattic to restore WP Engine's access and return the ACF plugin. Mullenweg responded: "It's hard to imagine wanting to continue working on WordPress after this."

April 2025: Automattic laid off 16% of its workforce (approximately 270-280 employees), with cuts at WooCommerce, Tumblr, and AI teams.

June 2025: BlackRock devalued Automattic shares to $27.74, down 67% from the 2021 Series E valuation of $85 per share. The devaluation continued through August 2025 to 32.6% of 2021 value.

February 2026: WP Engine's third amended complaint alleged that Automattic planned to target 10 hosting competitors with trademark royalties, not just WP Engine. The filing claims Newfold (parent of Bluehost and HostGator) is already paying.

September 2027: Jury trial is scheduled. No settlement has been reached. The case remains active.

Pressable's role during the conflict

One day after the WordPress.org ban, Pressable launched marketing ads targeting WP Engine customers who could no longer update their plugins. The timing was not subtle. Pressable offered $100 per site migrated (capped at $10,000), free migration services, and contract credit matching for customers leaving WP Engine.

WordPress.org published a promotions page listing Automattic's three hosting brands (WordPress.com, Pressable, WordPress VIP) as alternatives to WP Engine. The page appeared on WordPress.org, the infrastructure site that Automattic had just used to ban WP Engine.

A class action lawsuit against Automattic specifically alleges that the company "publicly pressured WP Engine customers to leave by listing them on the WordPress Engine Tracker website, while Automattic-owned hosting brands directly solicited them with incentives to migrate."

Pressable has issued no independent public statement about the dispute. No blog post, no FAQ, no acknowledgment. All communication has come through Automattic's corporate channels. Pressable is marketed as a separate brand, but during the defining governance crisis of the WordPress ecosystem, it operated as Automattic's customer acquisition arm.

What this means for your site

Pressable itself was never disrupted. The servers kept running. The hosting product continued functioning normally. If you are a Pressable customer who does not care about WordPress governance, nothing material changed for you during the conflict.

The risk is structural, not operational:

Your host is the platform gatekeeper. Every WordPress site depends on WordPress.org for plugin updates, theme updates, and core updates. Pressable's parent company controls that infrastructure. They demonstrated willingness to cut off a competitor's access. WP Engine's February 2026 filing alleges Automattic planned to target 10 competitors. If your business depends on WordPress stability, having your host and your platform gatekeeper be the same entity is a concentration risk that no other managed WordPress host carries.

No editorial independence, and the ecosystem deepens the dependency. Pressable has not once publicly stated its own position on the conflict, the ACF seizure, the governance questions, or the workforce reductions. For a brand marketing itself as a standalone hosting company, the silence is telling. And the silence matters more if you are also running Jetpack (Automattic), WooCommerce (Automattic), Akismet (Automattic), and WordPress.com email (Automattic). Your entire web business sits inside a single vendor's ecosystem, with every product subject to bundling, repricing, or deprecation according to Automattic's corporate needs, not yours.

Valuation decline. BlackRock's valuation cuts from $85 to under $28 per share represent a 67% decline. Automattic laid off 16% of staff. Pressable runs on Automattic's WP Cloud infrastructure. The financial health of the parent company directly affects the hosting subsidiary's long-term viability. This is not a prediction of failure; it is a risk factor that does not exist when you host with an independent company.

Portability is preserved. WordPress itself is portable. Your content exports via WXR. Your themes and plugins are standard. Your database is MySQL. If you decide to leave Pressable, migration plugins (Duplicator, All-in-One WP Migration) work normally. Kinsta, Cloudways, and Rocket.net all offer free managed migration from Pressable. The hard part is untangling Automattic-specific integrations (Jetpack features, Pressable caching, Pressable CDN), not moving WordPress itself.

The FAIR project and what it solves

The WordPress community's response to the governance crisis was the FAIR project (Federated and Independent Repositories), launched at WordCamp Europe in Basel in June 2025. Backed by the Linux Foundation, built by approximately 300 contributors including veteran WordPress core committers.

FAIR's goal: create alternative infrastructure for WordPress plugin and theme distribution so that no single person or company can cut off access for everyone else. If FAIR reaches production use, the structural risk of WordPress.org being a single point of control diminishes. Hosts would no longer depend entirely on WordPress.org, and the power that Automattic exercised during the WP Engine ban would be reduced.

FAIR is not production-ready. It launched in June 2025 with active development through early 2026. Whether it reaches the critical mass needed to serve as a real alternative to WordPress.org depends on hosting companies and plugin developers adopting it. But its existence is a direct consequence of what Pressable's parent company did, and its success would directly reduce the governance risk that comes with hosting on an Automattic-owned platform.

WordPress market share declined from 43.6% in January 2025 to 41.9% in May 2026. Six consecutive months of decline. The timing correlates with the conflict. Whether the dispute caused the decline, accelerated an existing trend, or is coincidental is not established. But the perception of governance instability is measurable.

FAQ

Does Automattic own Pressable?

Yes. Acquired in 2015, Pressable runs on Automattic's WP Cloud infrastructure. Matt Mullenweg, CEO of Automattic, also controls WordPress.org, which hosts the plugin and theme directories and the core update API. No other managed WordPress host has this relationship with the platform's core infrastructure.

Did Pressable benefit from the WP Engine ban?

Pressable launched marketing ads targeting WP Engine customers one day after the ban, offering $100 per migrated site. WordPress.org published a page promoting Automattic's hosting brands as alternatives. A class action lawsuit alleges Automattic pressured WP Engine customers to leave while its own brands solicited them with incentives.

Is Pressable safe to use?

The hosting product was not disrupted during the conflict. The risk is structural: your host's parent company controls WordPress.org and demonstrated willingness to use that control against a competitor. WP Engine's 2026 filing alleges Automattic planned similar actions against 10 other hosts. For most users this is abstract. For businesses that need platform neutrality, it is a concrete concern.

Can I migrate away from Pressable easily?

Yes. Standard WordPress migration tools work normally. SFTP, WP-CLI, and database export are available. Competitor hosts offer free managed migration. The difficulty scales with how deep you are in the Automattic ecosystem (Jetpack, WooCommerce, Akismet, WordPress.com email). WordPress itself is portable; the Automattic integrations take more work to untangle.