Every WordPress site runs on PHP, and every PHP version dies on a published schedule. After end of life, official security patches stop. Sites left behind run on an unpatched engine, and it sits on your infrastructure, under your brand.
WP Maintain manages the full PHP lifecycle across your fleet in three motions: find the at-risk sites, protect the ones that cannot move yet, and migrate the ones that can.
PHP Version Monitor: Find Every At-Risk Site
Real-Time Fleet Visibility
See the exact PHP version behind every site in your portfolio. Outdated and end-of-life runtimes are flagged automatically, with no manual auditing.
Early Warnings, Not Emergencies
Alerts fire when sites run unsupported or soon-to-be-deprecated versions, giving your team runway ahead of every EOL date and every forced-upgrade deadline.
Compatibility Awareness
Know which plugins, themes, and core versions will conflict with a runtime change before the change is made.
PHP Bridge: Protect Sites That Cannot Move Yet
Every fleet has stragglers: legacy custom code, abandoned owners, plugins that break on modern PHP. Forcing them breaks sites. Ignoring them leaves unpatched runtimes on your servers.
PHP Bridge Support is the program layer for exactly these sites.
Eligibility, Identified Automatically
The monitor flags which sites qualify, which PHP version they hold, and what blocks their upgrade, so the program runs on data, not guesswork.
Protection While They Wait
Legacy sites are hardened and shielded through security scanning, malware monitoring, and virtual patching integrations, reducing exposure while the runtime ages.
A Revenue Line, Not a Cost Center
Hosts retail PHP Bridge as a per-site monthly add-on. Customers on legacy runtimes pay for protection until they upgrade, then the charge falls away. The market has already proven this model at retail.
Built to Graduate
PHP Bridge is a bridge, not a destination. Every protected site is tracked toward an upgrade path, and the program is designed to shrink itself.
PHP Upgrades: Managed Migrations Off Dead Runtimes
Audit First
Each site is scanned for code that fails on the target PHP version. Outdated plugin and theme code is identified before anything moves.
Fix, Then Migrate
Incompatible code is resolved, the upgrade is proven on staging, and the site moves to a fast, supported runtime with approval and rollback at every step. No white screens, no surprise fatals.
Fleet Migrations, Not One-Offs
Sites move in controlled batches, grouped by risk and readiness. Compatible sites can upgrade automatically on an annual cycle, with failed upgrades rolled back instantly.
Why Hosts Run the Full Lifecycle
Retire Infrastructure Risk
End-of-life PHP on your servers is a security liability with your name on it. The lifecycle clears it systematically instead of one emergency at a time.
Free Your Platform Roadmap
Legacy sites are what stop infrastructure teams from retiring old runtimes. Protect the stragglers, migrate the rest, and deprecate on your schedule.
Earn on Both Sides
Bridge is recurring revenue from sites that wait. Upgrades are project revenue from sites that move. The monitor feeds both funnels automatically, and every migrated site gets a speed upgrade as a side effect.
Monitor finds them. PHP Bridge protects them. Upgrades graduate them. The platform keeps them current from then on. For fleets carrying legacy sites, these capabilities are packaged as the Legacy PHP Fleet Program with four lanes: protect, upgrade, freeze, and rebuild, including the Managed Static freeze, where WordPress stays the CMS but no PHP executes on the public site.