Bulk update WordPress plugins safely with auto-revert
Preview version changes, snapshot first, then update across the whole fleet. If a health check fails after the update, WPMgr reverts the site automatically.
Updating plugins one site at a time is slow, and a bad update can break a site silently
Running updates manually across a fleet means hours of repetitive clicks and no consistent safety net. A plugin update that breaks a site often goes unnoticed until a client calls. The right approach snapshots every site before updating, checks health after, and reverts automatically when something breaks, without you staying online to babysit the run.
Under the hood
The steps that make it work, and what each one does.
See what needs updating across the fleet
The updates dashboard shows every available update across all connected sites in one view: plugin, theme, or core, with the current version, the available version, and how many sites are affected.
Snapshot first, automatically
Before any update runs, WPMgr takes an automatic snapshot of the site. If the update fails or the health check reports an error, the site rolls back to this snapshot without any manual intervention.
Run bulk updates by group or tag
Select sites by tag, client, or individually, then kick off the update run. Live per-site progress streams to the dashboard with no refresh. Failed sites are flagged, auto-reverted, and reported.
Review the audit trail
Every update run, snapshot, and revert is recorded in the tamper-evident audit log. The log shows who initiated the run, which sites updated successfully, which auto-reverted, and why.
What's included
Every capability ships in the open-source release.
Bulk runs by group or tag
Select a subset of the fleet by tag, client record, or manually, then run updates in one go. Live status updates for each site stream to the dashboard.
Auto-snapshot before every update
A snapshot is taken before any change lands. If the post-update health check fails, the site reverts automatically, and the failure reason is surfaced in the dashboard.
Live per-site progress
Update state for each site streams in real time over a server-sent events connection. No manual refresh needed to see which sites are still running.
Tamper-evident audit log
Every update, revert, and snapshot is written to the hash-chained audit log. The log shows who triggered the run, what changed, and the outcome per site.
Pre-update version review
The dashboard shows the current version and the available version for every pending update before you apply it, so you can review changelogs and decide what to batch together.
Core, plugin, and theme updates
WPMgr handles WordPress core updates as well as plugin and theme updates, with the same snapshot-first, health-check-after safety model for each.
Questions answered
Common questions about this feature.
What happens if an update breaks a site?
WPMgr runs a health check after every update. If the check fails, the site is automatically reverted to the snapshot taken immediately before the update, and the failure reason is surfaced in the dashboard. No manual intervention is needed.
Can I update a single site or do I have to run the whole fleet?
Both. You can trigger an update for a single site from the site detail page, or run a bulk update across a selection, a tag group, or the whole fleet from the updates hub.
Is the snapshot taken before or after the update?
Before. WPMgr takes a snapshot of the current state before applying any update. The snapshot is preserved even after a successful update so you can roll back manually if you discover an issue later.
Does update history show across the whole fleet?
Yes. The tamper-evident audit log records every update run, auto-revert, and snapshot across all sites, with the operator who triggered the run, the timestamp, and the outcome per site.
Run your whole fleet from one dashboard.
Free and open source. No per-site fee. The full release is on GitHub.