ManageWP Backup uses the ManageWP Worker plugin on every connected site to communicate with the ManageWP dashboard. The dashboard owns the archive store and the central views; the worker writes local event records into wp_options under its own prefix to confirm runs, restores, and checks. The WP Admin side of ManageWP is intentionally minimal, which is fine until ops engineers want to answer per-site reliability questions without context-switching to the dashboard.

SleekView reads the worker's wp_options event records and gives each event its own row in a real WP Admin grid: started, event type (Backup, Restore, Check, Performance, Uptime), duration when present, outcome. The grid does not duplicate the ManageWP dashboard; it gives the per-site WP Admin instance a first-class read view of the events ManageWP already writes locally. Filtering event equals Restore with outcome equals Failed over the last 90 days surfaces incident history per site without ever leaving WP Admin.

Archive data stays off-site at ManageWP. The grid never claims to host backups itself, never decrypts content, and never bypasses the worker plugin. It simply surfaces the local event store as a queryable grid so operations questions about a site can be answered inside that site.

ManageWP's design assumes the central dashboard is where ops engineers live, which is true for the agency owner but often false for the per-site engineer or release lead. The worker plugin writes enough local event metadata to answer most per-site questions inside WP Admin, but until now there has been no read layer to do so. Site-level reliability conversations get pushed to the central dashboard, which is good for cross-site rollups and clumsy for one-site investigations.

SleekView reads the local wp_options records the worker plugin writes and turns them into a grid that lives where the site work happens. The ManageWP dashboard stays canonical for archive content and for cross-site overviews; the grid adds the missing per-site WP Admin read layer. That changes the operational story for sites managed through ManageWP: routine reliability work stays in WordPress, while the dashboard stays for the things only the dashboard does well, which is the right division of responsibility for a hosted backup product.