Edge Cache and CDN Platform  ·  View 10 of 29  ·  3 · Structure

Integration Surface — Every Interface

Every system that calls the platform and every system it calls, with the protocol at each crossing.

Editable source SVG draw.io All views
Callers End users Property owners Release pipelines Edge platform Edge Cache and CDN Platform delivery · config · purge Dependencies Tenant origins Transit and IXPs ACME CA · SPIRE · Keycloak HTTPS · H3 Git · explain Purge API HTTPS · mTLS BGP certs · identity Integration Surface — Every Interface Person or role Application we own External / third party Security / platform synchronous batch two-way Only the origin is on the request path, and only on a shield miss. Probes, NetBox and the finance export are on view 01; all may be down while delivery continues. v 1.0 · owner Edge Architecture · date 2026-09

Decisions

  • Property owners integrate through Git, not a configuration API. A change is a reviewed commit, the diff is the audit record, and a revert is a revert.
  • Release pipelines call the purge API directly with a scoped service identity. Purge is the privilege most likely to be abused, so it is its own role (ADR-25).
  • Certificates come from a public ACME CA over DNS-01, so issuance never needs a PoP to be reachable from the CA.

Contracts

  • Every response carries a Cache-Status header in the RFC 9211 format, so an origin team can read the edge's behaviour without access to its logs.
  • Origins receive requests only from shield addresses, over mTLS, with a platform-issued client certificate they can check.

Omitted

  • External probes, NetBox and the finance export are on view 01. None is on the request path.
◀  One Request Through One Edge Node All views Four Data Classes, Designed Separately  ▶
Solution Architecture v1.0 · Edge Architecture · 2026-09 · 29 views · open source, fully on-premises10-integration-surface