For hosting companies
Customers stuck on old PHP? Take it off the internet.
Some of your customers can't move off PHP 7.4 or 8.1 without breaking their sites. After PHP2Shell, leaving them as they are isn't comfortable either. WranglePress serves those sites' public pages as static files from Cloudflare, so the old PHP only faces the site's own editors while they plan an upgrade.
The problem you're holding
- No upstream fix. PHP 7.3 and older got no PHP2Shell fix from the PHP project, and 7.4 to 8.1 got only minimal backports.
- Upgrades break things. Old themes and plugins fail on new PHP, and the support tickets land on you.
- The deadline keeps coming. PHP 8.2 loses support on 31 December 2026. About 57% of WordPress® sites will then be on unsupported PHP.
What WranglePress gives your customers
- A public site with no PHP. Same pages, same addresses, served from Cloudflare's network.
- Nothing to migrate. The site stays on your servers. You keep the hosting customer.
- Editing as usual, or none at all. Their WordPress stays where it is, behind a login, or they retire it if the site never changes.
- Time to upgrade properly. Old PHP stops being an emergency.
Built for doing it at scale
WranglePress's MCP server lets you, or your support team's AI assistant, add and build up to 25 sites per request and up to 75 builds at once. Moving a batch of affected customers doesn't mean clicking through a dashboard hundreds of times. See the AI assistant tools.
Working together
We'd like to work with hosts on volume pricing, and on offering WranglePress to affected customers as an option in your control panel or support replies. If that interests you, email us with roughly how many sites are on end-of-life PHP.