WP Time Capsule Pro stores its job history through plugin-managed records in wp_options and wp_postmeta-style logs, with the actual data shipped to a connected cloud (Dropbox, Google Drive, Amazon S3, Wasabi). The plugin's history page lists recent backups but mixes incremental backups, staging restores, and full restores in a single stream. Spotting a regression in incremental duration over a quarter, or filtering only the staging operations, is more work than it should be.

SleekView reads the same records and gives each job a row with the columns that matter operationally: started, action (Incremental, Restore, Staging, On-demand), destination, files changed, duration, outcome. The same data, with the addition of saved views, role scoping, and combinable filters. Filtering action equals Restore with outcome equals Failed in the last 30 days surfaces the runs that the default history page never highlights.

Writes route through Time Capsule's own hooks. Re-running an incremental, pruning history, or promoting a backup to a staging snapshot all use plugin actions, not direct table writes. The plugin's incremental engine, schedule, and cloud credentials remain canonical; SleekView is the read layer over the records the plugin already maintains.

WP Time Capsule's selling point is incremental backups: smaller, faster, more frequent than full archives. That same property is exactly what makes its history harder to read in a flat list. A nightly incremental that shipped 412 changed files matters; the next night's incremental that shipped 4000 changed files might be a real signal, but the default UI does not surface that difference.

Mixed into the same stream are staging restores and one-click restores, each with different operational meaning. Ops engineers want failed runs in the last 24 hours; release engineers want staging duration trends; owners want change-volume aggregates. None of those are saved-view shapes inside the plugin today.

SleekView reads the records Time Capsule already writes and turns them into the grid the plugin's data deserves, with role-scoped views, sortable trend columns, and inline actions that call the plugin's own hooks. The incremental engine stays canonical; only the read layer changes, which is the right way to add observability to a backup tool without competing with it.