cdn.pizzaDocumentation

Private networks and Partner POPs

Partner POPs

The partner flow separates public caching from customer storage and mail.

#Overview

The partner flow separates public caching from customer storage and mail.

#From application to activation

The Partner POP form collects organization, location, and capacity data for review. After approval, a limited-use enrollment token associates the candidate node.

Certification, activation, drain, suspension, and retirement describe customer-visible availability. A public partner POP serves routing and cache; it does not automatically host customer file storage or mail.

#Prepare an application

  1. Describe location, network, and operational contact accurately.

  2. Submit and answer requests for information.

  3. Use the enrollment token only on the intended machine.

  4. Wait for certification and activation before announcing availability.

#State lifecycle

StateMeaning
submittedProposal submitted for review.
needs_infoAdditional information requested.
approvedProposal approved; enrollment can begin.
registeredNode registered but not yet certified.
certifyingCapacity and security checks are running.
certifiedChecks passed; final activation is pending.
activePOP admitted to the public pool.
suspendedPOP temporarily removed from public routing.
retiredPOP permanently retired from the public lifecycle.
Customer documentationReference generated from published interfaces