I want to break down this question slightly. > Can a third-party other than Google deliver an AMP page? Yes. Examples: Bing runs their own AMP cache and also

I want to break down this question slightly. > Can a third-party other than Google deliver an AMP page? Yes. Examples: Bing runs their own AMP cache and also delivers AMP pages. LinkedIn and Twitter also link to AMP pages, but they don't currently run a cache. IIRC, Twitter links to the Google AMP cache and LinkedIn links directly to the AMP variant on the publisher origin. They could run an AMP Cache. Cloudflare ran one for some time, but shut theirs down recently. The AMP Project maintains a list of known AMP Caches here: https://github.com/ampproject/amphtml/blob/master/build-system/global-configs/caches.json https://github.com/ampproject/amphtml/blob/master/build-syst... And provides some guidelines for running one here: https://github.com/ampproject/amphtml/blob/master/spec/amp-cache-guidelines.md https://github.com/ampproject/amphtml/blob/master/spec/amp-c... It's non-trivial, but absolutely supported. > Can a third-party other than Google deliver a Signed-Exchange? Yes. Cloudflare generates them for their customers who opt-in via their "AMP Real URL" product. "Generates" in this context implies delivering them. To date, I'm unaware of any large scale implementation that is delivering Signed Exchanges for third-party origins other than the Google Cache though this may change. The tech stack absolutely supports this.