Personal

Speed Up and Protect Your Sites. Understand Your Visitors. Connect Your Servers.

The Free plan already runs your sites with isolation, a base WAF, certificates, mail, backups and uptime monitoring. Personal is for people who run websites seriously: a self-hosted CDN (edge caching, the old cached copy served when the origin fails, rate limits and human checks), self-hosted analytics with heatmaps and session replay, log viewers, and mesh networking between your servers. Your data and your traffic stay on your own servers.

$3/month, or $30 billed annually, per node

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: Self-hosted CDN and traffic rules · Visitor insight · Mesh networking · Free vs. Personal · Billing

1

Self-hosted CDN: Speed Up Your Sites and Keep Abnormal Traffic Out

Put a CDN layer of your own in front of your websites and decide what gets cached and who gets in. The bandwidth and servers are yours; Nodekeeper is the software that manages them, not a hosted CDN service:

  • Cache rules: cache time, size limit, methods and status codes per path; the cache key can combine query string, Host, client IP and User-Agent. Large files and video are served with Range caching.
  • Your site stays up when the origin has a bad day: if the origin returns 5xx or times out, the cached copy is served instead. Add several origins and a backup origin; a failing origin is dropped automatically and brought back when it recovers.
  • Edge rewrites: request and response header rewrites, content replacement and redirects.
  • Abnormal traffic handling: rate limits (block outright, or show a human check first), IP and GeoIP rules, a human check in front of a site, and JA3 / JA4 client-fingerprint rules. A source that keeps tripping a rule can be escalated to the system firewall.
Limits and prerequisites
  • The stale copy can only answer for content that was cached earlier. 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.
  • Rules work as you configure them and cannot recognise every bot; rate-limit counting is asynchronous, so a fast burst can let a few extra requests through. Escalating to the system firewall needs a host with nftables and is off by default; without nftables only the application-layer rules apply.
  • GeoIP country, city and ASN use the free database. ISP, domain and connection type need a commercial GeoIP database; without it those rules never match. IP location is an estimate.
  • The browser-fingerprint origin engine, multi-node sync, and selling CDN plans and traffic packages are part of Business.

See everything the self-hosted CDN does →

Cache settings in the New CDN site dialog: per-path TTL and size limits, stale cache served when the origin fails.
Cache settings in the New CDN site dialog: per-path TTL and size limits, stale cache served when the origin fails. Addresses, accounts and domains are redacted.
Global JA3 / JA4 TLS fingerprint blocklist: matching connections are dropped before the TLS handshake completes.
Global JA3 / JA4 TLS fingerprint blocklist: matching connections are dropped before the TLS handshake completes. Addresses, accounts and domains are redacted.

2

See How Visitors Actually Use Your Website

A site can load fine while visitors leave at the form or the menu, and a CPU graph will not tell you. Personal adds the answers to the panel you already use:

  • JS website analytics: page views, sessions, real-time visits, events, goals and funnels.
  • Heatmaps: see where visitors click on a page.
  • Session replay: watch a real visit again to find what goes wrong on a page.
  • Country and city reports based on visitor IP addresses.
  • One analytics list: CDN sites appear next to your standalone sites and domain aggregates in the same visitor analytics list.
  • Website-log and WAF-log viewers. The WAF log records the requests that WAF rules stopped.
Limits and prerequisites
  • Heatmaps and session replay are off by default for each site. You switch them on where you need them.
  • Replay masks password fields by default. Mask other fields with CSS selectors before you record pages that contain personal data.
  • Locations are estimated from IP addresses. JS analytics counts only visits that run the tracking script, so it is not total server traffic.

Self-hosted website analytics, heatmaps and session replay →

Analytics overview: totals and daily trend, compared with the previous period.
Analytics overview: totals and daily trend, compared with the previous period. Addresses, accounts and domains are redacted.
Heatmap: clicks drawn over a copy of the page, switched on per site.
Heatmap: clicks drawn over a copy of the page, switched on per site. Addresses, accounts and domains are redacted.

3

Connect Several Servers into One Private Network

Mesh networking links your nodes over an encrypted network so services on different servers and in different locations can reach each other privately. You manage it in the panel instead of maintaining a separate VPN and tunnel tooling.

Limits and prerequisites
  • Every server in the mesh runs Nodekeeper and is licensed per node.
  • The overlay is one flat network where all members can reach each other. Segmented access rules are not available yet.
  • The client for remote staff laptops is part of Pro.

Multi-site networking and port forwarding →

Free vs. Personal

Personal is not where security starts. Free already has it. Personal adds more insight, traffic control and multi-server tools.

CapabilityFreePersonal
Sites, runtimes, databases, cron, systemd, Supervisor, reverse proxyIncludedIncluded
Site isolation, site SSH / SFTP and FTP, member accountsIncludedIncluded
Base WAF, system firewall, port forwarding, operation recordsIncludedIncluded
Domain and wildcard certificates, mail, scheduled backup and restoreIncludedIncluded
Uptime monitoring for sites and hostsIncludedIncluded
Website analytics, heatmaps, session replay, IP location reports—Included
Self-hosted CDN, rate limits, IP / GeoIP rules, human check, JA3 rules—Included
Website-log and WAF-log viewers—Included
Mesh networking between nodes—Included
PriceFree$3/month, or $30 billed annually, per node

Need user groups and roles, eBPF tamper protection or virtual machines? They start at Pro ($7/month, or $70 billed annually, per node).

How Billing Works and How to Start

  • Priced per node: each server that runs Nodekeeper needs its own licence.
  • Monthly billing charges the monthly price. Annual billing charges the full-year price once. The trial is available as a monthly subscription only.
  • If a paid licence ends, the node keeps running with the Free feature set and the paid features stop working.

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.

N Nodekeeper

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

Support
support@host.mw WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.