Caching and acceleration, HTTPS, CC and WAF protection on your own servers. Attack sources, the number of blocked requests and the layer that blocked them can all be viewed in the console in real time. Visitor traffic never passes through a third party.
Acceleration, security and monitoring, integrated in one place
Run one command on any Linux server to turn it into a CDN node. It registers with the controller and receives its config automatically.
Cache rules, purge and prefetch; HTTPS certificates are issued and renewed automatically, with HTTP/2 and HTTP/3.
Access lists, CC, bots and scanners, the WAF rule engine, upload scanning and auto-ban, all configured in one panel.
Security Overview and Attack Logs are available in every plan; WAF Plus adds the security posture screen.
Edge misses ask a regional L2 node first, reducing origin requests by about 50% in our tests. Included by plan; see the pricing page.
Every console function is available through the HTTP API, authenticated with API keys, and the reference is public.
Available with WAF Plus, with full-screen display and automatic refresh. Without it, Security Overview and Attack Logs remain available.
Source countries and cities and the targeted edge node; bar height indicates the number of attacks
Refreshed every 5 seconds: time, source IP, target, matched rule, action
Blocked requests and origin traffic saved, by protection feature (CC, WAF, auto-ban, region blocking and others)
Scored from protection switches and rule sync status; each deduction links directly to the setting to correct
Rule pack: OWASP CRS v4 conversions + vulnerability patches; without Rules Update, the built-in 23 rules are used
Updated hourly · Rules Update
Every block can be traced to its request and matched rule
Blocked requests are counted per feature under Protection results on the security posture screen
All protection runs on the edge node, so malicious requests never reach your origin. Each layer can be enabled globally and configured per site.
One default level for all sites, which can be overridden per site
Basic protection is included in every plan; the features below are included by plan or available separately
Deeper detection, fewer false positives
Included in Enterprise and Unlimited
Learn more ›What is the difference between the basic WAF and WAF Plus? View comparison ›
These are actual screens from the demo console; you can log in and try it online
Each record shows the time, source IP and region, target site, matched rule and action; an IP can be banned or allowlisted in one click.
Select any metric to open Statistics and drill down by site, node or time range; data can be exported to CSV.
Certificate issuance, configuration pushes and cache purges all show their progress and failure reasons.
All figures come from real-server load tests; test conditions are listed under each item
About 1.64 million requests during config pushes and certificate swaps
p95 0.96 ms
4-core node, 1 KB HTTPS cache hits; median of three runs about 5.5k–6.0k
nginx validation 118 ms
Data from real-server load tests in a Los Angeles data center; nodes with 4 vCPU
Compared across four dimensions: data ownership, cost structure, security capability and operational effort
| gocdn (private deployment) | Public cloud CDN | Self-built Nginx | |
|---|---|---|---|
| Visitor traffic passes through a third party | No | Yes | No |
| Cost grows with traffic | Flat price per node | Billed by traffic | Server costs only |
| Your own servers and network | |||
| Central multi-node management and one-click rollout | Needs your own scripts | ||
| WAF / CC protection | Built in | Extra cost | Set it up yourself |
| Security Overview and Attack Logs | Built in | Extra cost | |
| Emergency rules for new vulnerabilities | Rules Update · hourly | Watch it yourself | |
| Automatic HTTPS certificate issuance and renewal | Set it up yourself | ||
| From zero to your first accelerated site | About 10 minutes | About 10 minutes | Days |
The first site is onboarded in about 10 minutes on average
Leave your contact details and we will send you the controller install command (usually within 1 business day).
Run the install command on a Debian 13 / Ubuntu 26.04 server with 4 GB+ RAM, then access it in your browser.
t=$(mktemp) && curl -fsSL https://provider/i/•••••••• -o "$t" && bash "$t"; r=$?; rm -f "$t"; (exit $r)Copy the node command from the controller and run it on each node; add a domain and point its CNAME to the node to start acceleration.
www.example.com CNAME www.example.com.cdn.your-domainPlans differ in node limits and add-ons ·
For solo builders and small teams
10 nodes · Unlimited sites
Includes
For growing multi-region teams
60 nodes · Unlimited sites
Everything in Starter, plus
For large fleets and heavy traffic
300 nodes · Unlimited sites
Everything in Professional, plus
No caps on nodes or sites
You can choose monthly, quarterly, semiannual or yearly, and the period can be changed at renewal. Longer periods cost less per month.
gocdn is a private-deployment CDN solution. You deploy nodes on your own servers and manage caching and acceleration, HTTPS certificates, CC protection, WAF and real-time monitoring from one controller, with a complete HTTP API.
Visitor traffic does not. The controller and nodes run on your servers, and access logs and site content stay on your own machines. The controller only reports running status, usage totals, and suspicious IPs and request samples used for threat intelligence.
Self-service trials are not available at present. Please contact us to arrange one.
Open the live demo, or contact us for a quote and the install command