# Architecture

The controller manages config and analytics, nodes carry site traffic: get these two roles straight and everything else follows.

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


## 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](https://www.gocdn888.com/en/guide/quickstart).
:::