Redis object cache for WordPress Multisite networks.
All sites of a network share one Redis connection. Each site gets its own modules, emptying the cache of one site leaves the others alone, and the network admin page lists every site with its own flush button.
Built for networks with subdirectories and subdomains
What changes when CachePilot runs in a Multisite network.
One connection, one drop-in
Settings and the Redis connection apply to the whole network. Setup runs once.
Modules per site
Each site gets the modules that fit its own plugins.
Flush per site
Emptying the cache of one site leaves the other sites alone. The network flush works too.
Network page with paging
Every site of the network with its own flush button, page by page.
One weekly e-mail
One report for the network, sent to the network admin address.
Page cache by hand
Autopilot does not switch on the page cache in a network. You decide per site.
The network and one site
The network admin page of CachePilot and the Overview of a single site.
Settings and the Redis connection apply to the whole network; only super admins can change them.
From the FAQ of CachePilot 1.4.2
Beta
Bring one cache to your whole network.
Join the beta and test CachePilot on a staging copy of your network first. The requirements list what it needs.