Contents
Getting started
10-minute quick startArchitecture
Install and upgrade
Install the controllerAdd nodesOnline upgradesUninstall and migrate
Sites
Add a siteSet up the CNAME recordHTTPS certificatesCache rulesPurge and prefetchOrigin settings
Security
Security overview and big screenAttack logCC protectionWAFLists and access controlBots and scannersPaid protection add-ons
Analytics and alerts
StatisticsAccess logsAlerts and notifications
Accounts and licensing
Users and plansLicenses and add-ons

Architecture

Updated 2026-10-28

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.