CachePilot is developed by Patrick Schlesinger at CMS ADMINS in Munich.
CMS ADMINS builds and runs WordPress sites. CachePilot started as a tool for those sites: the first commit dates from 9 February 2026, with version 1.0.2 and 19 modules. Today the plugin has 15 modules and less than half of its former code.
Patrick Schlesinger
Why the code got smaller
Fewer modules, more automatic work.
In November 2026 CachePilot was rebuilt. The code shrank from about 54,500 to 24,250 lines, and the module count went from 19 to 15.
Modules for Yoast SEO, Jetpack and Elementor were removed because their caches did not save any work. TLS moved into the core settings, the Autopilot module into the plugin itself. CSS and JS Minify came in as a new module.
Versions 1.1.0 to 1.4.1 followed on 4 November 2026: a page cache served before WordPress loads, rules for WooCommerce shops, the safety check and zero-config setup. The figures of that work are on the benchmarks page.
The history of CachePilot
From the first commit to the beta, in the dates of the repository.
First commit
CachePilot 1.0.2 with 19 modules, Autopilot and Expert mode, WP-CLI and TLS support.
CachePilot Server for ISPConfig
Versions 1.0.0 and 1.1.0 of the extension: Redis instances per customer, limits, status and connection details in the panel.
The rebuild
Versions 1.1.0 to 1.4.1: code from about 54,500 to 24,250 lines, 15 modules, page cache before WordPress, Minify.
Zero-config Autopilot
Version 1.4.1 finds Redis on its own, checks its work and reports weekly. The admin was redesigned and translated into German.
Contact
Talk to CMS ADMINS.
Questions about the beta, the server part or a rollout on many sites reach the people who build CachePilot.
- Join the CachePilot beta
- Ask about CachePilot Server through the contact form
- Visit cms-admins.de