Skip to content

This is the multi-page printable view of this section. .

Return to the regular view of this page.

Scope and non-targets

What behavior the Cloud Exit Standard tests, and what it deliberately leaves outside the line of fire.

In scope

  • Transfer, retrieval, extraction, or deletion charges that shape exit economics.
  • Missing or incomplete bulk export paths.
  • Proprietary interfaces and semantics on the workload’s critical path.
  • Commitments, credits, and contracts that strand economic value.
  • Incident transparency, contractual remedies, and corrective accountability.

Outside scope

  • Whether cloud, colocation, managed service, or owned hardware is inherently better.
  • Provider size, nationality, ownership, or popularity.
  • Product features unrelated to portability.
  • A claim that every organization should self-host.

Compute vendors, CDNs, network carriers, colocation facilities, managed service providers, and cloud platforms can all be allies when they make portability real. The boundary follows conduct: selling resources is trade; pricing the fact that a customer cannot leave is rent extraction.