Главная / Гайды / Self-Host Uptime Kuma Anonymous VPS
Ops guide

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

Self-host Uptime Kuma on a no-KYC VPS. Starter is $8.50: 2 vCPU, 4 GB, 60 GB NVMe. Compose + volume. Deploy →

Полный текст статьи на английском. Шапка, каталог и оплата переведены.

self host uptime kuma anonymous vps — private Uptime Kuma on a no-KYC VPS

Why self-host Uptime Kuma

SaaS status pages see every probe: target URLs, incident notes, who is on-call. A copy you run on a no-KYC KVM keeps that file on your disk. Uptime Kuma is a small Node dashboard: HTTP/TCP/ping monitors, heartbeats, a status page if you turn one on. We rent root; we do not operate the checker. Legal targets only. CSAM and attacks are AUP fails. For checkout hygiene (inbox, wallet, tunnel) use the anonymous VPS guide.

self host uptime kuma anonymous vps — no-KYC KVM for a private status checker

VPS from $5.49/mo. Token-only or email + password, then a crypto invoice.

Запустить сейчас

Specs: Starter from $8.50

Catalog Starter (data.py): $8.50/mo, 2 vCPU (AMD EPYC 7443P / 3.2 GHz), 4 GB DDR4 ECC, 60 GB NVMe, unmetered / 1 Gbps, 1× IPv4 + /64. Same list price in all thirteen locations. Nested virt is on, so Docker Compose is in-scope. Nano ($5.49, 1 vCPU / 2 GB) can run a quiet checker; Starter is the honest floor if you also keep a reverse proxy and a few dozen monitors. Included L3/L4 DDoS filtering is on the SKU; it is not an L7 WAF for the dashboard. Token-only or email + password; crypto invoice. Open the Starter plan from $8.50.

Docker Compose install

Install Docker from distro packages. Put the Uptime Kuma tree you already have on the box (scp/rsync). Do not paste marketplace or VCS clone URLs. Persist /app/data on a named volume so recreating the container does not wipe monitors.

# 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

Bind 3001 to localhost until you put TLS in front. First boot: create the admin user in the UI, then add monitors. Snapshots are your rollback, not our managed backup SLA.

Dashboard (placeholder for a real screenshot). Dark list of monitors: name, type (HTTP / TCP / ping), last heartbeat, latency in ms, 24h uptime bar. Green = up, red = down, yellow = pending. Gear for notifications. Status-page toggle is off unless you mean to publish. Replace this caption with a WebP of your instance; do not ship a live admin cookie in the shot.

Monitor anonymously

The checker’s source IP is the VPS IPv4. Targets you ping will log that address. Do not put a public status page on a domain with real-name WHOIS if the point is a quiet probe box. Prefer SSH tunnel or WireGuard to the bound 3001 port instead of exposing the dashboard. Notification webhooks (Telegram, Discord, email) can name you — use a burner channel. Paying in crypto and skipping KYC does not anonymize the HTTP User-Agent Kuma sends. Harden sshd, then keep the dashboard off the public internet.

Need the checkout playbook again? anonymous VPS guide. Ready to size the box? Starter plan from $8.50.

Is Starter $8.50 enough for Uptime Kuma?

Yes. Starter is 2 vCPU / 4 GB DDR4 ECC / 60 GB NVMe at $8.50/mo. A quiet checker fits; add RAM if you also run a heavy reverse proxy.

Does NovaVPS operate Uptime Kuma?

No. We rent KVM with root. You run Compose and keep /app/data.

Should I publish a public status page?

Only if you accept that the page and the probe IP are public. Bind localhost and tunnel if the dashboard should stay private.

Готовы запустить?

Настройте VPS или dedicated, задайте пароль, оплатите счёт.

Network

Edge RTT

Uptime · 36h

Complaints · 36h

Pick a city