Every update is risk-scored, backed by a restore point, validated on staging, tested visually and functionally, then promoted or rolled back automatically. You decide the policy once and stop losing evenings to a plugin release you did not choose.
Included on every plan. No add-on pricing.
A WordPress site is not one piece of software. It is a WordPress core release, a theme, and typically twenty to thirty plugins, each maintained by a different team on a different schedule with different testing standards. Nobody tests that exact combination except you, in production, at the moment you press update.
Most breakage comes from a small number of predictable causes: a major version bump that changes an API other plugins depend on, a page builder update that shifts CSS, a PHP version requirement that your host has not met, or two plugins that both want to control the same hook. None of these announce themselves in the update notification. All of them are detectable before the update reaches a live site.
A patch release from 4.2.1 to 4.2.2 is a different proposition from 4.x to 5.0. WPCentrify reads the semantic version jump, the changelog, and whether the release is flagged as a security fix, then weights the risk accordingly. Security patches on low-risk plugins can be fast-tracked; major versions never are.
The update is checked against published vulnerability databases in both directions: whether the current version is vulnerable, which raises urgency, and whether the new version has any reported issues of its own, which raises caution.
If the same plugin version has caused health check failures or visual regressions on other portfolios, that signal raises the risk score before the update reaches you. The more sites running WPCentrify, the earlier a bad release is caught.
The same plugin update carries different risk on a brochure site and a WooCommerce store taking four hundred orders a day. You tag sites by criticality and business hours, and the policy engine treats them differently.
HTTP status on key URLs, PHP fatal error detection, database integrity, admin reachability, and REST API response. Anything that returns a 500 stops the rollout immediately.
Screenshots of your key templates before and after, compared pixel by pixel. You set the tolerance: 2 percent movement on a blog page might be fine, while any movement on a checkout template is not.
Contact form submission, add to cart, checkout page load, login flow and search. The things that earn money get tested explicitly rather than inferred from a page returning 200.
If any check fails, the restore point taken moments before the update is applied, the plugin version is pinned so it cannot be retried by accident, and you get an alert explaining exactly which check failed and why.
What people ask before they turn this on.
The rollback runs without you. The restore point taken immediately before the update is applied, the failing version is pinned, and an alert is sent through whichever channel you configured. Median rollback time is 41 seconds. In the morning you get a change record explaining which check failed, with the before and after screenshots attached.
Yes. Every automation is a default you can override. You can push a single update immediately, bypass staging, or run the full verification sequence on demand from any site's detail view.
Yes. WPCentrify can authenticate against a test account to capture screenshots of dashboards, account pages and checkout steps that are not visible to anonymous visitors.
Core automatic updates apply the change and hope. There is no pre-update backup, no verification afterwards, and no rollback. WPCentrify wraps the same action in the checks a careful person would run manually, then does the manual part for you.
The risk score falls back to version distance, install base across the network, historical failure rate for that developer, and the criticality of the site. A missing changelog raises risk rather than lowering it.
Connect a site in under two minutes and see this working against something real. Free during early access.
Free during early access. Keep your data, export any time.