Black Friday 2026: sign up before 30 November and keep 40% off for life when you upgrade after your 3 free months. No credit card now, no annual prepay. Start freeBlack Friday 2026: registrati entro il 30 novembre e mantieni il 40% di sconto per sempre passando a un piano dopo 3 mesi gratis. Niente carta, niente anticipo annuale. Inizia gratisBlack Friday 2026: meld je aan vóór 30 november en houd voor altijd 40% korting als je na je 3 gratis maanden upgradet. Geen creditcard nu, geen jaarlijkse vooruitbetaling. Begin gratisBlack Friday 2026: Bis 30. November registrieren und nach 3 Gratismonaten dauerhaft 40 % Rabatt beim Upgrade behalten. Keine Kreditkarte, keine Jahresvorauszahlung. Kostenlos starten Black Friday 2026 : inscrivez-vous avant le 30 novembre et gardez 40 % de remise à vie sur votre formule après 3 mois gratuits. Sans carte, sans paiement annuel. Commencer gratuitement Black Friday 2026: regístrate antes del 30 de noviembre y conserva un 40 % de descuento de por vida al pasar a pago tras 3 meses gratis. Sin tarjeta ni pago anual. Empieza gratis Black Friday 2026: cadastre-se antes de 30 de novembro e mantenha 40% de desconto para sempre ao assinar após 3 meses grátis. Sem cartão, sem pagamento anual. Começar grátis Black Friday 2026: zarejestruj się przed 30 listopada i zachowaj 40% zniżki na zawsze, gdy przejdziesz na płatny plan po 3 darmowych miesiącach. Bez karty teraz, bez rocznej przedpłaty. Zacznij za darmo Black Friday 2026: tilmeld dig inden 30. november og behold 40 % rabat for altid, når du opgraderer efter dine 3 gratis måneder. Intet kreditkort nu, ingen årlig forudbetaling. Start gratis Black Friday 2026: registrera dig före 30 november och behåll 40 % rabatt för alltid när du uppgraderar efter dina 3 gratismånader. Inget kreditkort nu, ingen årlig förskottsbetalning. Börja gratis

Safe updates

Safe WordPress updates, with evidence for your agency.

Verploy tests risky updates on a private copy of your site first, puts small, proven plugin updates live with a snapshot and a check, and verifies every update after. If a supported post-update check fails, Verploy attempts recovery and records the outcome; recovery can require manual intervention.

How it works

See Verploy in 80 seconds.

How an update is checked, tested on a copy when it is risky, and held back or rolled back when something looks off.

Start free →

Plays from YouTube once you click. Watch on YouTube

Safe updates

Risky updates are checked on a copy before deployment.

Verploy builds a temporary test copy on your own server. The copy shares the server environment, but a successful test does not prove every live workflow will work.

A safe update that was held back: the homepage returned HTTP 500 on the test copy, so the live site was not changed. Diagnosis and next steps shown (example data)

Shown: a real update that was held back because the test copy failed. The live site was never touched.

Read more: which updates go to a test copy first and what happens when an update goes wrong.

On sites with the data guard, the site is in maintenance mode only during the switch itself, and orders or form entries made around an update are kept even if a rollback is needed.

01

A private test copy

Built on your own server, with the same PHP version and limits. Invisible to visitors and search engines, and it never sends email.

02

The update runs there first

Updates routed to a test copy run there first. Eligible lower-risk plugin updates can use the direct route with a snapshot and live checks.

03

Verploy checks the result

The pages included in the run are compared before and after the update, on desktop and mobile. After a theme or page-builder update, styles are rebuilt first.

04

Review the result before deployment

A blocking failure detected on the test copy holds deployment back. Review reported differences and any supported approval step; untested pages and workflows remain outside this evidence.

05

The live site is checked again

Right after going live, Verploy compares the site with how it looked seconds before. Alerts by email, Slack or webhook.

06

