{"id":949,"date":"2026-08-22T22:42:49","date_gmt":"2026-08-22T22:42:49","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=949"},"modified":"2026-08-22T22:42:49","modified_gmt":"2026-08-22T22:42:49","slug":"uptime-kuma-vps-monitoring-status-page","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/uptime-kuma-vps-monitoring-status-page\/","title":{"rendered":"Uptime Kuma on a VPS: Self-Hosted Uptime Monitoring, Alerts, and a Status Page for Under 100 MB of RAM"},"content":{"rendered":"\n

External uptime monitors charge per check and store your site’s availability data on someone else’s server. Uptime Kuma is the self-hosted alternative: it runs on your own VPS, supports unlimited monitors, pushes alerts to Telegram, Discord, email, or ntfy, and ships with a public status page. Its entire footprint is under 100 MB of RAM, which means it coexists happily with a web server on the smallest VPS plan. Here is how to set it up properly, wire the notifications, and avoid alert fatigue.<\/p>\n\n\n\n

What you get, and what it costs<\/h2>\n\n\n\n
Resource<\/th>Footprint<\/th><\/tr><\/thead>
RAM<\/td>60\u201390 MB (Docker container)<\/td><\/tr>
Disk<\/td>~150\u2013250 MB (app + SQLite database)<\/td><\/tr>
CPU<\/td>Negligible; one check every 60 s per monitor<\/td><\/tr>
Monitors<\/td>Unlimited (practical limit: thousands)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Compare that with per-check pricing from hosted services: the monitoring stack costs you a slice of a VPS you are probably already renting, and the data stays yours.<\/p>\n\n\n\n

Install with Docker<\/h2>\n\n\n\n

The official container is the smoothest path. Bind it to localhost only \u2014 you will put TLS in front of it in the next step, and the admin UI should never be reachable over plain HTTP:<\/p>\n\n\n\n

mkdir -p \/opt\/uptime-kuma\/data\ndocker run -d --name uptime-kuma \\\n  -p 127.0.0.1:3001:3001 \\\n  -v \/opt\/uptime-kuma\/data:\/app\/data \\\n  --restart=always \\\n  louislam\/uptime-kuma:1<\/code><\/pre>\n\n\n\n
Prefer not to run Docker on your production VPS<\/a>? Uptime Kuma also runs directly with Node.js (npm install<\/code> then node server\/server.js<\/code>), or inside a separate container on a dedicated monitoring box.<\/p>\n\n\n\n
Put it behind HTTPS<\/h2>\n\n\n\n
Front the localhost port with a reverse proxy that terminates TLS, exactly like you would for any internal service. A Caddy or nginx vhost for status.example.com<\/code> with automatic certificates takes five minutes and keeps the admin panel off the wire. Once that is up, create your admin account and set a strong password \u2014 Uptime Kuma holds credentials for your notification channels, so treat it like a production service.<\/p>\n\n\n\n
Monitor types that matter<\/h2>\n\n\n\n