Guide · CDN
A self-hosted CDN is one or more edge servers that you run in front of your origin. Before you build one, settle three things: where the edge nodes sit, what they cache and for how long, and which protection rules stand in front of the site. Nodekeeper's own edge, which runs on ports 80 and 443, does the caching, the backup origin and the request filtering from one panel. Bandwidth and servers are yours: it is software that manages them, not a hosted CDN service.
A small studio runs a content site and a shop from one origin server in a single data centre. Most readers are in Europe, a growing share is in East Asia, and the pages are heavy with images and a few large downloads. Twice this quarter the origin restarted during a deploy and visitors saw errors. Meanwhile a scanner keeps requesting the same login paths. The studio has two spare servers it can place closer to its readers and wants an edge layer it controls.
The picture below is the layout this guide plans for. A visitor's lookup returns the nearest edge node; the edge answers from cache when it can and goes to the origin only when it must.
Start from your visitors, not from your servers. Look at where readers come from, pick the one or two regions that hurt most, and put one edge node in each. A single edge node already gives you the cache, the backup origin and the filtering. More nodes only shorten the distance for visitors who are far from the first one.
This guide covers failover to a backup origin. It does not cover moving visitors between edge nodes when a whole node is down: treat that as its own decision, together with the DNS and TTL choices you make for the domain.
Caching is a list of promises about how stale a page may be. Write the list before you set a single TTL.
| Content | Stance | Watch for |
|---|---|---|
| Images, CSS, JavaScript, fonts | Cache for a long time | Version the file name when you change a file, so visitors do not keep an old copy. |
| Public HTML pages | Cache briefly | A short TTL keeps edits visible quickly while still absorbing traffic spikes. |
| Large downloads and video | Cache, with a per-file size limit | Partial (Range) requests are served from cache, and several visitors asking for the same part make one request to the origin. |
| Logged-in pages, carts, checkout | Do not cache | Leave these paths out of the cache rules, and check which methods and status codes each rule covers. |
In the cache settings you give each path pattern its own TTL, maximum size per file, methods and status codes. You also choose what the cache key is built from: the query string, the Host header, the client IP and the User-Agent. Every part you add splits the cache into more copies, so add only what changes the page.

With stale-on-error on, an origin that answers with a 5xx error or times out no longer shows visitors an error page for anything the edge already has: the edge serves the old copy instead. A separate permanent-fallback switch serves the cached copy whenever one exists. The order is fixed: a normal cache hit first, then the stale copy if the origin fails, then a 502 for what was never cached. So it protects pages people have already requested, and it cannot invent a page the cache has never seen.
Give a site a primary origin and a backup origin. An origin that stops answering is dropped from rotation automatically and traffic goes to the backup; the edge keeps checking the dead origin and puts it back when it responds. A site with a single origin still retries a failed request, but has nowhere else to send it.
This is a suggested order to set the rules up, not the order the edge evaluates a request.

Everything below is in the same panel, and the edge itself is Nodekeeper's own software rather than something you assemble from separate parts.
| What you decided | What Nodekeeper gives you | Starts with |
|---|---|---|
| An edge on your own server | CDN sites on Nodekeeper's in-house edge, ports 80 and 443 | Personal |
| What to cache | Per-path TTL, file size limit, methods and status codes; cache key choices; Range cache for large files and video | Personal |
| Staying up when the origin fails | Stale-on-error, permanent fallback, several origins and a backup origin with automatic recovery | Personal |
| Changing what visitors see | Header rewrite, content replace and redirects at the edge | Personal |
| Who gets in | IP / CIDR sets, GeoIP rules, JA3 / JA4 blocklist, per-IP rate limits, human verification, firewall step | Personal |
| HTTPS on every edge | Certificate issuing and renewal, synced to the node group you choose | Every plan |
| Seeing the traffic | CDN sites appear in the same analytics list as your other sites | Personal |
| Several edge nodes, one setup | Sync groups | Business |
| Nearest node by region | Authoritative DNS with GeoDNS and a per-record CDN switch | Business |
| Origins that check browser fingerprints | High-performance origin fetch with browser fingerprint impersonation, HTTP/3 and proxy support, chosen per site | Business |

If you resell CDN through a billing system or the hosting API, that side of it is Business.
No. You run the edge nodes on your own servers and pay for their bandwidth yourself. Nodekeeper is the software that turns them into a CDN and manages them from one panel.
No. CDN sites, cache rules, stale-on-error, backup origins and the protection rules start with Personal. Business adds sync groups for several nodes, authoritative DNS with GeoDNS, and the per-record CDN switch.
The edge can only serve what it has stored, so those requests get a 502. That is why a backup origin matters as much as stale-on-error: one covers cached pages, the other covers everything else.
Yes. CDN sites appear in the same analytics list as domain aggregates and standalone sites. Heatmaps and replay are off by default for each site, and script-based analytics is not a count of total traffic.
Put the cache and the protection rules in front of one site first, then decide whether a second node is worth it. CDN sites are included from Personal.
30-day trial of Personal: monthly subscription, first month $0, card required, once per account, up to 3 nodes. Cancel before day 30 and you are not charged; after that, Personal renews at $3 per node per month.
Prefer to start on the free plan? Download it and add Personal when you are ready for the CDN. Compare plans on the pricing page.
Manage websites, office PCs and servers from one panel on your own hardware.