PHP fix. Our sites are patchedWhat to do
TopSyde
Abstract artwork of a smoky quartz crystal lit with muted gold light on a dark background

Where the WP Engine and Automattic Lawsuit Stands

WP Engine Automattic lawsuit status in plain English: what the court ordered, how plugin updates and ACF work today, and whether the case is a reason to move sites.

Rachel Nguyen

Rachel Nguyen

Senior WordPress Engineer

··13 min read

Last updated: November 22, 2026

As of this writing, WP Engine v. Automattic is still working through federal court in California. A December 2024 preliminary injunction keeps WP Engine connected to WordPress.org. For sites hosted there, plugin, theme and core updates run normally today. The lawsuit alone is a weak reason to migrate. Pricing, support and contract terms are better ones.

What is the WP Engine and Automattic lawsuit about?

The dispute is about money and the WordPress trademark. Automattic, the company behind WordPress.com, argued that WP Engine profited from WordPress without giving back and misused the brand. WP Engine argued that Automattic and Mullenweg tried to extort a licensing fee and used control of WordPress.org to damage its business.

It started in public. At WordCamp US on September 20, 2024, Mullenweg criticized WP Engine from the stage and followed with a blog post titled "WP Engine is not WordPress." His contribution comparison came from the Five for the Future pledge pages, which showed WP Engine pledging roughly 40 hours a week to WordPress core work against nearly 4,000 from Automattic (2024).

Cease-and-desist letters went both ways within days. According to the term sheet Automattic later published, it asked WP Engine to pay 8% of its monthly gross revenue as a trademark royalty, or commit that value in employee hours to WordPress development (2024). WP Engine declined and filed suit on October 2, 2024, with claims including attempted extortion, interference with contracts and antitrust violations. Automattic has since filed counterclaims, including trademark claims.

For your clients, the legal theories matter less than one question: can a fight between two companies stop the sites you host from getting updates? In 2024, for a few days, it did.

Where does the WP Engine lawsuit stand right now?

The case sits in the pretrial stage. The December 2024 preliminary injunction is still the order that governs day-to-day access, and the parties have spent 2025 and 2026 on motions over which claims and counterclaims go forward. A September 2026 scheduling order set a ten-day jury trial for October 2027. Check the public docket for the latest filings before you make a decision.

Here is how the main events line up, and what each one meant for a site hosted at WP Engine:

DateWhat happenedEffect on sites hosted at WP Engine
Sept 20, 2024Mullenweg criticizes WP Engine at WordCamp USNone on the sites themselves
Sept 23, 2024Cease-and-desist letters exchanged; 8% royalty term sheet surfacesNone
Sept 25, 2024WordPress.org blocks WP Engine servers from plugin and theme directoriesOne-click updates and installs from wp-admin fail
Late Sept 2024Block paused briefly; WP Engine deploys its own update sourceUpdates resume through WP Engine's mirror
Oct 2, 2024WP Engine files suit in N.D. CaliforniaNone
Oct 2024Login checkbox added to WordPress.org; ACF forked as Secure Custom FieldsSome ACF users on auto-update see the plugin swapped
Dec 10, 2024Preliminary injunction grantedAccess restored, checkbox removed, ACF listing returned
2025 onwardMotions, counterclaims, scheduling toward trialNo change to update access so far

The docket is public. Search "WP Engine v. Automattic 3:24-cv-06917" on CourtListener and you can read every order without a lawyer or a PACER account. News coverage of this case has been loud and partisan from both sides. The orders themselves are dry and clear.

A preliminary injunction is an early, temporary order. The judge found WP Engine likely enough to win, and likely enough to be harmed without the order, to restore the status quo while the case runs. It is not a final ruling. That distinction drives everything in the risk section below.

Can WP Engine sites still get plugin and WordPress updates?

Yes. Since the December 2024 injunction, sites at WP Engine pull plugins, themes and core updates the same way sites at any other host do. The one real outage of update access ran for a short stretch in late September 2024, and WP Engine worked around it with its own mirror.

