Starter
Special offerFor solo builders and small teams
- Includes CDN, caching and HTTPS
- HTTP/3 and live analytics
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.

Run one command on a supported Linux server (Debian 12/13, Ubuntu 24.04 LTS or later) 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; in a test with 2 edge nodes and 2,400 requests, origin requests fell from 544 to 300 (−45%). Included by plan; see the pricing page.
Tiered origin detailsAn HTTP API authenticated with API keys; the API reference and OpenAPI spec are public.
20 checks across TLS configuration, security headers, origin exposure and known-vulnerability probing; protection baselines by site type, with bulk remediation.
Config rolls out 1 node → 10% → all, with automatic rollback on regression; upgrade packages are signature-verified.
TLS 1.3 (0-RTT), HTTP/3 (QUIC) and 103 Early Hints; Always Online serves cached content when the origin is unreachable.
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 + exploited-vulnerability virtual patches (CISA KEV baseline); 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
Lists, CC, Bot, WAF, upload scanning and auto-ban filter in turn, all on the edge node.
Select any layer for its key pointsDemo animation · not live data

One default level for all sites, which can be overridden per site
used when no rule pack is available
OWASP CRS v4 conversions + virtual patches for exploited vulnerabilities + emergency rules
Known malicious sources, blocked at the node on match
Virtual patches for exploited-in-the-wild vulnerabilities are tracked against the CISA KEV catalog and pushed hourly to every edge node, with no version upgrade.View security details
Basic protection is included in every plan; the features below are included by plan or available separately
OR, quotes and other keywords1 match'1'='1' is always true, so it is flagged as injectionBlockedWhat 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
Select any metric to open Statistics and drill down by site, node or time range; data can be exported to CSV.
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.
Certificate issuance, configuration pushes and cache purges all show their progress and failure reasons.



Every figure comes from a real-server load test, with the test conditions listed under each card.
About 2.9 million requests during config pushes and certificate swaps
p95 0.99 ms
4-core node, 1 KB HTTPS cache hits; median of three runs about 8.1k–13.8k
nginx validation 144 ms
Real-server load tests; nodes with 4 vCPU
From commit to live on one node, with 2,000+ sites already hosted
Verified on a single node first
Wider scope, node health still watched
Pushed to the remaining nodes once the first two stages pass
Staged rollout; every upgrade package is signature-verified
For 5 minutes after a new config goes live, each node watches its own 5xx rate and worker crashes, and rolls back locally if either regresses.
Public cloud and self-built each trade something off: gocdn keeps traffic and data on your own servers and ships protection and operations ready to use.
| Features | 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 | Hardware cost only |
| Your own servers and network | |||
| Central multi-node management and one-click rollout | Custom orchestration required | ||
| WAF / CC protection | Built in | Extra cost | Self-managed deployment and tuning |
| Security Overview and Attack Logs | Built in | Extra cost | |
| Virtual patching for exploited-in-the-wild vulnerabilities | Rules Update · hourly | Manual vulnerability-intel tracking | |
| Automatic HTTPS certificate issuance and renewal | Self-built certificate issuance and renewal | ||
| From zero to your first accelerated site | About 10 minutes | About 10 minutes | Several days |
The first site can be onboarded in about 10 minutes
you@mail › Submit your contact details ✓ Controller install command received debian@master $ t=$(mktemp) && curl -fsSL https://provider/i/•••••••• -o "$t" && bash "$t"; r=$?; rm -f "$t"; (exit $r) ✓ Controller is ready; open it in your browser debian@edge-1 # Copy the node command from the controller and run it on each node ✓ Node registered with the controller; config pushed # After adding a domain, point its CNAME to the node www.example.com CNAME www.example.com.cdn.your-domain ✓ Acceleration started
Terminal output is illustrative; use the address and token shown in your controller
Plans differ in node limits and add-ons ·
For solo builders and small teams
For growing multi-region teams
For large fleets and heavy traffic
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; see the Privacy Policy.
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