请求面、主控与数据面相互独立 Request, control and data planes stay separate
主控负责编排和配置下发，业务请求由边缘节点自己承载。节点与主控暂时断连时，仍按本地缓存的配置继续服务；运行日志单独汇入日志分析数据面。 The control plane handles orchestration and config push, while edge nodes carry the request traffic themselves. If a node loses its connection to the control plane for a while, it keeps serving from the config it has cached locally. Operational logs take a separate path into the log analytics data plane.
三类平面的职责与数据流What each of the three planes does, and where the data goes
图分三层：主控在最上，业务请求在中间，日志在最下。主控负责编排和配置下发，业务请求由中间那层的边缘节点自己承载；虚线框内是可选组件。The diagram has three rows: the control plane on top, request traffic in the middle, logs at the bottom. The control plane orchestrates and pushes config, while the request traffic itself is carried by the edge nodes in the middle row. Anything in a dashed box is optional.
主控、Agent、节点与日志系统如何协同How the control plane, agent, nodes and logs work together
这些组件分别负责编排、承载流量、断连时继续服务、下发配置和升级，以及把日志送到最终落点。这里仅说明高层架构，不代表具体的网络拓扑或传输配置。These components handle orchestration, carrying traffic, continuing to serve through a disconnection, pushing config and upgrades, and getting logs to where they finally land. This is a high-level view only, not a statement about specific network topology or transport configuration.
主控 API 与授权服务Master API & license server
主控 API 通过 REST 和 gRPC 编排全局配置；授权服务结合签名授权文件与在线心跳，校验授权版本以及节点数、Zone 数配额。The Master API orchestrates global config over REST and gRPC; the license server combines a signed license file with an online heartbeat to validate the edition and the node and Zone quotas.
边缘节点与 cdn-agentEdge nodes & cdn-agent
每台主机常驻一个 cdn-agent，通过双向 gRPC 心跳与主控同步状态。配置经 gRPC Watch 增量下发，节点会将最新配置持久化到本地。A cdn-agent runs on every host and syncs state with the control plane over a bidirectional gRPC heartbeat. Config is pushed incrementally over gRPC Watch, and nodes persist the latest config locally.
回源中继（可选）Origin relay (optional)
回源中继位于边缘节点与源站之间，可用于跨网络回源，也可作为备用回源链路，按实际需要部署。The origin relay sits between edge nodes and origins; it can be used for cross-network origin pulls or as a backup origin route, deployed as needed.
主控断连时继续服务Serving when the control plane is unreachable
主控暂时不可达时，边缘节点会继续使用最近一次持久化的有效配置处理请求，避免请求面因主控波动而中断。When the control plane is temporarily unreachable, edge nodes keep handling requests with the last persisted valid config, so control-plane fluctuations don't stall the request plane.
签名升级Signed upgrades
cdn-agent 下载升级包后，会校验 SHA-256 摘要与 Ed25519 签名，随后执行原子替换并重启，避免加载被篡改的二进制文件。After downloading an upgrade package, cdn-agent checks its SHA-256 digest and Ed25519 signature, then replaces the binary atomically and restarts, which avoids loading a tampered binary.
日志分析数据面Log-analytics data plane
边缘节点和回源中继产生的日志，经 Log Ingestor 完成 HMAC 鉴权和批量写入后，可汇入外置 ClickHouse，用于访问、回源和高可用分析。ClickHouse 为可选组件。Logs from edge nodes and origin relays pass through a Log Ingestor (HMAC auth, batch write) and can flow into an external ClickHouse for access, origin-pull and HA analytics. ClickHouse is an optional component.
按需要选择授权版本和档位Choose the edition and tier you need
按节点数和授权站点数（以根域名 Zone 计）透明计费。选哪一档看实际部署规模，选哪个版本看您需要哪些高级功能与服务。Transparent pricing, based on licensed node count and licensed sites counted per root-domain Zone. The tier follows your deployment size; the edition follows which advanced capabilities and services you need.