What that week looked like matters, because it tells you what a worst case looks like. When WordPress.org blocked WP Engine's servers, the sites stayed up. Visitors saw nothing. What broke was the admin side: the "update now" button failed, plugin searches returned errors, and anyone setting up a new site couldn't install plugins from the directory. For an agency, that meant a pile of support tickets and some manual uploading. For a store owner, it meant a security patch could sit waiting.

WP Engine responded by building a replacement source for plugin and theme updates. That was a smart move, and it shows something about how hosts differ. A host that has its own tested path for updates can absorb an upstream problem. A host that depends entirely on a live connection to WordPress.org cannot.

If update timing on client sites is your worry, your own process matters more than the lawsuit. Testing updates on staging before they hit production protects you from a bad plugin release, which is far more common than a trademark dispute. Our guide to WordPress plugin update testing for agencies covers how to set that up.

What happened to Advanced Custom Fields?

On October 12, 2024, WordPress.org took over the free Advanced Custom Fields listing, which WP Engine maintains, and replaced it with a fork called Secure Custom Fields. The December injunction ordered the ACF listing returned. ACF and Secure Custom Fields now exist as separate plugins.

This was the part of the fight that touched the most sites. According to the WordPress.org plugin directory, ACF had more than 2 million active installations at the time of the fork (2024). Sites running the free version with auto-updates on could receive Secure Custom Fields in its place without anyone on the team approving the change.

ACF Pro was never distributed through WordPress.org, so Pro licenses kept updating from WP Engine directly.

If you manage client sites built on custom fields, spend ten minutes on each one. Open the plugins screen and confirm which plugin is installed: ACF, ACF Pro or Secure Custom Fields. Then decide on purpose which one you want to stay on, and note it in the client's documentation. Both work. Ending up on one by accident is what causes trouble six months later when a developer assumes the other.

Did the trademark fight change WP Engine's plans or support?

Mostly in naming. The WordPress Foundation updated its trademark policy page to call out WP Engine, and WP Engine dropped "WordPress" from its plan names and added a disclaimer that it is not affiliated with the WordPress Foundation. Support channels and service levels were not part of the dispute.

So the names on your invoice may have changed, but the product underneath did not. If you resell WP Engine hosting to clients under your own label, check that your proposals and contracts still match WP Engine's current plan names, since a mismatch looks careless in a renewal conversation.

Support quality at WP Engine is a separate conversation, and it predates the lawsuit. Agencies that complain about WP Engine tend to complain about plan limits, overage fees and what happened after the Flywheel acquisition, which we covered in what changed at Flywheel under WP Engine. Those are business issues with or without a court case.

Is the lawsuit a reason to move client sites off WP Engine?

For most site owners, no. The access risk that mattered was fixed in December 2024 and WP Engine has shown it can route around a block. The remaining risk is real but small: the injunction is temporary, and a final ruling could change the terms. Move for reasons you can price.

Here is the math an agency owner should run. Moving a typical brochure site takes 2-4 hours of someone's time once you include DNS, testing forms and checking redirects. At an internal rate of $100/hour, that's $200-$400 per site. Twenty client sites puts the move at $4,000-$8,000 of labor, plus the client conversations. That estimate assumes no surprises, and there are always a few.

Now compare that to the cost of the 2024 disruption: a few days of manual plugin uploads and some confused clients. Even if a block came back, WP Engine's mirror exists now. Spending $6,000 to avoid a repeat of a few inconvenient days is a poor trade.

The calculation changes when the lawsuit is the last straw on top of something else. Use this as a rough guide:

Your situationReasonable move
Happy with price and support, only worried about the lawsuitStay; check the docket every few months
Renewal coming up with a price jumpGet quotes now and compare on renewal price, not intro price
Hitting visit or storage overages every monthPrice a host that doesn't meter visits
Support tickets take days or bounce between tiersMove; slow support costs you every week, lawsuit or not
Clients ask about the lawsuit and you have no answerSend them this summary; you don't need to move to answer them

The thing I would watch for is the end of the case. A final judgment, a settlement or an appeal could reset the terms between WP Engine and WordPress.org. If you are going to act on the lawsuit at all, act on that news, and give yourself a 60-day migration plan you could start that week. Our WordPress migration guide lays out the order of steps so you're not inventing it under pressure.

