WP Staging Pro creates production-grade clones of a WordPress site for staging, dev, and migration use cases. Every clone is registered in the wpstg_existing_clones option array in wp_options with fields covering name, creation timestamp, prefix, size_in_mb, tables, and the source site URL. Push and pull jobs write detailed logs into the plugin's wpstg-jobs log directory and into option-stored job summaries.

SleekView Charts reads the same option and the job summaries and exposes them as a data source. A Number KPI counts active clones. A Pie groups clones by purpose extracted from the name prefix (staging, dev, qa, demo), so admins see how the team is using the plugin. A Bar ranks clones by size_in_mb, surfacing the staging copies that dominate disk usage. An Area trends push events per week, showing how often the team is rolling staging changes back into production.

The result is the staging environment dashboard nobody has had before. Eight active clones spread across staging, qa, and dev are no longer just a list, they become a chart of size, age, and activity. Stale clones surface, oversized clones surface, and push cadence becomes visible to the team leading the release process.

WP Staging Pro is the dominant WordPress staging plugin for sites that need real environment cloning without leaving the WordPress UI. The plugin does an excellent job of cloning, pushing, and pulling, but once a staging environment exists the information goes back to being invisible. Ops never sees disk growth across clones.

Release engineering never sees push cadence as a chart. Agencies never report on staging usage to clients. The data exists the whole time in the wpstg_existing_clones option and the job logs, but no admin screen aggregates it.

SleekView Charts reads the same option and logs and turns them into cards. Active clones, purpose mix, size distribution, and push cadence all live on one screen. Stale clones surface before they cost disk space, oversized clones surface before they slow backups, and push frequency becomes a release-engineering metric instead of a feeling.

The plugin keeps cloning, the dashboard does the reporting.