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

Release notes

One release a month. Tested first.

New features reach the monthly release only after they have run on our own client sites. Fixes ship in between, without ceremony. Everything below is live in the app before it appears here.

Next release: early December 2026 · Current status and incident history: status.verploy.com

In testing

November 2026 release

Running on our own client sites now. Release notes follow in early December, once it has proven itself.

Released

October 2026 release

From a safe-update tool to a full agency platform. Versions 2.22 to 2.101.

Safe updates

  • Real visitor actions checked. Forms, carts and key routes are tested on the private copy with every update, and optionally every day. A page that broke once is always tested again.
  • One approval for every site. The same update on many sites shows up once in your inbox; each site still goes through its own safe route.
  • Big updates handled for you. Rollouts continue by themselves once the same update has proven itself elsewhere, and a behaviour check runs on the test copy.
  • Smart update rules such as “vulnerability fixes only”, “wait after a new release” and “test only”.

Backups

  • Your own storage. A daily or weekly copy of every backup in your S3-compatible bucket, plus downloads and up to three backups per site kept for a year.
  • Hourly database backups for shops, and backups that retry when something interrupts them.

Security and health

  • Protection until the fix is safe. When a vulnerability has no safe update yet, Verploy blocks the exploit path temporarily and removes the rule once the real update has gone live.
  • Uptime every minute, one-click hardening, file integrity and known-malware alerts.
  • Theme risk and PHP in view: vulnerabilities in the theme a site actually uses, themes that look abandoned, the PHP version of every site and what blocks an upgrade.
  • Server load and bots. See what loads each server, where the bandwidth goes, and turn away costly bots before WooCommerce or your page builder start working.

Clients and team

  • Free plan for up to three sites, no credit card, no time limit.
  • Client portal, proof in every client report (before-and-after screenshots and the checks that passed) and shop data in reports.
  • Activity log and site timeline: who did what and when, across all sites.
  • 10 languages for the dashboard and reports, Verploy on your phone’s home screen, and far less email: only what is really urgent.
  • Connect Verploy to your own tools: an API key per website and an AI assistant that answers about your sites with evidence.
  • Plugins on many sites at once, users per site, clone and migrate, database clean-up and a custom price above 120 sites.
Released

September 2026 release · Launch

The first public version. Versions 2.8 to 2.21.

  • Safe updates, rebuilt. Risky updates are tested on an isolated copy, exactly the tested version goes live, and orders and form entries survive a rollback.
  • Backups by Verploy. Nightly encrypted backups stored in the EU, a restore test that never touches the live site, and a free-space check before every restore.
  • Uptime and vulnerabilities matched to the exact versions installed.
  • Premium plugins and themes updated through the site’s own licence or a ZIP.
  • Connection check after pairing, with a proposed fix and who can apply it.
  • Update queue and a quieter inbox.

What comes next is on the roadmap. No release date is promised.

Full version log: every build, newest first

