Architecture

About 4 min

gocdn has two kinds of roles, both installed on your own servers.

Visitor
Visitor
Node80 / 443
Node80 / 443
Origin
ControllerPanel · Config · Analytics
ControllerManagement plane, no site traffic
Nodes open to visitors80 / 443
Controller open to nodes7443 · 7444 · 7445
Visitor requests only go through nodes; the controller pushes config and collects logs, and carries no site traffic

Controller

The controller is the management plane: the panel, site and certificate configuration, analytics, alerts, users and licensing all live here. The controller only manages config and analytics; it carries no site traffic.

Node

A node is the data plane: visitor requests arrive at a node, which handles caching, HTTPS, CC protection and the WAF, and goes to your origin only on a cache miss. Nodes pull their configuration from the controller; add and inspect them under Node Management in the panel.

How traffic flows

A site's domain points to the nodes through a CNAME, so visitors reach a node first. On a cache hit the node answers directly; on a miss it fetches the content from your origin. Access logs and site content stay on your own machines.

Ports

The controller opens 7443 (node communication), 7444 (upgrade package delivery) and 7445 (log ingest) only to approved node IPs; nodes open 80 / 443 to visitors.

Tip For the complete walkthrough from scratch, see the 10-minute quick start.
Get started

Try the live demo

Open the live demo, or contact us for a quote and the install command