Breeze is the cache plugin Cloudways ships with every WordPress install. The page cache writes static HTML under wp-content/cache/breeze/ with one folder per host and one file per URL. Minified CSS and JS bundles land in wp-content/cache/breeze-minification/ with a hashed filename per bundle. The Varnish integration sits in front of the page cache on Cloudways infrastructure and the plugin tracks the Varnish state in wp_options under the breeze_varnish_settings key. The default Basic Settings screen exposes a Purge All toggle, which works on a Cloudways install and hides every interesting detail the moment a single URL stays stale.

SleekView Kanban reads the same Breeze folders and option rows the Basic Settings screen aggregates. A derived breeze_state field buckets URLs by page cache file presence, Varnish hit status, minify bundle status, and TTL freshness and every URL becomes a card grouped under Uncached, Preloading, Cached, or Stale. Card fronts can show the URL path, the cache file size, the Varnish status flag, the minify bundle hash, and the last write timestamp so a developer can spot bottlenecks across the cache stack without leaving the board.

Dragging a card between columns calls the Breeze helper API. A move from Stale back to Uncached purges the cache file and issues a Varnish purge for the matching path. A move from Preloading back to Uncached cancels the in-flight task. Breeze's automatic purge on post save keeps running, so a manual board action never collides with the plugin's normal cache invalidation flow on disk or in Varnish.

Breeze ships preinstalled on every Cloudways WordPress site, which means a lot of teams operate Breeze without ever choosing it. The Basic Settings screen exposes a small set of toggles and a Purge All button, which works for the small Cloudways install it was designed for and goes opaque the moment the install grows. A purge button hides the fact that only a slice of URLs is stale.

A Varnish status hidden inside the Cloudways admin panel hides the fact that several URLs are missing the edge entirely. The team relearns these blind spots every time a launch goes badly on Cloudways infrastructure. A kanban board flips that around.

Every URL is a card. Every combined cache and Varnish state is a column. A glance at the board tells the team how many URLs are uncached, how many are mid-fetch, how many are warm at both layers, and how many are stale past their TTL.

Dragging a card writes the change back through the same helpers the cron task already trusts. The Purge All button still exists, and still works as a last resort. The board exists for the rest of the time, when the team needs to see the cache stack the way the cache stack already sees itself.