The OpenWAF edge can now cache your sites. The cache is in beta and off by default; you switch it on per site, with templates for WordPress, Next.js and static sites, Cache-Status, stale-while-revalidate and stale-if-error. The WAF always runs first. A purge by URL, prefix, host or Cache-Tag, or of everything, reaches every edge node in about a second, from the dashboard, the API or the MCP tool purge_cache.
See the Cache documentation and the MCP tools.