Product Tour: Run Your Own CDN to Speed Up and Protect a Website

Start by creating a CDN site, then set up caching, a backup origin, rate limiting, a human check, and IP, country and TLS-fingerprint rules. When one edge node is not enough, join several into one network with a sync group and GeoDNS, or turn the CDN into a plan you sell to customers. The steps below follow the order you would work in, and each one points to a place in the panel.

From Personal Multi-node sync groups, GeoDNS, CDN plans and traffic packages: Business

Format: illustrated guideData: no customer systems or customer data

First month $0, then $3/month per node, billed monthly. Card required, once per account; cancel before day 30 and you are not charged. The trial covers up to 3 nodes.

Live Demo: try a real panel

Free, no sign-up. It opens a real Nodekeeper panel with a demo account and password already filled in — just click Log in. You can create a website and preview it, and add a domain and DNS records. Data resets daily at 20:30 UTC, and the demo is shared with all visitors, so please do not enter personal information. For safety these are disabled: changing the account or password, two-step verification, adding users, firewall rules, backup restore, ordering and billing management, uploads over 64 MB, and browsing server folders. We recommend opening it in a private window so it does not mix with a panel you are already logged in to.

Live Demo

Step 1 · Create a CDN site From Personal

  1. In the panel's CDN menu, create a CDN site: enter the domain you want to speed up and the address of the origin (your existing web server).
  2. The edge service listens on ports 80 and 443 of this server. Point the domain at it and visitors reach the edge first: cache hits are answered there, misses go back to the origin.
  3. Certificate issuing and renewal are included in every plan; for HTTPS, pick the certificate in the site settings.

One server is enough to run a CDN. The bandwidth and the machine are yours, and access logs and statistics stay on that machine.

The next steps happen in the same dialog

The site dialog is split into tabs: Basic, Network & SSL, Backends, Cache, Security and Advanced. Caching is on the Cache tab, rule bindings on the Security tab, and the backup origin on the Backends tab.

Step 2 · Cache rules, and stale cache when the origin fails From Personal

  1. Open the site's Cache tab. For each path pattern (*.html, *.css, *.js, *.jpg and so on) set the cache time, the maximum size per file, and the request methods and status codes that apply.
  2. The cache key can combine query string, Host, client IP and User-Agent; log retention is set on the same tab.
  3. Turn on the serve-stale switch for upstream 5xx or timeout: when the origin returns a 5xx or does not answer, the edge serves the copy it cached earlier, so visitors see older content instead of an error page.
  4. For a stronger fallback, turn on the permanent fallback: as long as a cached copy exists, it is served even after it has expired.
Limits and prerequisites
  • Only content that was cached before can be served: the order is cache hit first, then the stale copy when the origin fails, and a 502 only if neither exists.
The Cache tab of the New CDN site dialog: cache time and size limits per path, and stale cache when the origin fails.
The Cache tab of the New CDN site dialog: cache time and size limits per path, and stale cache when the origin fails. Addresses, accounts and domains are redacted.

Step 3 · Multiple origins and a backup origin From Personal

  1. On the Backends tab, add several origins to the site and mark one as the backup origin.
  2. When an origin cannot be reached, the edge stops sending it requests and shifts the traffic to the other origins or the backup.
  3. The edge probes the removed origin from time to time and puts it back once it answers again.
Limits and prerequisites
  • Automatic switching needs at least two origins. With a single origin the edge still retries once under the retry rules, but there is nowhere else to send the request.
  • The uptime monitor in the panel is a separate feature; it does not take an origin out of rotation.

Step 4 · Rate limiting From Personal

  1. On the Microservice Rate Limit page, add a rule and choose its scope: global, one site, or one URL prefix.
  2. Set how many requests one IP may make in a time window, for example 5 requests per 10 seconds for /contact.html.
  3. Choose what happens beyond the limit: block directly (HTTP 429), or first ask the visitor to pass a JS check or an image captcha. The grace count and the block duration are adjustable.
  4. A changed rule takes effect immediately, with no restart.
Limits and prerequisites
  • Counting is aggregated asynchronously in the background, so a fast burst can get a few extra requests through; it is not guaranteed that request N+1 is refused.

Step 5 · Human check From Personal

  1. Set the action for requests over the rate limit to a challenge instead of a direct block: a suspicious visitor first sees a verification page.
  2. The checks are a proof-of-work JS challenge, an image captcha and a JS check. Once passed, a cookie is set so the visitor is not asked again on every request.
  3. People pass and carry on; scripts and crawler tools do not.
