More reliable safe updates. Verploy distinguishes between kinds of failure (a slow or briefly unreachable site, a firewall or security plugin, rate limits, a wrong server clock, a broken pairing, or a fault in Verploy itself) and handles each differently: temporary failures are retried after a suitable pause; persistent ones are explained with what you can do. Sites that redirect (http to https, with or without www) work without re-pairing.
Pre-check per update. If a new version requires a newer PHP or WordPress version than the site has, that update is left out with an explanation and the others continue. Too little disk space for a test copy is reported before anything starts.
Rollbacks are checked before they count as done. When an update is rolled back, it is only reported as rolled back after the tested pages have been reloaded and the installed versions have been compared with the site.
Risk per update on the site page (low, medium, high, or not available through WordPress), with the reasons.
Staged “update on all sites”. Updating a component on all sites starts with one site, then two, then the rest. If an update breaks something, Verploy pauses and leaves the other sites untouched until you choose to continue or stop.
Overview “Your sites”: one status line per site. What needs your action is shown in orange or red; what is outside your control, or what Verploy handles itself, in grey.
Includes 2.15.1 (PHP end-of-support notice shown correctly in the site status).