Ownership
No one can take your site hostage.
WordPress the software is open source. The servers most WordPress sites take their updates and plugins from are a different matter. Below is what happened on those servers in 2024, by date, from the published record, with a link to each source. Draw your own conclusion.
Every source was opened and read on 20 November 2026. We state only what each one states.
The record
What happened, by date
1 of 8
WordPress.org publishes “WP Engine is not WordPress”
A post on WordPress.org News, written in the first person by Matt Mullenweg, says of a hosting company: “WP Engine needs a trademark license to continue their business.”
- Who it affected
- WP Engine, a company that hosts WordPress sites, and its customers.
2 of 8 · 4 days later
WP Engine is cut off from WordPress.org's servers
A second post, titled “WP Engine is banned from WordPress.org”, says: “WP Engine no longer has free access to WordPress.org’s resources.” It lists what that covers, including the update servers and the plugin and theme directories.
- Who it affected
- Sites hosted by WP Engine. The post tells “any WP Engine customers having trouble with their sites” to contact WP Engine.
3 of 8 · 2 days later
A block lifted for four days
WordPress.org writes that it has heard from WP Engine customers that updates, the plugin directory and the theme directory have not worked on their sites, and that it has lifted the block “until October 1”.
- Who it affected
- WP Engine's customers.
4 of 8 · 15 days later
The Advanced Custom Fields listing is replaced with a fork
WordPress.org announces it is “forking Advanced Custom Fields (ACF) into a new plugin, Secure Custom Fields”, and that sites with automatic updates from WordPress.org switched on will be moved from one to the other by the update. The ACF team writes the same day that the code under its listing was no longer controlled by the ACF team.
- Who it affected
- Sites running Advanced Custom Fields that update through WordPress.org. The plugin's listing shows 2+ million active installs today.
5 of 8 · 59 days later
A court orders access restored
In a lawsuit brought by WP Engine, a California district court judge rules that Automattic and Matt Mullenweg must restore WP Engine's access to WordPress.org as it was on 20 September, and its access to and control of the Advanced Custom Fields listing.
- Who it affected
- WP Engine, its customers, and sites running Advanced Custom Fields.
6 of 8 · 10 days later
WordPress.org pauses sign-ups and new plugin and theme submissions
A post titled “Holiday Break” says WordPress.org is pausing new account registrations, new plugin directory submissions, new plugin reviews and new theme directory submissions.
- Who it affected
- Anyone opening a WordPress.org account, and authors submitting a new plugin or theme.
7 of 8 · 661 days later
Where the plugin stands now
The ACF team's page, last updated on this date, says Advanced Custom Fields is available in the WordPress.org plugin directory, where the ACF team at WP Engine publishes and maintains it.
- Who it affected
- Sites running Advanced Custom Fields.
8 of 8 · 21 days later
A lawsuit by WP Engine customers is still in court
The Repository reports that Automattic and Matt Mullenweg have asked a federal judge to send two WP Engine customers who are suing them into private arbitration, which would end the case as a class action if the judge agrees, and that the parties are due to meet a mediator on 3 December.
- Who it affected
- WP Engine customers who were affected in 2024.
What this means if your site is WordPress
A WordPress site that takes its updates and plugins from WordPress.org depends on WordPress.org's servers staying open to it.
In 2024 those servers were closed to one hosting company's customers, and one plugin's listing was replaced, until a court ordered both undone. Whether that could happen to your host or to a plugin you rely on is not something you get a vote on. That is a fact about how the system is arranged, not about anyone's intentions.
TechCrunch describes WordPress.org as
a theme and plug-in repository owned by Mullenweg
The contrast
A Hostless Duck site has no centre to seize
These are facts about how a Hostless Duck site is built, not promises about how we will behave. Each one can be checked in the code of a site you have built.

- Your site is files on your own accountIt runs on your own Cloudflare account or your own server. Hostless Duck hosts nothing.
- A built site never calls Hostless DuckIt contacts only the services you switch on yourself, such as your email provider.
- No central server can revoke itA built site holds no Hostless Duck key, and the delivery server holds no key to your site.
- Cancel Hostless Duck and it keeps runningIt stays up and editable on your own account. You stop getting updates, new modules and support.
- Export is part of Core, and tested every releaseOne file with every database table and your settings, plus a list of your media files, which already sit in your own storage.
- The delivery server can stop serving new modules. It cannot touch a built site.It only answers requests for items. It makes no request to your site.
- What you do give up if you cancel
- Updates, new modules and support.
- What stays
- The site, its files and its data, running on your own account.
See if your site can leave.
A real scan of your public pages, never a made-up result. No card.

