Purge-only API tokens
An API token can now be created as purge-only: it is limited to one zone and can only purge that zone's cache and list its purges. Any other route, MCP included, answers 403 token_scope. It is the token to give a CI job that purges after each deploy.
See the Cache documentation.
Edge cache and purge in about a second
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.
103 Early Hints
Sites can now send 103 Early Hints: the edge learns the resources a page needs and hints them to the browser while the origin is still building the response. Early Hints are off by default and are switched on per domain or per name, from the dashboard, the CLI, the API or MCP (early_hints.enabled).
See the Cache documentation.