VPS for self-hosted uptime monitoring (Uptime Kuma)

Run Uptime Kuma on a VPS to monitor your sites and services and host your own status page — from a server outside your own infrastructure, so it can still alert you when your main box goes down. Dedicated IP, crypto payment, no KYC. From $8/mo.

The one rule of monitoring is that the monitor has to live outside the thing it watches. A health check running on the same server as your app is useless the moment that server goes down — they fail together, and no alert ever fires. So you want a small, independent box whose only job is to watch everything else and tell you when it breaks. Uptime Kuma is the self-hosted tool for exactly that, and a cheap VPS is its natural home.

Why self-host it

Independence. On its own VPS — ideally a different region from your main infrastructure — Uptime Kuma keeps checking and alerting even when your primary server or home connection is down. That's the entire value of a monitor.
Control and privacy. Your list of monitored endpoints, your alert rules, and your status page live on a server you own, not a third-party dashboard that knows your whole stack. Flat monthly cost, no per-monitor pricing.
A status page you host. Uptime Kuma publishes a clean public status page — on your own domain, telling your users what's up, without renting a status-page SaaS.

What it needs

A dedicated IPv4, a domain and HTTPS. You reach the dashboard and status page at https://status.yourdomain.com, which needs a domain, valid TLS and inbound 443 — a dedicated-IP plan. NAT plans don't take inbound. Nano-IP ($8/mo) runs dozens of monitors comfortably.
Light resources. Uptime Kuma is small; RAM grows only with the number of checks and retained history. Add headroom for hundreds of endpoints, otherwise the smallest box is fine.

Set it up (Ubuntu 24.04, Docker)

# dedicated-IP plan, root shell
apt update && apt install -y docker.io caddy
systemctl enable --now docker

docker run -d --restart=unless-stopped \
  -p 127.0.0.1:3001:3001 \
  -v uptime-kuma:/app/data \
  --name uptime-kuma louislam/uptime-kuma:1

# TLS + reverse proxy on your domain
echo 'status.yourdomain.com { reverse_proxy 127.0.0.1:3001 }' > /etc/caddy/Caddyfile
systemctl restart caddy && ufw allow 80,443/tcp

Point status.yourdomain.com at your IP, open it, create the admin user, and add monitors — HTTP(S), TCP port, ping, DNS, and more. Wire up notifications (Telegram, email, webhooks, ntfy) so an outage reaches you, and publish a status page for the services you want public.

Who this is for

Devops and self-hosters who want an independent watchdog over their own servers and services.
Small teams that need a status page and alerting without paying per-monitor for a hosted tool.
Anyone running a home lab who wants a cloud vantage point that stays up when the house connection doesn't.

Why EQVPS for Uptime Kuma

Dedicated IPv4 from $8/mo, domain + HTTPS friendly, all ports, self-service rDNS.
EU locations (Germany, Finland) — and because we run two regions, you can place the monitor away from your main box for genuine independence.
No KYC, crypto payment. Email to register, USDC/USDT to pay.
Root in ~60 seconds, NVMe. Bring up Uptime Kuma, add Caddy, and your own monitoring is live.

Running several services on one box already? See self-hosting multiple services behind one IP — a monitor pairs naturally with a Docker stack, though for true independence the watchdog belongs on its own separate server.

VPS for Grafana + Prometheus server monitoring →

Ready to deploy? Pay with crypto, no KYC — live in about a minute.

Deploy now →

FAQ

Why self-host uptime monitoring instead of a hosted service?

Two reasons. Control and privacy — your monitors, your alert rules, and the list of what you run stay on a server you own, not a third-party dashboard. And independence — a monitor has to live outside the thing it watches. Uptime Kuma on its own small VPS keeps checking (and alerting) even when your main server, or your home connection, is down. A hosted service does that too, but self-hosting keeps it yours and flat-cost.

What plan and resources does Uptime Kuma need?

It's light — a Nano-IP ($8/mo) runs dozens of monitors comfortably. RAM use grows with the number of checks and retained history, so add headroom only if you're monitoring hundreds of endpoints. You want a dedicated IP so the dashboard and public status page are reachable over HTTPS, and so your checks originate from a stable address.

Do I need a dedicated IP and a domain?

For the web dashboard and a public status page, yes — you open https://status.yourdomain.com in a browser, which needs a domain, valid TLS and inbound 443. That's a dedicated-IPv4 plan; NAT plans don't accept inbound web traffic. A reverse proxy (Caddy) gives you automatic HTTPS.

Should the monitor be on the same server as the things it watches?

No — that's the whole point of a separate box. If your monitor runs on the same machine as your app, they go down together and you get no alert. Put Uptime Kuma on its own small VPS (ideally a different region from your main infrastructure) so it's an independent observer that can still reach you when something breaks.

Do you ask for ID or a card?

No. Register with an email, pay in USDC or USDT. No documents, no card, no KYC.

Comments

No comments yet. Be the first.