What should you look for in a WordPress host if you do leave?

Look for a host that controls its own update and rollback process, gives you full downloadable backups, puts support response times in writing and lets you leave without penalty. Those four things protect you from upstream fights, from the host itself and from bad plugin releases equally.

The lawsuit's real lesson for agencies is about dependence. Any host can be caught between upstream parties, change ownership or make a mistake. One agency owner we wrote about watched a hosting support team wipe an entire server of client sites, and the only thing that saved some of them was backups stored somewhere the host couldn't touch.

When you compare hosts, ask each one these questions in writing:

  • Where do plugin and core updates come from, and can you hold or roll back an update per site?
  • Can I download a full backup (files and database) on demand, and how long are backups kept?
  • What is the written response time for a normal ticket and for a site-down ticket?
  • Are there visit, bandwidth or storage overages, and what does renewal cost compared to the first year?
  • If I leave, do you charge to export sites, and what happens to my backups?

Our vendor due diligence questions for a WordPress host goes further if you're running procurement for a larger organization.

For what it's worth, here is how TopSyde answers those. Plans start at $59/mo per site with no visit metering. A site-down ticket is answered within 15 minutes, 24/7, and other tickets within the times on our service level agreement: an hour for a broken checkout or form during business hours, one business day for other issues and change requests. Monitoring runs 24/7. Updates, backups and malware cleanup through TopSyde Sentinel are part of both plans, and the full list of what's covered sits on the spec sheet. On Complete, small content changes are covered too. AI edits let you or your client swap text, images and links from a chat, previewed first and undoable for 30 days.

If you're comparing several hosts side by side, start with our WordPress hosting comparison of WP Engine, Kinsta, Flywheel and TopSyde, which lines up pricing, backups, updates and the add-on costs that appear after signup. Agencies moving a batch of client sites should also read WP Engine alternatives for agencies moving 40 client sites and look at our agency hosting plans.

When you're ready to test it, monthly Complete plans on our pricing page start with a 30-day free trial, and we handle the migration. Move one site first, watch how support responds to your questions, and decide on the rest after you've seen it run.

Frequently Asked Questions

Is the WP Engine and Automattic lawsuit over?

No. As of this writing the case is still in pretrial proceedings in the Northern District of California, with a jury trial scheduled for October 2027. The December 2024 preliminary injunction remains in effect, and you can check the latest status on CourtListener under case 3:24-cv-06917.

Will my WP Engine site stop getting plugin updates again?

Not under current conditions. The injunction requires Automattic to keep WP Engine's access to WordPress.org open, and WP Engine built its own update source during the 2024 block. The risk returns only if the injunction is changed or the final outcome goes against WP Engine.

Should I switch from ACF to Secure Custom Fields?

You don't have to. Free ACF is again maintained by WP Engine on WordPress.org, ACF Pro updates directly from WP Engine, and Secure Custom Fields is a separate fork. Pick one deliberately for each client site and record the choice so the next developer knows which plugin the site depends on.

Do I need to tell my clients about the lawsuit?

Only if they ask or if it changes your recommendation. A short note explaining that updates work normally, that you're watching the case and that you have a migration plan if the outcome changes will answer most clients. Bringing it up unprompted tends to create worry without a decision to make.

What does it cost to move client sites away from WP Engine?

Labor is the main cost. A typical small business site takes 2-4 hours to move and test, so at $100/hour expect roughly $200-$400 per site in agency time. Some hosts, including TopSyde, include migration with the plan, which removes most of that cost for the sites you move.

Rachel Nguyen
Rachel Nguyen

Senior WordPress Engineer

8+ years WordPress & WooCommerce development

Rachel is a senior WordPress engineer at TopSyde specializing in WooCommerce performance and plugin architecture. She has built and maintained high-traffic e-commerce sites processing millions in annual revenue.

Related Articles

View all →

For agencies

Managing WordPress for clients?

White-label portal, volume pricing that drops as your portfolio grows, and a senior developer behind every site. Your clients see your brand. We do the work.

Complete $89 a site a month · Less from 11 sites · Free migration · 30-day free trial