Self-Hosted CDN
Caching, failover to a backup origin, rate limits, human checks and IP, region and TLS-fingerprint rules, all handled by the Nodekeeper edge that runs on ports 80 and 443 of your own servers. The bandwidth and machines are yours, and so are the traffic logs and analytics, so your sites never have to pass through someone else's network. Personal is enough to start. To turn several nodes into one edge network, or to sell CDN plans to customers, look at Business.
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.
On this page: Who it is for · Caching and always-online · Origins · Protection · Multiple nodes · Certificates · Analytics · Providers · Plans · FAQ
For site owners, web agencies and ops teams that already have servers and want a cache and a protection layer in front of their sites, without paying a third-party CDN for traffic and feature tiers.
Put edge nodes in data centers close to your visitors, and requests that hit the cache never travel back to the origin. Where the nodes go, and how many, is up to you.
Images, scripts, styles and downloads are served from the edge cache. Large files and video are cached in ranges, so the origin is not asked for the whole file every time.
Limit requests per IP and either block or challenge the excess. Add IP and region rules and TLS-fingerprint blocking, and part of the junk is stopped before it reaches your site.
You pay a licence per node, not per gigabyte, and the bandwidth is the one you already have. Whether that is cheaper depends on your traffic, so run the trial and compare.
The edge service, access logs and visitor analytics all live on your own Nodekeeper servers.
When the origin returns 5xx or times out, the edge can keep serving what it cached earlier. With a backup origin configured, traffic moves over on its own.
When you create a CDN site, the Cache tab decides what is cached and for how long.
Set the TTL, the maximum file size, and the methods and status codes that apply for each path pattern, such as *.html, *.css, *.js or *.jpg. Build the cache key from the query string, Host, client IP and User-Agent, and set how long logs are kept.
If the origin returns 5xx or times out, the edge serves the copy it cached earlier. A separate permanent-fallback switch serves the cache whenever one exists, even after it has expired.
Range requests are answered from cache. Smaller files are cached whole and sliced in memory; larger ones are cached in slices, and when several visitors ask for the same slice at once, the origin is fetched only once. The slice size is configurable.
Rewrite request and response headers, replace text in responses (for example an old domain name in your pages) and set redirects at the edge, without touching the origin application.

A CDN site can have more than one origin, plus a designated backup origin.
When an origin cannot be reached, the edge stops sending it requests and uses the other origins or the backup. It keeps probing the dead one and puts it back as soon as it answers again.
With a single origin the edge still retries a failed request, but there is nowhere else to send it; failover needs at least two origins. The panel's uptime monitor is a separate feature and does not take origins out of rotation.
An origin-fetch engine that impersonates a browser's TLS fingerprint, with HTTP/3 and proxy support, is for origins that block by TLS fingerprint. It is switched on per site and belongs to Business; if it is unavailable, the standard engine takes over.
On the same edge layer, abnormal traffic is handled in steps from light to heavy, with rules bound per site.
Cap requests per IP in a time window, globally, per site or per URL prefix. Past the limit you can block outright (429) or show a JS challenge or an image captcha first, with a configurable grace count and block duration.
A JS proof-of-work check, an image captcha or a JS check lets a suspicious visitor prove they are real before you block them. Passing sets a cookie. The page is our own minimal one and is not themed per site.
Allow or block by source IP, IPv4 and IPv6, or by country, city and ASN. Several allow sets are combined, and so are several block sets.
A connection that matches a blocked fingerprint is dropped before the TLS handshake completes. It works against scanners and scrapers whose fingerprint stays the same. The list can be global or per site.
A source IP that keeps tripping the rate limit can be escalated to a block in the system firewall (nftables), where its packets are dropped at the network layer, saving CPU and bandwidth. The block expires by itself, and a whitelist keeps you from locking yourself out. The switch is off by default.
JA3 fingerprints · IP / CIDR rule sets · GeoIP rules · WAF · Security