Limits and prerequisites
  • The verification page is a minimal page of our own and does not follow the site theme.
  • Rules work as you configure them and cannot recognise every bot.

Step 6 · IP, country and TLS-fingerprint rules From Personal

  1. First build the rule sets in the rule libraries: IP / CIDR rule sets (IPv4 and IPv6), GeoIP rule sets (country, city, ASN and more), and the JA3 / JA4 fingerprint blocklist.
  2. Open the site's Security tab and tick the rule sets this site should use. Rules are bound per site, each set is either allow or block, several allow sets are combined as a union, and so are several block sets.
  3. A connection whose fingerprint is on the blocklist is dropped before the TLS handshake completes, which works against scanners and crawler tools with a fixed fingerprint. The list can be global or per site.
  4. A new CDN site does not go through the WAF by default: tick at least one WAF rule set on the same tab to turn it on.
Limits and prerequisites
  • Country, city and ASN rules work with the free GeoLite2 data; rules by ISP, domain or connection type need MaxMind's commercial GeoIP2 database and do not match without it. IP geolocation is only an estimate.

JA3 fingerprints · IP / CIDR rule sets · GeoIP rules · WAF

The global JA3 / JA4 TLS fingerprint blocklist: a connection matching any entry is dropped before the TLS handshake.
The global JA3 / JA4 TLS fingerprint blocklist: a connection matching any entry is dropped before the TLS handshake. Addresses, accounts and domains are redacted.

Step 7 · Several edge nodes: sync groups and GeoDNS From Business

  1. Put one Nodekeeper edge node in each location.
  2. Create a sync group and add the nodes. Defence rules, CDN sites and forwarding configuration are synchronised across the group: change one, and the whole group follows.
  3. Host the domain's DNS on Nodekeeper's own authoritative DNS and use GeoDNS to return different nodes to visitors by continent, country, region, city and more. The minimum TTL is 60 seconds.
  4. Switch the CDN on with one click on a DNS record (like an "orange cloud"): the record now points at the edge nodes, its old value automatically becomes the origin, and the matching CDN site is created. Switch it off and the original record is restored.

Docs: sync groups → · Docs: own DNS server

Limits and prerequisites
  • Only A, AAAA and CNAME records can have the CDN switch; TXT, MX, NS and GeoDNS records cannot.
  • A sync group synchronises rules, CDN sites and forwarding configuration; website files and databases are not part of it.
  • GeoDNS conditions by ISP, domain or connection type also need the commercial GeoIP2 database.
  • Failover is confirmed at the origin level only; switching DNS away from an edge node that is itself down is outside what this page promises.

Step 8 · Sell the CDN to customers as a plan From Business

  1. An administrator defines a CDN plan from a sync group and a CNAME target; the plan can include an amount of traffic.
  2. Customers buy traffic packages or top up their traffic; ordering and renewal go through the billing system or the hosting API.
  3. Outbound traffic is metered per site per day and deducted from the traffic packages first in, first out.
Limits and prerequisites
  • When the traffic runs out, the site is disabled and deleted after a 7-day grace period. There is no throttled mode: it is either on or off, so say so in the plan description you give your customers.

Hosting providers: automated delivery and quotas →

Step 9 · See analytics for the CDN site From Personal

  1. The CDN site appears in the analytics list on its own, in the same table as domain aggregates and standalone sites that are not hosted on Nodekeeper.
  2. Click View data for page views, visitors, sources and devices; turn on heatmaps and session replay per site when you need them.
Limits and prerequisites
  • JS analytics only counts visits that ran the analytics script. It is not total server traffic and not a basis for bandwidth or billing.
  • Heatmaps and session replay are off by default for each site and switched on as needed.

Self-hosted website analytics, heatmaps and session replay →

Try it on your own server

Install Nodekeeper, create a CDN site, enter the origin address and point the domain at it. The Personal trial covers up to 3 nodes.

First month $0, then $3/month per node, billed monthly. Card required, once per account; cancel before day 30 and you are not charged. The trial covers up to 3 nodes.

Further reading: Self-Hosted CDN · Guide: building a self-hosted CDN · Docs: CDN sites · Docs: sync groups · Pricing · Download Free

Tell us which websites, office PCs or infrastructure you want to manage and we will arrange a walkthrough. Please do not send passwords, keys or customer data.

N Nodekeeper

Manage websites, office PCs and servers from one panel on your own hardware.

Support
[email protected] WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.