SleekView for WPVivid Pro
SleekView reads the WPVivid Pro job history the plugin already writes (and an optional wp_wpvivid_runs shim for indexed columns) and renders every Full, Incremental, Restore and Migration job as a sortable, filterable operations table inside WordPress.
♾️ Lifetime License available
Backup history is data, the table view is the audit surface
WPVivid Pro extends the WPVivid backup engine with incremental backups, multiple remote-storage destinations (S3, Google Drive, OneDrive, Dropbox, Wasabi, sFTP, local) and scheduled migrations. Every job leaves a record with action, destination, size, duration and outcome. The plugin's default history page shows the latest jobs in a paginated list, ordered by date and broken down loosely by job kind.
SleekView reads the same records and renders them as a real audit table. Action, destination, size, duration and outcome become first-class columns. Sorts work the way a site reliability engineer expects: largest size first, longest duration first, failed first. Filters compose, so "every Incremental in the last 14 days that landed on Wasabi" is one composed view, and "every Full backup that took longer than 20 minutes this quarter" is another. The optional shim into wp_wpvivid_runs turns sizes and durations into indexed columns so the table stays fast even on installs that have shipped tens of thousands of backups.
The plugin keeps doing the heavy lifting of capturing, compressing and shipping the data. The table view becomes the audit surface reliability teams, compliance owners and agency ops actually open during a review.
Workflow
How SleekView surfaces WPVivid Pro data
Point at the WPVivid Pro history
Normalise into a table (optional)
wp_wpvivid_runs with indexed columns for started_at, action, destination, size_mb, duration_seconds and outcome. Makes thousand-row history responsive.
Compose the columns
Save and gate the view
Sample columns
A typical WPVivid Pro audit view
wp_wpvivid_runs
| Started | Action | Destination | Size | Duration | Outcome |
|---|---|---|---|---|---|
| 2026-05-15 02:00 | Incremental | S3 | 184 MB | 00:01:48 | Success |
| 2026-05-14 02:00 | Full | S3 | 2.4 GB | 00:18:12 | Success |
| 2026-05-12 02:00 | Incremental | OneDrive | 162 MB | 00:02:11 | Retried |
| 2026-05-09 09:43 | Restore | S3 | 2.3 GB | 00:22:04 | Success |
| 2026-05-07 02:00 | Migration | Wasabi | 2.5 GB | 00:34:51 | Failed |
Comparison
Default WPVivid Pro admin vs SleekView
Default WPVivid Pro admin
- History page is paginated and ordered by date, not composable by outcome or destination
- Sorting by size or duration to find heavy or slow runs is not a built-in column
- Filtering by Action (Full vs Incremental vs Restore vs Migration) needs scrolling
- Failed runs sit beside successful runs with no triage-specific view
- Sharing a backup-health summary outside admin needs screenshots
SleekView
- Every captured run rendered as a sortable, filterable row
- Sort by Duration or Size to surface heavy or slow jobs
- Filter by Outcome to triage failures separately from healthy runs
- Saved views: backup health, failure queue, destination scoped
- Same dataset feeds the audit table and the chart dashboard
Features
What SleekView gives you for WPVivid Pro
Destination as a real column
S3, Drive, OneDrive, Dropbox, Wasabi, sFTP and local become first-class column values. The strategy of one primary plus one secondary destination is verifiable, not aspirational.
Failure queue without an export
Filter to Outcome != success and the table scopes to failed runs only. Recurring failures get a triage queue of their own instead of hiding inside the main history.
Heavy and slow jobs on the surface
Sort by Size or Duration descending to find the runs that need attention. WPVivid Pro already records the numbers; the table view turns them into a signal.
Audience
Who uses SleekView for WPVivid Pro
Site reliability
Pin a saved "last 14 days" view sorted by Started descending with Outcome highlighted. Backup health becomes a real surface, not a checkbox someone hopes is green.
Agency ops
Hand each client a read-only backup table scoped to their site and destinations. Renewals and reviews stop being a conversation about screenshots and start being a list.
Compliance owners
Export the rows behind a filter as evidence of the backup cadence required by SOC 2 or ISO 27001. The audit trail is the table plus the CSV behind it.
The bigger picture
Why backups need a real audit table
Backups quietly become decorative the moment nobody looks at them. WPVivid Pro does the actual work faithfully, but a paginated history page does not by itself tell anyone that yesterday's incremental landed on Wasabi, that the Migration last week was the one that failed or that the Full backup has gradually grown from 9 minutes to 22. A composable table turns the same records into a measurable surface.
Filters compose, sorts work, and a sceptical question from a reliability engineer or a compliance auditor gets a one-view answer instead of a CSV round trip.
Questions
Common questions about SleekView for WPVivid Pro
From the plugin's own job history in wp_options and optionally from a shim table such as wp_wpvivid_runs for indexed columns. SleekView does not change how WPVivid Pro records jobs; it just reads what the plugin already writes.
Yes. The destination column is a first-class filter, so the table can be scoped to S3, Drive, OneDrive, Dropbox, Wasabi, sFTP or local. Combine with a filter on Action to scope further to one action type per destination.
Yes. The Action column carries Full backup, Incremental, Restore and Migration. Filter to one Action and the table scopes to that workflow; sort by Started descending and the latest runs of that action surface first.
Yes. Filter to Outcome != success and the table narrows to failed runs only. Save that as "Failed backups" and the team has a permanent triage queue rather than scrolling past failures inside the main history.
Yes only if the plugin's option-based records are read directly on every load. The optional wp_wpvivid_runs shim adds proper indexes; SleekView paginates server-side, so installs with multi-year history stay responsive.
Yes. Views are saved with a name and a capability gate, then surfaced as a read-only URL inside WP Admin. A client with an editor account can open the agency-prepared backup audit without ever touching the WPVivid Pro settings.
Yes. Any filtered view exports to CSV with the columns the table shows. Compliance evidence and post-incident reviews get a real spreadsheet of runs instead of screenshots of the WPVivid Pro screen.
No. The plugin still owns capture, compression, shipping, alerting and configuration. SleekView adds a composable audit table on top of the records the plugin already writes.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout