Duplicator Pro Cloud writes every build to wp_duplicator_packages with name, type (manual or scheduled), size, build duration, status, and the list of remote storage destinations the archive was pushed to. The default Packages screen lists rows as a flat WP_List_Table, sorts on a handful of columns, and exposes destinations only when you open a row. That works for a single-site recovery story and becomes painful once you maintain backups across many sites or destinations.

SleekView reads the same packages table and joins to wp_duplicator_storages for destination labels (S3, Google Drive, OneDrive, FTP, Dropbox). Status, destination set, build size, and build duration become first-class columns. Filter to failed builds in the last 24 hours, group by destination to validate every cloud target succeeded, or pin a saved view of weekly schedule packages.

Inline edits route through Duplicator Pro's own CRUD layer, so retrying a failed build, downloading the installer, or pushing to an additional destination from a row uses the same code paths the default UI uses. Bulk delete of expired packages becomes a one-step cleanup instead of a click-per-row chore.

Backups are the one feature on a WordPress site nobody thinks about until they need them, and then everything depends on them. Duplicator Pro Cloud already stores the right data: every build is a row in wp_duplicator_packages, every destination is a row in wp_duplicator_storages, and the join between them tells the full operational story. What the default UI is missing is a working surface.

A weekly audit of which destinations actually received the archive should be one filtered view, not a click-per-row inspection. A retention cleanup should be a bulk action on a filtered set, not a tedious page-by-page chore. A disaster-recovery check should show last-known-good per destination at a glance, not require switching screens.

A real grid puts the data Duplicator Pro already collects into the hands of the people who need to act on it during normal operations and especially during an incident. The cost of a missed backup is too high to leave the working surface to chance.