One server is enough to run a CDN. To put an edge node in each of several data centers and manage them together, bring them into a sync group.
Edge nodes in a group share defence rules, CDN sites and forwarding settings: change one place and every node in the group follows. A group can be bound to a domain and a prefix, which creates a wildcard record pointing at the IPs of all member nodes. A node can carry several IPv4 and IPv6 addresses.
Host a domain's DNS on Nodekeeper's own authoritative server and return different answers by continent, country, region, city, ISP, domain or connection type, with a minimum TTL of 60 seconds. ISP, domain and connection type again need the commercial GeoIP2 database.
Much like an orange cloud: on the A, AAAA and CNAME records of a domain hosted on Nodekeeper's DNS, CDN is one toggle.
Certificate issuing and renewal are on every plan. The two items below need sync groups or Nodekeeper's own DNS and are From Business: with several edge nodes, issued and renewed certificates can sync to the nodes you choose, so you do not upload them node by node.
Syncing is opt-in: tick a sync group on each certificate, and the private key goes only to that group. Both new and renewed certificates sync automatically.
For external domains, validation uses an HTTP file, and the challenge file is pushed to the edge nodes while it runs, so it succeeds even when the domain already resolves to your CDN. For domains on Nodekeeper's own DNS, the DNS record that wildcard validation needs is written by Nodekeeper itself.
CDN sites, domain aggregates and standalone sites that are not hosted on Nodekeeper share one analytics list, so traffic, sources and devices are in one place. If a site sits behind another CDN with Cache Everything turned on, analytics has a CDN-mode setting for it.

Hosting providers and web agencies can turn their own edge nodes into a CDN product: plans can include some traffic, customers buy traffic packages or top up, and ordering and renewal run through a billing system or the hosting API.
Each site's outbound traffic is metered daily and deducted from its traffic packages, oldest package first.
When the balance is used up, the site is suspended and deleted after a 7-day grace period. There is no throttling step; it is either on or off, so say so in the plan terms you give customers.
First month $0, then $29/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.
| Feature | Free | Personal | Business |
|---|---|---|---|
| CDN sites: cache rules, origin settings, range cache | — | ✓ | ✓ |
| Stale copy when the origin fails | — | ✓ | ✓ |
| Several origins, a backup origin, automatic removal and recovery | — | ✓ | ✓ |
| Header rewrite, content replace, redirects | — | ✓ | ✓ |
| Rate limits and human verification | — | ✓ | ✓ |
| IP / CIDR, region (GeoIP) and JA3 / JA4 rules | — | ✓ | ✓ |
| Firewall escalation (nftables) | — | ✓ | ✓ |
| Analytics for CDN sites | — | ✓ | ✓ |
| Certificate issuing and renewal | ✓ | ✓ | ✓ |
| Browser-fingerprint origin engine (HTTP/3, proxy) | — | — | ✓ |
| Sync groups: rules, CDN sites and forwarding shared across edge nodes; certificates synced per group | — | — | ✓ |
| Built-in authoritative DNS, GeoDNS, per-record CDN switch | — | — | ✓ |
| CDN plans and traffic packages (sold through a billing system or the hosting API) | — | — | ✓ |
| Price (per node, billed monthly in USD) | Free | $3/month | $29/month |
See the pricing page for prices and the full comparison. Every server that runs Nodekeeper needs its own licence. When a paid licence ends, the node keeps running on Free features and the paid features stop working.
They give you their own global network and bandwidth, ready to use. Nodekeeper gives you no network; it manages your own servers and bandwidth. Your data and logs stay on your machines, and the cost is your bandwidth plus a per-node licence, with no per-traffic billing. The trade-off is reach: you cover as many places as you deploy nodes, and there are no ready-made global points of presence. If your visitors sit in a few regions that can be a good deal; for worldwide coverage you would have to place nodes there yourself.
Yes. Caching, the stale copy on origin errors, rate limits, human checks and IP, region and fingerprint rules all work on a single server. Failing over between origins needs at least two origins. Combining several nodes into one edge network, GeoDNS and the one-click CDN switch need Business.
It stops part of them, not every bot. Rate limits, human checks, IP and region rules, TLS fingerprints and firewall escalation are tools you use in steps, and the result depends on how you set them. An attack that simply saturates your bandwidth cannot be answered by edge rules; that takes protection further upstream at your network provider.
For country, city and ASN rules, the free GeoLite2 database is enough, and Nodekeeper downloads and refreshes it monthly. Rules on ISP, domain or connection type (residential, data center, mobile) need MaxMind's commercial GeoIP2; without it those three rules never match, and the rest are unaffected. Keep in mind that IP geolocation is only an estimate.
No. A new CDN site does not go through the WAF until you tick at least one WAF rule set on the site's Security tab. The basic ModSecurity WAF rule sets are included in every plan.
Install Nodekeeper, create a CDN site, enter your origin address, then 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.
First month $0, then $29/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.
Related: Analytics · Web hosting · Security · Hosting providers · Guide: planning a self-hosted CDN · Docs: CDN sites · Docs: sync groups · Docs: GeoIP · Pricing
Manage websites, office PCs and servers from one panel on your own hardware.