Fixes and small improvements ship as soon as they are ready; features are announced in the monthly release above once they have proven themselves. This log lists every build for those who want the detail.

  • 2.106.0: light mode

    Light mode. Choose System, Light or Dark at the bottom of the menu (on a phone under More). Verploy remembers your choice on that device for a year; dark stays the default. Reports and emails are unchanged.

  • 2.102.3 and 2.102.4: a clear note when updates wait for you

    When updates wait for you, Verploy says so (2.102.3). If automatic updates are off for your agency and updates are waiting, the Sites page now shows a bar at the top with how many updates on how many sites are waiting. A second bar shows known vulnerabilities that have a fix ready and are waiting for your permission. Admins get a link straight to Settings. A recurring problem card no longer says that Verploy will try again in the next round when automatic updates are off. It now says Verploy tries again when you start an update.

    “Can Verploy fix this for you?” (2.102.4). When automatic updates are off, at least five updates are waiting and Verploy has not finished a run in seven days, the owners and admins of the agency get one email, at most once every 14 days, in the language of the agency. It shows what is waiting, explains why Verploy has not acted (it never touches a site without your permission) and how it would handle the updates. One button, “Yes, fix it for me”, turns on automatic updates and automatic security fixes for that agency after you sign in. You can turn both off again in Settings.

  • 2.102.2: closed notices stay closed

    Closed notices stay closed. A notice you have closed at the top of the dashboard no longer shows up for a moment when you open the app. The dashboard now waits until it knows which notices you closed before it shows any.

    PHP notice removed. The fixed notice about the October 2026 PHP vulnerability is no longer shown at the top of the dashboard.

  • 2.101.0: full IP addresses in the firewall report, if you choose

    Firewall: full IP addresses, if you want them. By default Verploy leaves out the last part of a blocked IP address (203.0.113.x), because an IP address is personal data. If your server administrator wants to block attackers on the server itself, you can now turn on “Show full IP addresses” under Settings. It applies to all your sites from the next blocked request. Turning it off shortens the stored addresses again straight away. Only the owner or an admin of the agency can change it.

    Connector 2.27.0. This setting needs Verploy Connector 2.27, which your sites get automatically. Until a site has it, its firewall report stays shortened.

  • 2.100.0: the timeline shows what was there from the start

    The starting point of a site. A site’s timeline now also shows what was already there at the first backup: files that belong to known malware, PHP files among the uploads and suspicious file names in the WordPress core folders.

    “WordPress itself” instead of “Unknown”. A core update that WordPress installs by itself and updated translations are now listed under “WordPress itself”. What stays under “Unknown” is what really needs attention.

  • 2.99.0: the site page in tabs

    A calmer site page. Opening a site now starts with an overview: what needs attention right now, four tiles (updates, last backup, security, uptime) and the latest events. Everything else is in tabs: Updates, Backups, Security, Performance, Client and Settings. A red or orange dot shows where to look, and old links to a section open the right tab.

  • 2.98.0: a timeline of every change on a site

    A timeline of every change. Under Backups on the site page there is now “View timeline”. Verploy compares the nightly backups and shows, night by night, what changed: files, settings, user accounts, content and orders, with who most likely made the change (an admin, visitors, a Verploy update, or unknown). Changes made outside the normal route, such as a new PHP file in the WordPress core folders or a hidden administrator, are listed at the top as serious. Verploy reads nothing on the live site for this.

  • 2.95.0 to 2.97.0: 3 months free, known malware alerts, fewer false failures

    3 months free, up to 40 sites. New and existing agencies on Free get 3 months free on up to 40 sites, with every feature and no credit card. A bar at the top of the app shows how many days are left, with a link to the plans. Afterwards you pick a plan or go back to Free (3 sites); nothing is deleted. The offer is given once per agency.

    Known malware raises a critical alert. When the nightly file check finds files that belong to known malware in WordPress’s own folders (such as the WP-VCD family in wp-includes), Verploy now raises a critical alert and sends an email straight away, with the file names and what to do next.

    Fewer false failures when several updates run at once. When a site’s server throttles requests (HTTP 429), Verploy waits and measures again instead of judging the update, and a lost site lock is requested again instead of failing the run.

  • 2.94.0: services at a glance, pinned sites

    Services at a glance. The Overview now shows one line per service: uptime, backups, security, speed and forms. Each line shows how many sites are fine and how many need attention, and every number opens the list behind it.

    Pin your key sites. In Sites, use the star to keep your most important sites at the top. The pins apply to your whole agency. With several clients, you can also filter the list by client.

  • 2.93.0: a calmer overview, with every update and one button

    Four boxes at the top. The Overview now opens with four boxes: what visitors notice right now, what is waiting for you, which updates are ready and whether last night’s backups succeeded.

    All updates, one button. A new block lists every waiting update, with one button to update them all safely: first on a test copy, then live in stages. You confirm before anything starts. Major version jumps are left out, so you review those yourself.

    Less noise in the activity feed. A site that keeps switching between down and reachable now shows as one line in the activity feed. The count of compared pages is fixed as well.

  • 2.91.0: a behaviour check on the test copy

    A behaviour check before go-live. A compromised update can leave every page working. On the test copy, Verploy now also looks at what an update does: new administrators or extra permissions, a new must-use plugin, a plugin folder that doesn’t belong to the update, PHP files in uploads, options with known backdoor names, new scheduled tasks and connections to new servers. You see the result in the update’s timeline. For now this is a notice only; it does not hold an update back.

    Connector 2.26. The behaviour check needs Connector 2.26. Verploy updates the connector by itself. The image check is also stricter, so ordinary images are no longer reported as PHP in uploads.

  • 2.90.1: protection until the fix is safe

    Protection until the fix is safe. Verploy can now block the exact request used to exploit a known vulnerability until a safe update is live. The first rule blocks UpdraftCentral remote commands (stolen UpdraftCentral keys, October 2026) on sites with UpdraftPlus; UpdraftPlus’s own backups keep running. Requires Connector 2.23 or later.

    A cleaner malware scan. The malware scan no longer reports Verploy’s own working folders or Wordfence’s firewall rules as findings.

  • 2.90.0: where the bandwidth goes, backups that retry

    Where the bandwidth goes. Under Bandwidth on the site page you now also see which file types cost the most, which crawlers, and which other websites load your images or videos directly (hotlinking), with what you can do about it. If a site goes over the limit of its hosting plan, the alert is critical.

    Backups retry when a server is busy. If a site’s server is busy, the nightly backup is retried later in the night. The backups page shows why a backup failed.

    Connector 2.25.0. The new bandwidth detail works on a site once it runs Verploy Connector 2.25.0, which sites receive through the normal rollout.

  • 2.89.0: bandwidth per site

    Bandwidth per site. On the site page, under Bandwidth, you see how much data the website sends per day, how much of it goes to bots and which files cost the most. Verploy reads the hosting’s access log for this, where the hosting makes that log readable; you do not need to connect anything. If one day suddenly costs more than three times the usual amount, or a site approaches the limit of its hosting plan, you get a warning.

    A calmer site list on mobile. The site list now shows four filters by default (All, Critical, Attention, OK); the other filters, including PHP versions, sit under “More filters”.

    Refresh now and PHP errors. “Refresh now” checks again whether a PHP error on the live site still occurs; if it no longer does, the notice closes (2.87.4).

    Connector 2.24.0. Bandwidth works on a site once it runs Verploy Connector 2.24.0, which sites receive through the normal rollout.

  • 2.86.0: plugins on many sites at once, users per site, shop data in reports

    Plugins and themes on many sites at once. Under Sites → Manage plugins you can install a plugin or theme from WordPress.org on a whole set of sites at once, or activate, deactivate or remove it. Choose the sites yourself or by label. Verploy works site by site, never at the same time as an update or backup, and shows per site how it went.

    Users per site. Every site page now has a Users block: see who has access, add someone (they choose their own password), change a role, send a password email or remove a user. The last administrator always stays.

    Shop data in the client report. If a site runs WooCommerce, the client report now also shows orders, revenue and best-selling products, compared with the period before.

    Connector 2.23.0. These functions work on a site once it runs Verploy Connector 2.23.0, which sites receive through the normal rollout.

  • 2.85.0: Verploy on your phone’s home screen

    Verploy on your phone. Add Verploy to the home screen of your phone and it opens like an app. Works on Android (Chrome) and on iPhone and iPad (Safari).

  • 2.84.0: forms, scheduled tasks and database load in view

    Form email failures. With connector 2.22, Verploy notices within minutes when a contact or booking form cannot send its email, as far as we can see, with the name of the form and the error message, never the content. Works with Contact Form 7, Gravity Forms, WPForms, Fluent Forms, Ninja Forms and Elementor Forms.

    Scheduled tasks and database health. You get a notice when WordPress scheduled tasks are hours behind, or when WordPress loads too many settings on every visit. Notices appear in the inbox, on the site page and in the morning email.

    More caches cleared. After an update, Verploy now also clears the cache of Varnish, Nginx Helper, Hummingbird, Cache Enabler, WP-Optimize, Kinsta and WP Engine.

  • 2.83.0: less email, only what is really urgent

    Fewer emails. Under Settings → Morning email you can set a maintenance window, for example your server’s nightly backup: if a website is briefly unreachable during that window, you get no email. A website that often drops out for a moment is only emailed about once it has been down for an hour; the short interruptions appear in your morning email.

  • 2.82.0: proof in every client report

    Proof in the client report. Under each update in the client report you now see what was tested on a copy first: how many pages, at which screen sizes and how many checks passed. For the latest updates the report shows the home page before and after the update. Your client sees in black and white what your maintenance delivers.

  • 2.81.0: every Monday, theme risks in the morning email

    Weekly theme risk summary. On Mondays the morning email lists every site with a theme risk: a vulnerability without a fix, a theme that looks abandoned, or a theme that cannot be repaired through an update. Most serious first, so you see at once which clients to talk to.

  • 2.80.0: an API key for one website, with an expiry date

    API key per site. Under Settings → API and AI connection you can now limit a key to one website and give it an expiry date (30, 90 or 365 days). Handy for a client or freelancer who may only look at their own website with an AI assistant. An expired key stops working by itself. Under “How to use the key” you find example questions for your AI assistant.

  • 2.79.0: ask your AI assistant about your sites, with evidence

    AI assistant, read-only. The Verploy AI connection (MCP) now answers four questions with evidence from your account: which sites need a PHP update, why an update was held back or rolled back (with the failed checks on the test copy: page, screen size, HTTP status, visual difference and JavaScript errors), how your updates turned out over a period, and how each site is protected. Connect your assistant with an API key under Settings → API and AI connection. It can only read; it cannot change anything on your sites.

  • 2.78.0: mail conflicts that make forms fail silently

    Mail conflict. If a website has two or more active plugins that both take over WordPress mail (such as WP Mail SMTP and SMTP2GO), contact and booking forms can fail to send without the website showing an error. Verploy now flags this in your inbox and by email, with the names of the plugins. Switch one off and send a test form; the alert closes by itself. This is the first step of form monitoring.

  • 2.77.0: the PHP version of every site, and which ones need action

    PHP version per site. The Sites list now shows which PHP version each website runs. Red means that version no longer gets security updates, or that the security fixes of 21 October 2026 are missing. Orange means support ends within six months. Above the list you see how many websites run each PHP version; click a version to show only those websites. The filter “PHP action needed” shows the websites where you need to ask the host to update.

    The PHP vulnerability of 21 October. The app explains what happened with the critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619) and what to do now: ask your hosts whether the 21 October update is in place, and plan the move for sites on PHP 8.1 or older. The judgement follows the reported version number; some hosts backport fixes without changing it. Read the full story.

  • 2.76.0: spot themes that look abandoned

    Themes that look abandoned. Under Theme risk, Verploy now also checks whether the theme a site uses is still maintained. For themes from WordPress.org, it looks at when the latest version appeared and whether the theme is still listed in the theme directory. For premium themes, it looks at how far “Tested up to” lags behind and whether updates still arrive. When a theme looks abandoned, the site shows “Theme: looks abandoned”, and the explanation names which signals were triggered. Your agency’s own custom themes are not counted. This is based on the signals Verploy can see, not on a statement from the theme’s vendor.

    Verploy Connector 2.21. The connector now sends the theme details this check needs, such as “Tested up to”. Verploy rolls it out to your sites by itself.

  • 2.75.0: theme risk, vulnerabilities in the theme your site actually uses

    Theme risk. A vulnerable plugin can be fixed with an update or switched off. A theme in use is not something you simply switch off. That is why Verploy now looks separately at the active theme and, for a child theme, its parent theme. The sites overview shows a label when that theme has a vulnerability without a fix, or when the fix does not arrive through a normal update. The Theme risk filter shows those sites together. If a custom theme happens to share its folder name with a known vulnerable theme, it says “check” instead of reporting a vulnerability.

  • 2.74.0: switch to Verploy and connect all your sites at once

    Connect all your sites in one go. Under Sites → Switch you can paste the addresses of your sites, or a CSV export from your current tool. Then you create an agency key and download a personal connector. Install it on all your sites at once with WP-CLI, or with the bulk plugin install of your current tool (we have not tested this with ManageWP, MainWP or WP Umbrella yet). After activation, each site connects itself to your agency, without a pairing code per site, and the same page shows which sites are connected.

    Safe by design. An agency key is valid for 7 days, only for the number of sites you choose and only for your agency. Verploy stores only a fingerprint of the key, the site removes the key after connecting, and you can revoke a key at any time. Your plan’s site limit still applies. Requires Verploy Connector 2.20, which Verploy rolls out by itself.

  • 2.70.0 to 2.73.0: choose which bots to block, and connect Verploy to your own tools

    Choose per site which bots are blocked. Each site page now has a “Bots on this site” block: which bots visited in the last 24 hours, how much server work they cost and how often they were turned away. Tick per bot whether it is blocked, for example to let an AI search bot in or keep an SEO tool out. Googlebot and Bing are always welcome. Available from Verploy Connector 2.18; Verploy updates the connector by itself.

    Advice per bot. The same block now shows our advice for each bot: allow, block or your choice, with the reason. The advice depends on what a bot does, not on how often it visits: search engines and the search bots of ChatGPT, Claude and Perplexity help clients get found; bots that only collect text for AI training or for someone else’s SEO index bring nothing back. If your choice differs, you see it right away, and “Apply advice” sets everything in one step.

    Firewall and malware scan, starting with Verploy Connector 2.19. One-click hardening gets a firewall that stops known attack patterns (such as SQL injection and probing for secret files), locks login for half an hour after 10 failed attempts and blocks IP addresses that keep attacking, while forms and shops keep working. The site page shows what it stopped in the last 24 hours, and you can block IP addresses yourself. Verploy also scans the PHP files of your sites every night for clear signs of malware, such as web shells and hidden code; it only reads and changes nothing. Both are included in Verploy Connector 2.20, which Verploy rolls out by itself.

    API keys, REST API and MCP. Under Settings you can now create API keys. With a key, an AI assistant such as Claude, ChatGPT or Cursor can answer questions like “which sites are offline?” or “which updates are still waiting?” through the Verploy MCP connection, and your own tools can fetch the same data through the REST API. A key gives read-only access to your sites, updates, alerts, backups and update runs, and you can revoke it at any time.

  • 2.67.0 to 2.69.0: one approval for every site, see what loads your server

    One approval for the same update on every site. When the same update needs your approval on several websites (for example a new major version of a page builder), it now appears as one item in your inbox. One click approves it for all of them; each website is first tested on a test copy and only then goes live.

    See which websites load your server. New in the menu: Load. For each website you see how heavy it is for its server (availability, response time, memory, PHP errors, size and known heavy plugins) and what Verploy itself does there: backups, database backups and updates, in minutes per day. An hourly chart shows when Verploy keeps your server busiest, and each website lists what you can do first to make it lighter.

    Bot filter. Starting with Verploy Connector 2.17, Verploy measures which bots cost how much PHP time on each site, without visitor data. The Load page shows it per site, with a button that turns those bots away before WooCommerce or your page builder start working. Googlebot, Bing and the search bots of AI chat tools stay welcome. Verploy updates the connector by itself. Common plugins such as WooCommerce and Elementor no longer count as heavy.

  • 2.64.0 and 2.65.0: a calmer inbox, quieter nights, honest numbers

    A calmer inbox. What needs the same step is now one item in your inbox. All components whose safe version only comes from the vendor (licence or ZIP) are grouped in one item, and so are all security updates that were held back on the test copy. If the same update was held back on several websites, you see one item with all of them. Nothing disappears: the site page and Security still show everything per website and per component.

    Quieter nights. An update that skips many versions always goes through the test copy first, security updates included. If an update already failed on a site, Verploy does not retry it there by itself. When a licence is missing or PHP is too old, the update waits in your inbox instead of failing again every night. If the storage for backups is briefly unreachable, Verploy tries again later that night.

    Honest numbers. The overview of what Verploy did for you now counts each update only once.

  • 2.59.0 to 2.63.0: pages that broke once are always tested again, far less email

    Pages that broke once are always tested again. If a page ever broke after an update, Verploy now remembers it. Every following update on that site tests that page too, even when it is not in your list of pages to test. The update report shows which pages came from this recovery memory.

    Security fixes on their own, if you want. Verploy can now fix known vulnerabilities by itself. You turn this on under Settings. If the same fix was rolled back or held back on a site, Verploy does not retry it automatically for 30 days; a newer version or a manual start still can.

    A calmer “Now running”. You see how many websites are actually being worked on right now, and how many are waiting in the queue.

    Far less email. Verploy only emails you right away when a website is really down: after 15 minutes, at most once every half hour, and several sites in one email. A rolled-back update (your live site is already fine again), a PHP error or a recovery is no longer a separate email: you find it in the app and in your morning email.

  • 2.56.1 to 2.58.0: big updates handled for you, rollouts that continue by themselves

    Big plugin and theme updates, handled for you. A major version jump of a plugin or theme now runs in its own pass, after the regular updates, with a stricter check: it only goes live when every page has been compared on desktop and mobile and every form that worked before still works afterwards. If that cannot be proven, the update is not installed and Verploy asks you first next time. WordPress major versions and updates marked as risky always ask you first.

    Paused rollouts continue by themselves. When an update rollout paused because a single site held it back before going live, and the update already went live safely on at least two other sites, the rollout now continues automatically for the remaining sites.

    A busy site is no longer a failed attempt. If another task is still running on a site, Verploy now waits for it (up to half an hour) instead of counting it as a failed try.

    Clearer counter. The Updates counter in the menu now counts components instead of individual vulnerabilities, so the number matches what you actually need to update.

  • 2.55.0: see what Verploy did for you, and what blocks a PHP upgrade

    See what Verploy did for you, and what blocks a PHP upgrade. The top of the Overview now shows what Verploy did itself in the last 24 hours: updates tested on a copy, pages compared, forms and carts tested, and what went live safely. For every update you can slide between the site before and after. And on sites with an old PHP version, the PHP upgrade check shows what is blocking the move and in which order to fix it.

  • 2.54.0: more than 120 sites? Request a custom price

    More than 120 sites? Request a custom price. Scale still covers up to 120 sites, but that is no longer the limit. At site 121, or under Billing through the new Enterprise card, you can request a custom price straight away. You get a proposal within one business day; until then everything keeps working on your current plan.

  • 2.53.0: activity log, who did what and when

    Activity log: who did what, and when. New in the menu: Activity. One timeline per day with updates, changes made outside Verploy, alerts, backups and WP Admin logins, with who did it. Filter by site, type and period (7, 30 or 90 days) and export to CSV.

  • 2.52.0: Verploy in 10 languages

    Verploy in 10 languages. Next to Dutch, English, German, French and Spanish, Verploy is now also available in Italian, Portuguese (Brazil), Polish, Danish and Swedish. Choose your language under Settings; reports for your clients can be in these languages too.

  • 2.51.0: important things in view right away

    Important things in view right away. The menu now shows counters for Sites (unreachable), Security (critical vulnerabilities), Updates (security updates) and Backups (failed). Updates opens with four tiles and shows everything at once: first what is waiting for you, then the security updates, then the rest. The Overview starts with what needs your attention.

  • 2.50.1: tidier emails from Verploy

    Tidier emails from Verploy. All emails from Verploy now carry the Verploy logo, a calm light layout and a fixed signature with how to reach us. Reports you send on behalf of your own agency keep your own branding.

  • 2.50.0: backups in your own storage

    Backups in your own storage. Connect your own S3-compatible storage (Amazon S3, Backblaze B2, Wasabi, Cloudflare R2) under Settings. Every day or every week, Verploy puts a copy of the latest backup of each site there, as one plain .tar.gz file with all files and the database. That way you always have a second copy that is entirely yours.

  • 2.49.0: paused updates in one place

    Paused updates in one place. When Verploy pauses an update because it was held back on a site, it now appears under Paused in the menu, with a counter. You see right away what went wrong and choose: continue with the other sites, or stop.

  • 2.45.1 to 2.48.11: fewer emails, calmer overviews, key visitor actions checked

    Fewer emails, only what matters. Only critical alerts are still emailed right away; everything else is in the morning email. If a site is briefly unreachable, Verploy only emails when it is still down 5 minutes later, and if several sites are down at once you get one email with the list. When many sites fail in the same minute, Verploy first checks its own connection, so a hiccup on our side no longer counts as downtime for your sites.

    Calmer overviews. Sites shows one next step per website, with problems at the top; the full table with filters is one click away. Updates separates what is waiting for you from what is running and what has already happened. You can mark a problem on the live site as resolved yourself.

    Check key visitor actions. Set up to three paths per site that visitors really use, such as a form or the shopping cart. Verploy walks through them with every update and can check them daily on a private copy, and alerts you if something breaks. Needs Verploy Connector 2.16.

    Updates that succeed on their own more often. If a server does not respond at night while Verploy prepares an update, Verploy tries once more during the day instead of giving up. Staged rollouts show their progress on the overview, and the morning email no longer lists an update as failed when a later attempt succeeded.

  • 2.45.0: uptime checks every minute, one-click hardening, hourly database backups for shops, invite another agency

    Uptime checks every minute. Verploy now checks every minute whether your sites can be reached. You get an alert only when a site fails for two minutes in a row, including a second check. The site page shows the response time and the uptime of the last 30 days.

    One-click hardening. Turn on common WordPress security settings per site with one click: file editing in WP Admin off, XML-RPC closed, usernames shielded, version number hidden and a vague login error. No files are changed, and Verploy checks from the outside that the settings work.

    Hourly database backups for shops. For WooCommerce sites, Verploy makes a database backup every hour next to the nightly backup, so today’s orders can be restored too. These are kept for 48 hours; restoring one puts back only the database.

    Test copy on demand. Make a private copy of a site with one click on the site page, to try something out without touching the live site. The copy sends no email, is not indexed by Google and is removed by itself after 23 hours.

    Invite another agency. Under Settings → Invite you find your own link. The agency you invite gets its first month free; you get a month of credit once they pay their first invoice.

    Needs Verploy Connector 2.16. One-click hardening, hourly database backups and the test copy on demand run on the site itself. Sites are moved to the new connector in stages.

  • 2.44.0 and 2.44.1: PHP errors on the live site, smart update rules, test only for big updates

    PHP errors on the live site. If a visitor or administrator runs into a fatal PHP error, the site page shows which error, how often, since when and whether it started after an update, and you get an alert. Needs Verploy Connector 2.15, which Verploy rolls out to sites by itself, in stages.

    Smart rules for automatic updates. Under Settings, choose whether Verploy automatically fixes only vulnerabilities, waits a few days after a new version is released, or only applies an update once it has gone live without problems on other sites.

    Test only, for big updates. A risky update, such as a major version jump, now has “Test only”: Verploy runs it on a test copy, with screenshots before and after, and puts nothing live. If it looks right, one click puts it live through the safe route. A link shows what changes in the new version.

    Spam links recognised as a sign of a hack. The nightly link check now recognises links to fake pharmacies, casinos and the like in a site’s content, and shows on which page they are. It also no longer counts shopping-cart and filter links, or pages that a firewall briefly slows down.

    Delete backups, see storage per site. You can now delete a backup yourself. The Backups page and each site show how much storage the backups take, and before you delete, roughly how much that frees up.

    Steadier nightly backups (2.44.1). When several sites share one server, Verploy now makes one backup at a time per server, and a backup that fails on a network error is retried up to six times over the following hours.

  • 2.43.0: backup downloads, keep backups for a year

    Backup downloads. Download any backup as a single file with all of the site’s files and its database. Choose “Download” next to a backup on the site page; the download link is valid for 24 hours.

    Keep backups for a year. Keep up to three backups per site for a full year, for example right before a big rebuild. Regular backups are still kept for 30 days.

    What’s new, in the app. After a new version you see a short overview of what changed, once. Planned maintenance or an outage is now announced at the top of the app.

  • 2.42.0: support in the app

    Support in the app. Ask for help from “Support” in the menu, or from “Need help?” on a site page. Add a screenshot if it helps; the status of the site (connection, health, open notices, last sync) and the page you were on are sent along automatically, so you do not have to explain it all. You get the answer in the app and by email, in your dashboard language.

  • 2.41.0: client portal, database clean-up, clone and migrate

    Client portal. Each client can get a private, read-only link to their own site status, in your agency’s branding, with a button to ask you a question. Only a fingerprint of the link is stored, so the link itself cannot be read back from our database.

    Database clean-up. Verploy scans a site’s database for leftovers such as old revisions and expired temporary data. You choose what goes. Verploy makes a backup first, cleans up in small steps, checks the site afterwards and restores the backup automatically if anything is off.

    Clone and migrate. Put the latest successful backup of one site onto another site you manage. Verploy replaces the old address everywhere and compares the pages of the old and new site, so you can see that the move worked.

    Needs Verploy Connector 2.14. Database clean-up needs connector 2.14 on the site, and clone and migrate needs it on the target site. Sites are moved to the new connector in stages.

    Updates made outside Verploy. If you update a plugin by hand in WordPress, Verploy now sees it: a related warning closes by itself and the update history shows the change as made outside Verploy. “Refresh now” no longer keeps spinning; it shows the result within about half a minute, or tells you the site is not responding.

  • 2.40.0: broken links and images, direct connector updates

    Broken links and images. Every night, Verploy checks up to 15 pages per site, starting from the homepage and the links on it, and up to 300 of the site’s own addresses and 100 external ones. The site page lists what no longer loads, on which page and since when, with the site’s own links and images first. The monthly client report includes the list (up to 15 lines). Anything that works again disappears by itself.

    Verploy Connector updates go live directly. An update of only the Verploy Connector does not change what visitors see, so it skips the test copy and goes live directly, with a backup beforehand, a check after going live and an automatic rollback if anything is off. If it fails, Verploy tries again after 24 hours, up to three times per version. Connector 2.13.0 can also keep itself up to date through WordPress’s own automatic updates; its signature is still checked.

    Fixes. Error messages in the update timeline now show the real text instead of “[object Object]”. The page of a held-back update could show an error since 2.39.0; it opens normally again. The app’s framework was updated for known security issues.

  • 2.39.0: visitor routes tested, combination warnings, fixes found for you

    Visitor routes tested. Verploy now tests the paths your visitors actually take — the pages they land on and click through — on the test copy, before and after an update, instead of only a fixed set of pages.

    Combination warnings. Before you click, you see when a version broke elsewhere together with the same theme or page builder, based on what Verploy has seen across sites.

    Fixes found for you. When an update fails on the test copy, Verploy tries the known fixes itself and offers the one that works, so you decide instead of debug.

    Also in 2.38.1 and 2.38.2: a faster dashboard. Pages refresh in the background only when they are visible and not already refreshing, and links no longer preload pages you have not opened.

    Needs Verploy Connector 2.12. The route tests run on the site through the connector; sites are moved to the new connector in stages, starting with our own.

  • 2.38.0: an email when your update is live, one-click approval, faster runs, shorter maintenance

    An email when your update is live. When you start an update yourself, you now get one email the moment it is live and checked, or when it was held back or rolled back. Webhooks receive the same event.

    Approve with one click. Alerts that ask for your decision now carry a signed link: one click approves, without digging through the dashboard first.

    Faster runs. Desktop and mobile are measured at the same time, and with short maintenance the live baseline runs while the test copy is being tested.

    Shorter maintenance, per component. Each plugin or theme gets its own short maintenance window while it is installed and its styles are rebuilt, instead of one long window for the whole run. Short maintenance now also applies to sites without a data guard when nothing transactional runs on them.

    Site problems found at night, before you click. The connection check now runs every night between 01:00 and 06:00 (Amsterdam) and also checks the PHP version and plugin licences, so a known problem shows on the site page before anyone starts an update.

    Fewer false visual differences. Feeds, review widgets, counters, tickers and external embeds are masked automatically, and sliders are checked by height, so moving content does not read as a broken page.

    Plugins bundled with your theme. With Verploy Connector 2.11, a plugin that ships inside your theme (via TGMPA or a ZIP in the theme folder) can be updated from the version your theme provides, so the “no download file” block no longer applies there. The connector is rolled out in stages, starting with our own sites.

  • 2.35.0 and 2.37.0: faster small plugin updates, known site problems are not retried

    Known site problems are not retried (2.37.0). When an update cannot be installed on a site for a reason the site has to fix first — a licence that is not active, no download file from the plugin’s maker, a PHP or WordPress version that is too old, not enough disk space for the test copy, a firewall that blocks Verploy — Verploy now says so once and does not start that update again, not at night and not when you click. The site page shows “Not available” with the one thing to do, and the inbox shows what it is waiting for and who can fix it. As soon as something changes — a new version from the maker, the licence activated, PHP updated by your hosting provider, a passed connection check — the update runs again by itself. If you want to try anyway, “Try anyway” is one click away.

    Faster small plugin updates (2.35.0). A small update of a plugin from WordPress.org — same major version, at least seven days out in the open or live elsewhere without trouble, and never failed on a Verploy site — now goes live without a test copy: snapshot first, then the update, then the same checks on the live site and automatic rollback if anything is wrong. Themes, page builders, WordPress core, premium plugins, shop and payment plugins and webshops always keep the test copy. The run page says which route was taken.

    A green test copy is enough (2.35.0). When an update passes every check on the test copy, it goes live, also at night. Softer signals that used to hold updates back on their own, such as a failure on another site or an earlier failed attempt, no longer do. A failed check still holds an update back.

  • 2.36.0: free plan for up to three sites

    Free plan for up to three sites. Agencies can start on a free plan that covers up to three sites, with no credit card and no time limit. Updates on the free plan go through exactly the same checks as on the paid plans. When you add a fourth site, Verploy shows the switch to Solo right away. Since 8 October 2026, the first 30 agencies can sign up without an invitation.

  • 2.34.0: “Not available” instead of “held back” for updates without a download file

    “Not available” instead of “held back”. A premium plugin or theme without a download file, because the licence is not active or the version is bundled with your theme, cannot be installed by anyone. Such a run now ends as “Not available”, shown in grey in History, Recent activity and the results, and it no longer counts as held back. The item tells you what is needed: a licence, or a ZIP you upload once.

    Held back still means held back. If a run contains at least one update that failed for another reason, it stays held back and your live site is not touched.

  • 2.33.0 and 2.33.1: styles rebuilt after a theme or page-builder update

    Styles rebuilt after a theme or page-builder update. Some themes and page builders only rebuild their CSS after you save their settings once more, so right after an update the pages can look different even though nothing is wrong. Verploy now does that step itself, on the test copy and on the live site, before it compares the pages: theme options are saved again unchanged, Elementor’s CSS is regenerated and page caches are cleared. That removes a common reason for a visual difference, so fewer updates need your one-click approval.

    Needs Verploy Connector 2.10. This step runs on the site itself, through the connector. Sites are moved to the new connector in stages, starting with our own; until a site has it, the update runs as before. The timeline of a run shows “Styles rebuilt” when the step ran.

    2.33.1: a shifted page is not a broken page. When an update only moves content on a page, for example a booking plugin that renders slightly lower, the visual comparison no longer reports it as a difference.

  • 2.31.0 and 2.32.0: approve a visual change with one click, shorter maintenance mode

    Approve a visual change with one click (2.31.0). When a theme or page-builder update changes only how pages look, and every other check passes, Verploy no longer simply holds it back. It shows the before-and-after screenshots side by side with one button, “Looks good, go live”, which puts that update live through the normal safe route: backup first, checked after.

    Maintenance mode only while installing (2.32.0). On sites with the data guard, which keeps orders and form entries made during an update, the backup is now taken before maintenance mode starts, and the full check after going live runs on the public site. Visitors see the maintenance notice only during the switch itself, not during the backup and the full check as well.

    Small fixes. Free disk space in the pre-check is shown in GB instead of MB, and a visual change you approved no longer counts as an earlier failure for that site.

  • 2.30.0: more updates go live automatically

    The nightly round runs again. Automatic updates now skip a version only when an earlier attempt showed that the update itself broke something on the test copy. A site problem, or an update that could not be downloaded, no longer stops the nightly round from trying the rest.

    Updates without a download file. A premium plugin or theme without an active licence, or one bundled with your theme, cannot be installed by anyone. Verploy now sets it aside for three days instead of holding it back, lets the other updates on that site go ahead, and shows the ZIP and licence route. Clicking “Update” again within a day shows that route right away instead of starting a new run.

    Shops with a cache. A webshop whose cache hides the maintenance page now goes live the normal way when the data guard is on, so orders and form entries made in the meantime are kept if a rollback is needed.

  • 2.29.0: findability in Google, Slack and webhook alerts, measure now

    Findability in Google. The daily Google PageSpeed check now also looks at the homepage’s search basics: title, description, indexing, canonical link, robots.txt, language links and link texts. The site page shows an SEO score and, in plain language, what fails. If the homepage asks Google not to show it — often an accidental setting after a migration — you get an alert, and it clears itself once fixed. The monthly client report includes the SEO score.

    Notifications to Slack or a webhook. Next to email, Verploy can send the same alerts, and the all-clear, to a Slack channel or your own system (up to three per agency), with a minimum severity per destination and a test button. Messages to your own system are signed, so you can check they come from Verploy.

    Measure now. The Speed block on the site page has a “Measure now” button: Google PageSpeed measures the homepage right away, on mobile and desktop, and the page updates itself when the new score is in (about a minute). Numbers follow your dashboard language.

  • 2.26.0: speed scores with Google PageSpeed

    Speed scores with Google PageSpeed. Verploy now measures every connected site’s homepage once a day with Google PageSpeed Insights, on mobile and desktop. The site page shows the score, the key loading metrics, a 90-day trend and the three fixes that save the most time, in plain language. You get an alert only when the mobile score drops clearly and stays down, not after one bad measurement. The monthly client report now includes the typical speed score for the period and the period before.

  • 2.25.0: fewer unnecessary hold-backs

    Fewer unnecessary hold-backs. Updates to an inactive plugin or an unused theme now go live without a maintenance page, because visitors never see them; the test copy, the backup beforehand and the check after going live stay in place. When a site’s cache blocks Verploy’s view during maintenance, the result now says clearly that the update passed on the test copy and that the site caused the hold-up.

    Mobile. On a phone, the bottom menu on the Sites, Backups and Reports pages is visible again without scrolling.

  • 2.23.0: overview since your last visit

    Overview: what Verploy did since your last visit. The overview now opens with four numbers for the period since you last looked (or the last seven days): updates deployed, updates held back before going live (your live site was not touched), updates rolled back automatically, and backups made. Each number opens the matching history. Below it: “Waiting for you” in a compact list, “Security and risk” with a count of open serious vulnerabilities, and “Recent activity”.

    Mobile. On a phone, the menu now sits at the bottom of the screen: Overview, Inbox, Sites and More (Updates, Security, Backups, Reports, Settings, Sign out). Settings tabs fit the screen.

    Confirming your email from another device. Opening the confirmation link in a different browser or device than the one you signed up with now tells you that your address is confirmed and asks you to sign in, instead of showing an error.

    Founding applications. Agencies can now apply for a founding spot on verploy.com/founding; we review every application personally and send an invitation when there is a fit.

  • 2.22.0: founding status in the app

    Founding status in the app. Founding agencies no longer see a trial countdown or plan buttons. Settings and the subscription page now show that the account is free through the founding phase, with no time limit, and that if you continue when we open up more widely, you keep 40% off, for life. The plans are shown for reference only, with your own plan marked and how many of its sites you use.

  • 2.21.0: connection check after pairing

    Connection check after pairing. Right after you pair a site, Verploy checks whether it can work on that hosting: reach the site, talk to the connector, receive data back from the site (outgoing traffic), update files, and find room for a test copy. The check only reads; it changes nothing on the site. Each blocker comes with one suggested fix and who can apply it (you or your host), and appears in your inbox. You can rerun the check at any time from the site page with “Check connection”.

    Pairing with a different address. If WordPress reports from another address than the one you entered (for example with or without www), the pairing screen shows it and lets you adjust the address with one click. If nothing comes in after three minutes, the screen shows what to check.

  • 2.20.0: free-space check before a restore

    Free-space check before a restore. Before a restore or a restore test starts, Verploy shows how much space the site needs on the hosting and compares it with the free space you entered for that site (under Backups; valid for seven days). If there is not enough room, or the site recently ran out of space, the restore is not started and you are asked to enter or free up space first. If writing fails during a restore (quota or disk full), Verploy stops and cleans up.

    Includes 2.19.1 (restore test wording).

  • 2.19.0: restore test

    Restore test. Check that a backup can be restored, without touching the live site. Verploy takes the latest backup, restores it next to the live site on the same hosting (files in a separate folder, database under a temporary prefix), counts whether every file and database row came back, and then removes the copy again. Nothing is swapped and nothing goes live. The result is shown next to the site’s backups: files, tables, size and duration, or what was missing. Updates for that site wait while a restore or restore test is running.

  • 2.18.0: update queue and a quieter inbox

    Update queue. If an update is already running on a site, new updates for that site no longer have to wait for you: they are queued and start automatically through the same safe route once the running update is finished. The queue is visible under “In progress” and on the site page, and an item can be taken out again.

    Quieter inbox. One cause is one item. Updates that fix a vulnerability are listed with that vulnerability instead of as a separate approval, and items that are no longer relevant (for example a connector update that has since been installed) are removed. Rolled back updates always stay listed.

  • 2.17.0: new overview

    New overview. After signing in you see all your websites in four groups: Needs action, Watch, All good and Still to connect. Each website appears once, in the most severe group, and each group opens the site list filtered to exactly those sites. Live incidents (a site that stopped responding, or an update whose rollback failed) are listed separately with the impact, since when, and the next step. “Waiting for you” lists up to five actions; “In progress” always shows what is running (updates, backups, restores). “Security” shows only serious vulnerabilities that have no step for you yet, so nothing appears twice. “Last 24 hours” lists completed updates and new or resolved notices.

    Inbox in four tabs: Action possible, Waiting for vendor, Review later and Resolved. Each item shows the severity, who resolves it, which websites, what it means for the live site, and the next step. “Review later” parks an item for seven days and can be undone.

    History page. All completed updates and backups, filterable by period (7, 30 or 90 days), started by (automatic or manual), outcome and website.

    Failed updates explained in five parts: what failed, what it means for the live site, the cause (or likely cause), what you can do, and whether Verploy retries. Technical details are collapsed and cleaned of HTML; e-mail addresses, keys and tokens are removed.

    Adding a website needs only the address; name, client name and report language can be filled in later. Adding the same domain again resumes the existing site instead of creating a second one. A new site only joins automatic updates after you confirm it.

    Site page: edit name, address (http/https, www) and labels; labels are searchable from the overview and the site list. “Refresh now” asks the connector for fresh data without changing anything. The test settings explain which pages are checked and what the checks do and do not cover.

    All of this is available in the five dashboard languages.

  • 2.16.0: invite-only signup

    Invite-only signup during the founding phase.

    What stays in place on a rollback. When Verploy rolls back an update that went live, orders, form submissions, comments and user accounts created after the backup stay on the site; everything else goes back to the version from before the update. The state from after the update is kept for seven days. A missing or incomplete backup is reported as an error instead of a success.

    Site frozen while going live. During the switch to the new version, visitors, the REST API, payment webhooks and scheduled tasks receive a temporary “try again later” response instead of hitting a half-updated site.

    Exactly the tested version goes live. If the live site offers a different version than the one tested, nothing is installed. If one component cannot be installed on the live site at all (nothing changed for it), the other tested components still go live and that component is reported as needing attention.

    Test copy isolation, checked on every run. Before testing starts, Verploy checks that the test copy sends no email, makes no outgoing requests, runs no scheduled tasks, is not indexable by search engines, and is reachable only by Verploy (visitors get a plain “Verploy staging” response). If one of these checks fails, the update is held back before anything is tested.

    Pre-check before the test copy: disk space and write permissions are checked first.

    Recurring problems per site. On the site page and in the inbox, a repeated failure (hosting limits, firewall, connector not reachable) is shown as one block: what is going on, who fixes it (Verploy, you or your host), what to do, and how often it already happened. After two failures in a row with the same non-update cause, Verploy pauses automatic updates on that site until it is resolved; a successful or manually started update lifts the pause.

    Includes 2.16.1: a routine update of the Verploy Connector was held back by mistake; connector-only updates are now assessed correctly.

  • 2.15.0: more reliable safe updates

    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).

  • 2.13.0: site status “waiting for a fix”

    Site status “waiting for a fix”. A site whose only open issues are vulnerabilities for which no fixed version exists yet counts as healthy, with a grey label (“2 vulnerabilities, no fix available yet”). As soon as an update that fixes the vulnerability appears, the site moves to “needs attention” by itself. New filter “Waiting for update”. A critical vulnerability without a fix stays “needs attention”, with the advice to consider disabling or replacing the plugin.

    Includes 2.13.1 (shorter action line for premium fixes).

  • 2.12.0: faster safe updates

    Faster safe updates. The baseline at the start of a run only checks that the live site works; the full baseline of the live site is taken right before going live, as before. Pages are measured three at a time, and three updates run in parallel instead of two.

    “In progress” on the overview now also shows running or queued backups and restores, with progress.

  • 2.11.0: premium plugins and themes

    Premium plugins and themes. Verploy shows why an update is missing: “licence not active” (update known, but no download available), “part of the theme”, or “no update channel”, with a button that signs you in to the licence setting in WP Admin.

    Upload a ZIP. Download the new version from the vendor and upload it in Verploy; Verploy reads the version inside and installs it through the normal safe update (test copy first, then live, rolled back if something breaks). The ZIP is removed afterwards. Available under Security, in the inbox and under Updates.

  • 2.10.0: backups menu

    Backups menu. Per site: the latest backup, its status (ok, outdated, failed, running, none yet), size and how many are kept, with “Back up now” and a link to restore. A “Backup” column in the site list.

    Healthy means nothing to do right now. Acknowledged notices no longer count. A failed last backup counts as “action needed”.

    Visual comparison against both baselines. A page that renders slightly differently on every load (for example a post list on mobile) no longer holds back a harmless update.

  • 2.9.0: backups by Verploy

    Backups by Verploy. Every night Verploy makes a backup of each site through the connector, on the hosting your clients already use, without needing access to the hosting account. The first backup is complete; after that only what changed, plus the database each time. Backups are encrypted on the site before they leave it (the key stays with Verploy), stored in the EU and kept for 30 days. “Back up now” on the site page.

    Restore per site. Only that website (files and its own database tables) is restored: first prepared next to the live site, then switched in one step, then checked. If the site does not work afterwards, Verploy automatically puts the previous state back. wp-config.php, the connector and the pairing with Verploy are left in place.

  • 2.8.0: uptime and vulnerabilities

    Uptime. A site only counts as offline when the website itself does not respond; a quiet WordPress cron is no longer treated as an outage. Earlier notices based on the heartbeat alone no longer count towards the uptime percentage.

    Vulnerabilities. The column counts vulnerable components (plugins and themes) instead of individual reports. Only critical and high vulnerabilities make a site “needs attention”; medium and low are informational.

  • The new verploy.com is live

    The new verploy.com is live. Choose your plan first, then create your account, so you always know which plan you’re starting with. We also added a Trust & data page, honest comparisons and this changelog.

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

Spend less time checking WordPress.

Let Verploy do the maintenance work.

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