Uptime Kuma Hosting on Your Own VPS
Uptime monitoring and status pages, with unlimited monitors and no per-check billing.
Size a server for Uptime Kuma
Every stop is a real configuration you can deploy. Priced per month and billed monthly, exclusive of 18% GST.
What Uptime Kuma is
Uptime Kuma is a self-hosted uptime monitor. It checks HTTP endpoints, TCP ports, DNS records, ping and certificate expiry on a schedule, and notifies you when something stops responding — with public status pages if you want to publish that.
It is deliberately small. There is no metrics pipeline and no log ingestion; it answers one question, which is whether a thing is responding, and it answers it well. That focus is why it runs happily on a modest server where a full observability stack would not.
One placement point matters more than any specification: a monitor on the same server as the thing it monitors tells you nothing when that server dies. Uptime Kuma belongs on a different machine — ideally a different region — from the systems it watches.
“Uptime Kuma is an easy-to-use self-hosted monitoring tool.”
Why run Uptime Kuma on a VPS
Unlimited monitors, with no per-check or per-monitor pricing.
Put it in a different region from the systems it watches, which is the point of external monitoring.
Notification history and status page data stay on your machine.
Root access to adjust check intervals and retention as the monitor count grows.
Uptime Kuma features
HTTP, TCP, ping, DNS and certificate expiry checks
Notifications to email, Slack, Telegram, webhooks and more
Public status pages on your own domain
Configurable retry and interval per monitor
Maintenance windows that suppress alerts
Response-time history per monitor
Uptime Kuma hosting requirements
The recommended starting point for Uptime Kuma, not a hard floor — size it on the sliders.
| Memory | 2 GB is plenty for a few hundred monitors |
|---|---|
| CPU | 2 vCPU |
| Storage | 40 GB; history is small unless intervals are very tight |
| Operating system | Ubuntu 22.04 LTS or Debian 12 |
| Installs on | Ubuntu 24.04 LTS, Ubuntu 22.04 LTS, Debian 13 (Trixie), Debian 12 Bookworm, AlmaLinux 9, AlmaLinux 8, Rocky Linux 9, Rocky Linux 8 |
| Ready in | About 4 minutes |
| Smallest server | 2 vCPU · 4 GB memory · 20 GB disk |
How deployment works
Uptime Kuma is installed with Node.js and run under a process supervisor, behind TLS on your own domain. Deploy it somewhere other than the infrastructure it monitors — a monitor that dies with its target is not a monitor. A different region is better than a different machine in the same one.
What people run it for
External monitoring
Watch your production servers from somewhere they are not.
Public status page
Publish uptime on your own domain instead of paying for a status service.
Certificate expiry
Catch a certificate before it lapses rather than after.
Internal service checks
Monitor private endpoints over a private network.
Uptime Kuma hosting questions
Related applications
Grafana Hosting Dashboards and alerting over your own metrics, without per-seat or per-metric billing. 
Zabbix Hosting Agent-based infrastructure monitoring with no per-host licence and retention you decide. 
PostHog Hosting Product analytics and session recording with event data that never leaves your server. 
Windmill Hosting Scripts become APIs, workflows and internal UIs — with executions bounded by your server, not a plan. 
Node-RED Hosting Event-driven flows for IoT, MQTT and API glue, on a server with a fixed address. Deploy Uptime Kuma on your own server
Root access, your choice of size, and no container between you and the application.