For high-traffic platforms

— statnive.live · self-hosted

Run statnive on your own infrastructure.

A single Go binary plus ClickHouse. No outbound calls. Air-gap capable. For regulated markets, customer-supplied data centers, and teams that want to own every byte.

Made in Germany Hosted in Nuremberg
Talk to engineering Read the architecture doc
Single Go binary + ClickHouse Zero outbound, air-gap 10,845 ev/s on one 8-core box BYO infra

— Measured on one self-hosted box

10,845 events per second, at 57% CPU.

The same engine, on hardware you control. On a single 8-core / 16 GB box under real production traffic, the load climbed tenfold and the database barely moved. It never became the bottleneck.

events / sec ClickHouse CPU, ~0.3 cores 1k ev/s 10,845 ev/s
Load climbs 10x. The database does not follow.
~0.3 cores
database CPU across a 10x load span
0.1 ppm
data loss at the 10,845 ev/s edge
~22 bytes
per event, compressed on disk
40+ days
in production, zero restarts

— System requirements

Reference single-box deploy.

Statnive's reference deployment runs comfortably on a single bare-metal or VPS instance. Scale up vertically before you reach for sharding. ClickHouse and the ingest binary both saturate cores before they saturate I/O.

Compute

8 cores · 32 GB RAM

Engineered for 100M+ events/day. Measured at 10,845 ev/s on an 8-core / 16 GB box, half this RAM. Scale CPU first; ClickHouse rewards core count.

Storage

NVMe SSD · 1–4 TB

~1 GB / 1M events compressed. Retention operator-configurable; 180-day default.

Network

No outbound required

Air-gap capable. Updates ship as signed binaries; no telemetry, no auto-update.

OS

Linux x86_64

Statically linked. No glibc version dependency. Reference: Ubuntu 22.04 LTS / Debian 12. arm64 build planned.

— Deployment

Single binary. systemd unit. Done.

No Helm charts, no operators, no service mesh. The binary is what runs in production.

  • Bring your own infra. Bare metal, VPS, on-prem, or regulated cloud. The binary does not care.
  • Reverse proxy in front. Caddy, nginx, or your existing edge. Statnive also serves HTTPS directly if you let it.
  • ClickHouse alongside. Either local or on a dedicated host. Schema migrations are versioned and re-runnable.
  • No outbound calls. No phone-home, no signed-update fetch, no third-party CDN, for environments where CDNs are restricted.
$ wget https://statnive.live/dl/statnive-live.tar.gz
$ tar -xzf statnive-live.tar.gz
$ ./statnive-live --config /etc/statnive-live/config.yaml
listening on :8443 ✓ ingest ready

— Air-gap deployments

For regulated markets and customer-supplied data centers.

Zero required outbound connections, verified running under a full outbound firewall block (iptables -P OUTPUT DROP). The self-hosted binary runs where third-party CDNs are restricted, where audit chains require local data residency, or where procurement mandates local currency and operator-configured local time. We ship the binary, the ClickHouse schema, and the architecture doc. You ship the box.

— Privacy invariants

The privacy contract, verbatim on every deploy.

  • No cookies. No localStorage. No sessionStorage.
  • No fingerprinting. No third-party scripts.
  • No outbound calls from the binary. Air-gap capable.
  • Daily rotating salts. Same visitor, different hash each day.
  • SHA-256+ only. No SHA-1 or MD5 in any security path.
  • DNT and GPC respected on by default.
  • Static binary, statically linked. No glibc surprises.
  • Schema migrations versioned and re-runnable.

Self-host on your terms.

Get the architecture doc, a reference deploy, and access to engineering for capacity questions.

Talk to engineering Self-host pricing
Get Statnive Free