Fastor CDN is a thin integration plugin: it does not maintain its own database tables, instead storing configuration entirely in wp_options under keys like fastor_cdn_settings, fastor_cdn_rewrites, and fastor_cdn_excluded. Recent purge activity sits in a rolling option, and CDN host details live next to the rewrite rules. The default admin shows the settings as a single form, but never lists rewrite rules with their match counts or exposes the purge log as a sortable table.

SleekView reads the Fastor CDN options and parses them into flat rows. One row per rewrite rule can show its source pattern, target CDN host, and the number of front-end matches produced by the rewrite filter. Exclusions become their own table with the same match data. Purge events surface in a separate view with timestamp, scope (URL, prefix, full zone), and which user triggered the purge through the WordPress admin.

SleekView is honest about the CDN itself: it does not call Fastor's edge API. Inline actions write through the plugin's option API and, where the plugin already exposes a purge action, invoke it through Fastor's own hook. The plugin keeps rewriting URLs and purging the zone exactly as before. Saved views like Rewrites with zero matches or Purges last 24h scope per role so a developer audits the CDN without access to API tokens or zone credentials.

Fastor CDN is a slim plugin by design. It does not store traffic or analytics inside WordPress; it just rewrites URLs and forwards purge requests to the upstream edge. That minimalism is good for performance but bad for auditing.

The default admin shows the settings as a single form, and the only signal that a rule is unused is the absence of a regression report. Most teams discover a stale rewrite when a theme refactor reveals an asset path that no longer exists, by which point editors have been shipping broken images for days. SleekView treats Fastor's options as the ledger they already are.

Every rewrite is a row, every exclusion is a pattern with a match count, and every purge is a logged event with a scope and outcome. Performance engineers can remove dead rules with confidence, agencies can hand clients a read-only inventory, and developers can replay failed purges without holding rights to the API token. The plugin keeps rewriting and purging on the edge; SleekView just lets the team read the configuration that drives it.