Problem? Recovery with a recorded outcome

Verploy attempts recovery from the pre-update snapshot when supported checks require it. Inspect the recorded result: restoration can fail or preserve data and require manual follow-up.

See it work

A real update run, replayed.

Two runs from 24 September 2026, step by step. One update was stopped on the test copy before it could reach the live site. The other was tested, put live and verified.

Verploy · Safe update · WooCommerce shop (anonymised)

5 updates, including WooCommerce 11.0.1 → 11.1.2

24 September 2026 · duration 3:59

  1. 19:258 pages chosen to testHome, news, about, contact, shop, cart, checkout, plus the login page
  2. 19:26Baseline on the live site17 of 17 measurements OK
  3. 19:26Test copy created on the same server31,252 files, 99 database tables
  4. 19:28Updates installed on the test copyPremium plugin fetched with the site’s own licence
  5. 19:29Test failed: news page, desktop4.2% visual difference, 2% allowed
  6. 19:29Go-live skipped, test copy removed
Stopped. Nothing went live.

The live site was never touched. Verploy explained why and suggested the next step: check the difference image, then mask the changing element or keep the current versions.

Page on the test copyDesktopMobile
Home0.0%0.0%
News4.2%0.0%
About0.0%0.0%
Contact0.0%0.0%
Shop0.0%0.0%
Cart · Checkout0.0%0.0%
News page section before the update, blurred for privacy
Before the update
The same section after the update, changed pixels marked in red
After, with the difference in red

Replays of two real Verploy runs on 24 September 2026. Site names are anonymised and screenshots blurred; times, steps and percentages are unchanged.

Verification

More than a screenshot comparison.

Verploy measures the pages included in the run before and after an update, on desktop and mobile. Only new problems count: issues your site already had won't block an update.

Pages still load

Reachability, HTTP status, and PHP or WordPress error pages.

No new JavaScript errors

Console errors that weren't there before the update.

Scripts and styles load

Your site's own CSS and JavaScript files still load.

Layout stays intact

Pixel comparison per page, with a threshold you choose and masks for sliders or dates.

Structure is still there

Header, navigation, main content and footer haven't disappeared or halved.

Login form is present

The WordPress login form still appears as it should.

Supported form and checkout checks

A contact form is filled in and submitted, and on a WooCommerce site a product is added to the cart and the checkout opened, on the test copy. Nothing is sent, paid or ordered. Forms with a captcha are skipped.

When something goes wrong

A failed update needs a clear next step.

Verploy is built for the moment an update breaks something. The run records detected problems and recovery outcomes so your team can decide what to do next.

Stopped on the copy

If a check fails on the test copy, nothing happens to your live site. You get a notification with the diagnosis.

Rolled back on live

When supported live checks detect a problem, Verploy attempts recovery. Confirm the outcome before calling the site restored; failed or incomplete recovery needs manual attention.

Explained in plain language

Every stopped or rolled-back update comes with an explanation: which plugin, what went wrong and what you can do.

You stay in control

Every run is transparent.

Choose which updates to run, per site or in bulk. Each run has a timeline with every step, and before, after and difference screenshots per page.

  • Test settings per site: pages, threshold and masks
  • Timeline for every update run
  • Before, after and difference screenshots
  • Critical alerts by email; other maintenance outcomes in the periodic summary

What you give us access to

One small plugin. No passwords.

You install the Verploy Connector plugin and pair it with a one-time code. Verploy never asks for WordPress passwords or hosting logins, and every request between Verploy and your site is signed. The test copy is built on your own server and removed after each run.

  • No WordPress passwords, no hosting account access
  • Test copy on your own server, deleted after the run
  • Nightly backups encrypted and stored in the EU
  • Disconnect a site at any time by deactivating the plugin

The full picture, including what we store and for how long, is on Trust & data.

Spend less time checking WordPress.

Let Verploy do the maintenance work.

3 months free, up to 40 sites. No credit card.