One plugin, all your sites: why Verploy updates in waves

A new version of a popular plugin comes out. You run it on thirty client sites. Updating all thirty at once is fast, until the new version turns out to conflict with something, and thirty clients have the same problem at the same time.

Waves, not a big bang

With “update on all sites”, Verploy does not start everywhere at once. Wave one is a single site. Wave two is two more. Wave three is the rest. The next wave only starts when the previous one is finished, and every site in every wave goes through the normal safe update route.

The right order

Sites with the most successful updates go first; shops go last. If something goes wrong, it goes wrong on the site that can best handle it, not on your biggest webshop.

Pause on failure

If the update breaks a site in an early wave, Verploy pauses the rollout. The remaining sites are not touched until you have looked at what happened.

Want to see it on your own sites? Start free on up to 3 sites, no credit card.