See:

• A CDN for the AMP runtime section in the OpenJS Foundation application.

• The FAQ on the OpenJS Foundation announcement:

  Currently, the AMP runtime is hosted on the same infrastructure as the Google AMP Cache. Doesn’t this present serious issues?

  The end goal is to separate the AMP runtime from the Google AMP Cache. The Project is currently in the incubating stage and Project leaders are still determining the next steps. Ideally, hosting and deployment of the AMP runtime to the CDN would fall under the purview of the OpenJS Foundation, much like the foundation is handling other projects CDNs, such as the jQuery CDN.

  Untangling the runtime from the cache is a complex endeavor requiring significant investments of time and effort which would be planned and implemented in collaboration with the foundation and industry stakeholders during and after incubation.

  The OpenJS Foundation CPC is committed to having a long-term strategy in place to address this issue by the end of AMP’s incubation.

This should notably:

• be done in collaboration with the foundation and the CPC,
• describe the difference between the proprietary AMP caches, such as Google's or Bing's, and the hosting of the AMP runtime,
• include a projected timeframe for dis-entangling the two,
• specify the domain(s) on which the AMP runtime would be hosted,
• clarify that AMP caches would probably host their own copy of the runtime (and that cached AMP pages would be transformed accordingly as part of the pre-caching transform process),
• describe by whom the supporting infrastructure would be provided, how it would be maintained, and how it would be governed,
• describe the deployment process and related security considerations, and
• describe the privacy policy under which the runtime would be hosted.