Azure CDN purge after a static deploy is the classic “make the new bits show up now” move. On a multi-node self-hosted fleet the same need shows up as coordinated invalidation: who triggers purge, which paths, and how you avoid a stampede back to origin. We have been building an open-source CDN control plane (CDNCA, AGPL-3.0) around self-hosted nodes and a plugin marketplace; marketplace features roll out release by release. Did you purge by path prefix, or did full-distribution purge become the default under pressure?