CachePilot for agencies and hosting providers
The same cache on every client site, set up without a checklist. For hosts, Redis per customer from the panel.
What makes CachePilot easy to hand over
Four things that save time once more than a few sites run on it.
01
Rollout by command line
Every function the admin offers for daily work has a WP-CLI command, from status to modules.
02
A log instead of notes
The Autopilot log says what changed on a site and why, for you and for the client.
03
Reports to the right person
The weekly e-mail goes to the admin address of the site and only when there is something to say.
04
Redis per customer
CachePilot Server provisions Redis 7 in ISPConfig with limits per customer and reseller.
What to plan before a rollout
Every site needs PHP 8.3 or later with phpredis, WordPress 6.4 or later and a Redis server from version 6.0. Without phpredis CachePilot stays inactive.
Several sites can share one Redis database. CachePilot prefixes every key and limits flushes to its own prefix when it finds other keys.
Sites that use another page cache plugin keep it; CachePilot then runs the object cache only. In Multisite networks the page cache is switched on by hand.
Updates come from update.cms-admins.de. The plugin is GPL v2 or later; the beta is free for businesses, pricing follows after the beta.
Contact
Rolling out on many sites? Talk to us.
Tell us how many sites you run and on which hosting. We reply with what fits: the plugin beta, CachePilot Server or both.
- Send a request through the contact form for agencies and hosts
- Start with one site in the CachePilot beta
- Check the figures on the benchmarks page