Our real numbers: 100 went live, 90 held back, 16 rolled back

2 min readBy the Verploy team

Real update runs, 30 days to 2 October 2026Went live after every check100Held back on the test copy90Rolled back automatically16Our own agency’s client sites. Updated monthly.

We use Verploy on our own agency’s client sites every day. On the homepage we show the result of 30 days of real update runs, up to 2 October 2026:

  • 100 updates went live after passing every check.
  • 90 were held back on the test copy. The live site was never touched.
  • 16 were rolled back automatically after going live.

We update these numbers every month.

Why we show the held-back number

A tool that only shows its successes is hard to trust. Every held-back update is a site that did not break in front of a client. But we also know that some of those 90 did not need to be held back: a visual difference that was only a changed banner, a premium plugin without an active licence, a site problem that was there before the update.

What we changed because of it

  • More updates go live by themselves when every check passes.
  • When only the look of a page changed, you see before and after side by side and approve it with one click.
  • Small, proven plugin updates go live directly, with a backup, a check afterwards and an automatic rollback.
  • Known site problems are not retried; you are told once what blocks the update.
  • Updates without a download file are marked “not available” instead of “held back”.
Example of the Verploy overview: sites, what needs action, updates deployed and held back (example data)
The Verploy overview. (Example data, not the numbers above.)

What comes next

The next monthly update of these numbers will show whether these changes worked. We will publish it here, including the parts that did not go as planned.

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