Self-Host Uptime Kuma on an Anonymous No-KYC VPS

Run Uptime Kuma on a no-KYC KVM: Sentry at $7.50 list ($6.00 annual) gives 2 vCPU, 4 GB ECC, 60 GB NVMe. Compose plus a volume.

Le corps de l'article est en anglais. L'interface, le catalogue et la caisse sont traduits.

Why self-host Uptime Kuma

A SaaS monitor records everything you would rather keep: every target URL, incident notes, on-call names, response latencies from its own vantage. A copy of Uptime Kuma on a no-KYC KVM keeps that file on your disk instead. The app is a light Node dashboard — HTTP, TCP and ping probes, heartbeat history, and an optional public status page. We rent the root server; running the checker is your side of the line. Probe only targets you have a right to watch: the AUP bans attack traffic, and CSAM is out everywhere. For the account and wallet side of the setup, follow the anonymous VPS guide.

Specs: Sentry at $7.50

Catalog Sentry (data.py): $7.50/mo list, $6.00 on the annual term, 2 vCPU (AMD EPYC 7443P / 3.2 GHz), 4 GB DDR4 ECC, 60 GB NVMe, unmetered / 1 Gbps, 1× IPv4 + /64. One list price covers all twenty-one locations, with Iceland and Switzerland as the only published premiums. Nested virtualization is enabled, so Docker Compose runs without argument. Scout — from $3* funded — will hold a quiet checker, but Sentry is the honest floor once a reverse proxy and a few dozen monitors join. L3/L4 DDoS filtering rides the SKU; that is not an L7 WAF for the dashboard itself. Token-only or email + password, then a crypto invoice. Open the Sentry plan at $7.50.

Docker Compose install

Install Docker from the distro's own packages, then move your existing Uptime Kuma tree onto the box with scp or rsync — no marketplace images or registry pulls. The one thing that must survive container recreation is /app/data, so mount it on a named volume as below.

# Save as docker-compose.yml next to ./uptime-kuma/
# Local build only. No registry or VCS URLs.
services:
  uptime-kuma:
    build:
      context: ./uptime-kuma
    container_name: uptime-kuma
    restart: unless-stopped
    ports:
      - "127.0.0.1:3001:3001"
    volumes:
      - kuma-data:/app/data
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"
volumes:
  kuma-data:

# docker compose up -d

Keep 3001 bound to localhost until TLS sits in front of it. First boot creates the admin user in the UI; then add monitors one by one. Snapshots are a checkout add-on and your rollback tool — there is no managed backup SLA on guest volumes in this catalog.

Monitor anonymously

Every probe leaves from the VPS IPv4, and every target you watch logs that address — that is the footprint, and no amount of crypto payment changes it. Skip a public status page on a domain whose WHOIS carries your name; that pairs a quiet probe box with a loud identity. Reach the dashboard through an SSH tunnel or WireGuard instead of publishing 3001. Notification webhooks to Telegram, Discord or mail can identify the operator — route them through a channel created for this box. Harden sshd before the first monitor goes live.

Need the checkout playbook again? anonymous VPS guide. Ready to size the box? Sentry plan at $7.50.