The product came out of a specific frustration: WordPress caching makes sites fast, but keeping cached content fresh after changes is unreliable, inconsistent, and usually handled by flushing everything. That works — until the site is large enough that flushing everything has a cost.

The project that made it unavoidable was taking over tierpark-bern.ch — the official zoo website in Bern, Switzerland. Over 1200 URLs, 16 custom post types, 15 forms across the site, three languages. Writing one-off invalidation snippets wasn’t going to scale. So the problem got solved properly.

WP Cache Autopilot is the result: two plugins with clearly separated responsibilities, built to manage the full cache lifecycle automatically — deciding what actually changed, purging only the affected pages, and warming them again before visitors arrive.

It’s maintained by one person, which means priorities come from production site needs rather than a feature roadmap. New capabilities ship when they solve a genuine problem. Stability comes first.

If you want to know more about the work behind it — or about Beat — you’ll find that at ekesto.com.