PHP versions reach end of life on a fixed schedule, and many sites stay behind: a plugin breaks, custom code was never updated, or nobody owns the upgrade. There are two ways out. You can patch the old version so it stays secure for longer, or you can upgrade the site to current PHP. Patching buys time; upgrading ends the problem.
How we chose
- Upgrade or patch: does it move sites to current PHP, or keep old versions secure?
- Coverage: which PHP versions, and WordPress only or any PHP application?
- Testing: are upgrades tested on staging before they reach production?
- Fit for hosts: panel extensions, add-ons to resell, and fleet scale.
- Support: who answers when an upgrade or patch goes wrong.
Verdict
SeaPHP is our pick for custom PHP applications that need a real upgrade or a move to Next.js. For WordPress fleets, WP Maintain is the only service that includes the PHP upgrade itself in care, so sites move to current PHP and stay there instead of paying to patch the past. When sites must stay on old PHP for now, ZendPHP and TuxCare offer long-term security patches, and CloudLinux OS includes hardened PHP on shared servers.
For isolating tenants and limiting resources on those servers, see our server isolation tools list.