Updatronix

Open Tools → Updatronix. The first tab is the log: date, item, version change, outcome. Click any row to drill into a single entry. Logging is on by default after activation; if you've turned it off in the past, only events recorded while it was on will show up.

Yes. Filter the log how you like, then click the Export logs button. You get a clean report you can drop into an email to your team, a maintenance summary for a client, or a note to whoever you've called in to help.

In Settings, turn on Manage update notifications and put the address in the recipient field. A comma-separated list works if you want to send the emails to several inboxes. Pick which event types should trigger an email (core, plugin and theme, debug summary, technical alert) then save. WordPress keeps sending the same emails it always sends; they just go to the address you picked instead of the site admin.

Yes. In Settings, turn on Disable all update notification emails. That suppresses the core, plugin, theme, and debug summary emails WordPress would normally send. Recovery mode emails, the ones that arrive after a fatal error so you can log back in, are deliberately exempt. Disabling those would lock you out of your own site, which is the opposite of helpful.

Yes. In Schedule, enable Delay Updates and set the number of days WordPress should wait after a release appears. The countdown is per release, not per check, so a 7-day hold means an offer is at least 7 days old before it installs. While anything is on hold, the Updates, Plugins, and Themes screens display a notice explaining what's happening.

It hooks into the same update pipeline WordPress already runs, so anything that updates through Dashboard → Updates or the automatic update system gets logged, whether the package comes from WordPress.org, a private source, or your host's mirror. If your host or wp-config.php locks a setting from outside the dashboard, Updatronix surfaces a notice explaining what's locked, so you don't waste time wondering why a toggle isn't responding.

No. Rolling updates back is a different problem with different tradeoffs and Updatronix deliberately stays out of it. What it does instead: when an update fails, the plugin captures the WordPress error and the version snapshot before WordPress moves on. That's the data you need to recover by hand, or hand to your host's support so they can.

Nowhere. Logs and settings live on your site. The plugin makes zero outbound network calls of its own: every API it touches is one WordPress was already going to call without it.

Up to you. In Settings, set the retention window between 1 and 365 days. A daily cleanup task drops anything older. The default is 90 days, which works for most sites; raise it if you need a longer audit trail, or lower it if your hosting is tight on storage.

Yes. Network-activate Updatronix for the whole network and manage everything as a Super Admin from the Network Admin dashboard. Settings, schedule, email controls, and update history are shared across every site in one unified log. Single-site installs work the same as before.

You can buy the pro version if it fit your needs. Also, I am accepting sponsorships via the GitHub Sponsors program. If you work at an agency that develops with WordPress, ask your company to provide sponsorship in order to invest in its supply chain. The tools that I maintain probably save your company time and money, and GitHub sponsorship can now be done at the organisation level. In addition, if you like the plugin then I'd love for you to leave a review. Tell all your friends about it too!

I welcome your ideas! If you have a suggestion for the roadmap, please visit the official support forum. If you are a developer, you can also contribute directly to the project on GitHub.