Thanks so much for reaching out — great question!
At the moment, Breeze does not include direct integration with NGINX FastCGI cache. Breeze operates at the WordPress (application) level by generating and serving its own static HTML cache, so it does not directly communicate with NGINX’s fastcgi_cache module for cache purging or invalidation.
On Cloudways servers, server-level full-page caching is typically handled by Varnish, and Breeze automatically purges Varnish whenever content is updated. For most websites, the Breeze + Varnish combination provides the same practical benefit users generally expect from FastCGI caching.
In addition, Breeze also integrates well with:
- Cloudflare — automatic edge cache purge via API token
- Browser caching — via proper
Cache-Control and Expires headers
- Redis / Memcached — fully compatible when enabled on the hosting environment
If you have a specific use case in mind for FastCGI cache, or if it has been enabled separately on your server, please feel free to share more details about your setup and we’ll be happy to take a closer look.
For server-level cache configuration questions specific to Cloudways infrastructure, the Cloudways support team may also be able to provide additional guidance.
Hope this helps!
