SleekView for Cyberduck Backup
Cyberduck Backup ships archives over SFTP, S3, and WebDAV using the Cyberduck transport stack. SleekView reads its push records and renders them as one sortable grid where protocol, destination, and outcome are first-class columns.
♾️ Lifetime License available
Protocol-aware pushes need a protocol-aware grid
Cyberduck Backup writes per-push records to wp_options and stores transfer logs alongside the archives it generates. Each push carries protocol metadata (SFTP, S3, WebDAV) because the plugin uses Cyberduck's transport library to talk to each endpoint. The plugin's dashboard lists pushes by date, but it treats SFTP, S3, and WebDAV pushes identically on the surface even though they fail in protocol-specific ways.
SleekView reads the same per-push records Cyberduck Backup already writes and renders them as a real WP Admin grid with protocol exposed as its own column. Filters by protocol, destination, or outcome make a WebDAV endpoint that quietly returned a 207 multistatus look different from a healthy SFTP push, which is the whole reason the protocol column matters. The same dataset, with filters, sorts, and saved views layered on top so the relevant rows surface in one click.
The protocol column is also where audit trails live for compliance reviews. Some industries require backups to be shipped over WebDAV to a specific archive endpoint and over SFTP to a separate disaster recovery host. A grid that filters by protocol turns that compliance question into a one-click saved view instead of a manual log read.
Workflow
From Cyberduck pushes to a protocol-aware grid
Read push records
wp_options entries Cyberduck Backup writes for each push, plus the protocol-specific transfer logs the plugin stores alongside the archive.
Surface the protocol
Save the compliance views
Drill into transfer logs
Sample columns
Cyberduck push runs
wp_options entries Cyberduck Backup writes for each push plus per-run transfer logs
| Array | Array | Array | Array | Array | Array |
|---|---|---|---|---|---|
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
| Array | Array | Array | Array | Array | Array |
Comparison
Cyberduck Backup admin vs SleekView
Cyberduck Backup
- Dashboard does not filter by protocol
- WebDAV and SFTP pushes look identical at a glance
- Compliance audits require manual log reads
- Transfer failures hide inside protocol-specific logs
- No saved view for per-protocol rotation health
SleekView
- Protocol exposed as a filterable column
- Per-protocol saved views for compliance review
- Saved view for failed pushes in the last 7 days
- Sort by duration to catch endpoint throttling
- Click through to the protocol-specific transfer log
Features
What SleekView gives you for Cyberduck Backup
Protocol-aware grid
SFTP, S3, and WebDAV pushes get their own filter values. A protocol-specific failure stops hiding inside a generic chronological list.
Compliance audits
Saved views per protocol turn a quarterly compliance audit into a glance. Filter to protocol equals WebDAV, scope to the audit period, export.
Failure inbox
Failed and Slow pushes stack at the top of a saved view until someone triages them. The 0 MB secondary SFTP push stops being silent.
Audience
For compliance, ops, and reliability
Compliance reviews
Industries that require dual-protocol backup rotation get a saved view per protocol. WebDAV to the compliance endpoint, SFTP to disaster recovery, no manual logs.
Agencies
Bring multi-protocol backup health into the same WP Admin you already use for client sites. One grid per site, no second tool, no extra license.
On-call engineers
When an endpoint is suspect, filter the grid to that protocol and destination and sort by Started descending. The rotation gap or silent failure jumps out.
The bigger picture
Why protocol matters when SFTP and WebDAV share a dashboard
Cyberduck Backup's distinguishing feature is that it uses the Cyberduck transport library to handle SFTP, S3, and WebDAV with first-class protocol support, not just thin wrappers. That strength is also what makes its history hard to read as a single chronological stack. A WebDAV push to a compliance endpoint fails in ways an SFTP push to a disaster recovery host does not, and yet they sit next to each other on the dashboard with identical formatting.
Compliance reviews ask which WebDAV pushes succeeded in the last quarter; reliability reviews ask which SFTP pushes were slow this week. Both questions answer cleanly when protocol is a filter column and a saved view, and both questions answer painfully when the dashboard is a flat chronological list. SleekView exposes the protocol Cyberduck Backup already records, turns it into a filter, and lets the two reviews live as separate saved views on the same dataset.
Questions
Common questions about SleekView for Cyberduck Backup
No. Cyberduck Backup owns the schedule, the transport, and the protocol-specific handshake for each destination. SleekView reads the records the plugin writes and surfaces them. The backup plugin stays canonical; the observability layer is read-only.
From the wp_options entries Cyberduck Backup writes after each push, plus the per-run transfer logs the plugin stores alongside the archive. No reindex, no second store.
It surfaces them. The protocol column distinguishes SFTP, S3, and WebDAV pushes, and the outcome column carries the plugin's interpretation of the protocol response. Deep protocol diagnostics still live in the transfer log itself, which is one click from the row.
We recommend pruning through Cyberduck Backup itself so its log files and metadata stay aligned. SleekView can hide rows visually, but deleting records should go through the plugin so transfer logs do not orphan their metadata.
Yes. Each subsite has its own Cyberduck Backup records and its own SleekView. Cross-subsite reporting works the same way it does in the plugin itself: switch subsite, or roll up CSV exports per network admin.
None. SleekView paginates and queries on demand, and the per-push wp_options entries stay small even on sites with two years of multi-protocol history. Queries finish in well under a second on typical hosting.
Indirectly. Cyberduck Backup does not write a row for a missed schedule, but the gap shows up clearly in a grid sorted by Started descending. A saved view per protocol and destination makes a missing night obvious.
No. SleekView reads protocol names, destination labels, and push metadata, but never the credentials Cyberduck Backup uses to authenticate against endpoints. Credential management stays in the plugin's destination settings, where it belongs.
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 checkoutBrowse more
- Woocommerce Octanepay
- Woocommerce Rewards Points
- Woocommerce Bring Shipping
- Wpc Frequently Bought Together
- Woocommerce Quick View
- Shopify Importer
- Product Csv Import Export
- Woocommerce Shipping Royal Mail
- Woocommerce Advanced Product Labels
- Charitable
- Givewp
- Woocommerce Laybuy
- Woocommerce Amazon Feed
- Yith Woocommerce Sales Countdown
- Checkout Field Editor