Edge Cache and CDN Platform  ·  View 26 of 29  ·  6 · Operations

Roadmap

Prove the properties everything depends on, then ship the MVP, then the economics, then reach.

Editable source SVG draw.io All views
Proof · 8 weeks Key contract + explain 2 properties Tag purge at 2 PoPs acks measured Control plane off 7 days PoP keeps serving MVP · to month 6 Edge + shield tiers collapse · ranges Purge + reconcile moved up from Phase 2 Ring rollout + revert Anycast · drain · guard Phase 2 · months 6–12 Footprint floors · ceilings Origin failover slow ≠ down Cost per TB · per miss Partial objects · signed URLs Phase 3 · months 12–24 Keyless TLS top properties only Crypto-shred runbook Second CDN path only with purge parity Edge compute inside the key contract Roadmap — Correctness First, Economics Second, Reach Third Application we own Decision point Interface / broker Security / platform Hardware beyond the first 6 PoPs is ordered only after the traffic volume check in the proof phase. v 1.0 · owner Edge Architecture · date 2026-09

Decisions

  • The proof phase tests three things first: declared keys with explain against two real properties, tag purge with measured acknowledgements across two PoPs, and a PoP serving for seven days with the control plane switched off.
  • Reconciliation moves from Phase 2 to the MVP (view 17). Wildcard purge stays in Phase 2 because it needs the role and rate limit to exist first.
  • A second CDN path is Phase 3 and conditional. It happens only if purge semantics can be matched across both paths, because two caches with different definitions of purged are worse than one.

Exit criteria for the proof

  • Zero key-defect findings on two properties under a hostile review; purge p95 under 5 s across two continents; seven days of serving with no control plane and no expired certificate; a measured per-node Gbps ceiling; and a measured monthly volume.

Risks

  • If the proof measures traffic near 6 PB a month, the right next step may be to buy delivery and keep only the key contract and the purge semantics in-house. The roadmap treats that as a valid result, not a failure.