BackupBuddy stores per-job metadata in wp_options rows under the itsec_ and backupbuddy_ prefixes, with archive metadata extended for cloud-destination jobs that ship to Stash, Stash Live, S3, Dropbox, or Google Drive. The plugin's Backups page lists archives by date, but the screen is built for restore, not for sliceable history. A Stash Live continuous push that uploaded zero bytes in three seconds looks identical to a healthy nightly Stash job, and there is no way to ask the page which destination has been slowest this month.

SleekView reads the same per-job metadata BackupBuddy already writes and renders it as a real WP Admin grid. Columns become the things you actually want to slice by during a cloud-backup audit: started, scope (Full, Database, Files), destination (Stash, Stash Live, S3, Dropbox, Google Drive), size, duration, outcome. The same dataset, with filters, sorts, and saved views layered on top so the relevant rows surface in one click.

The destination column is the unlock for sites that ship to multiple clouds. BackupBuddy supports a half-dozen destinations and rotates them per schedule for resilience. The default page lists archives chronologically; a grid filtered by destination shows a redesign-sprint timeline as one clean list per cloud. Saved views per destination make rotation health legible across weeks instead of guessable from a long scroll.

BackupBuddy was one of the first WordPress backup plugins to ship to multiple cloud destinations from one schedule, and that strength is also what makes its history hard to read. Five destinations rotating across nightly schedules produces a long chronological list where every destination's health is buried somewhere in it. The default Backups page treats the list as a restore picker, which it is, but it does not treat it as a dataset.

A Dropbox push that silently shipped zero bytes is hidden until someone filters to Failed and looks at last week. A Stash Live continuous stream that quietly stopped is hidden because Stash Live shares the screen with everything else. SleekView lifts that history into a grid where destination is a column.

Filter to one destination, sort by duration, save the view. Rotation health stops being implicit in a long scroll and becomes explicit in five saved views, one per cloud. The same plugin, the same dataset, finally queryable.