Deploy Uptime Kuma, a self-hosted monitoring tool, on NABHCLOUD App Hosting in one click, with HTTPS, your domain and GST billing from Noida.
Uptime Kuma works as a self-hosted monitoring tool. It runs scheduled checks against your websites, APIs, open ports and certificates, sends alerts through dozens of channels, and can publish status pages for visitors to see.
Deploying Uptime Kuma needs the Starter plan or above; current plans and prices are shown on this page, charged before GST. The setup comes with HTTPS enabled, support for your own domain, and a proper GST invoice, running from our data centre in Noida. View our App Hosting plans
The install process brings Uptime Kuma online over HTTPS. On your first visit you create the admin login, and from there you can begin adding monitors and configuring alert channels.
Uptime Kuma is a self-managed monitoring application built with Node.js and released under the MIT licence. It listens on port 3001. Monitors can watch many kinds of target: an HTTPS address, a DNS entry, a TCP port, matching text on a webpage, as well as a running Docker container. Each one is checked on a timer, every 60 seconds by default unless you set it differently. Should a check fail, you are notified through Telegram, Discord, Slack, email, a webhook, or any of several other channels it supports.
All monitoring history is kept in a SQLite file named kuma.db, stored inside /app/data. That single folder holds both your settings and your historical data, so back it up from time to time. A push-style monitor is also available: an external cron job calls a URL at set intervals, and if that call does not arrive, Uptime Kuma raises an alert — useful for keeping an eye on backups or scheduled jobs.
One limitation is worth noting. If a monitor runs on the very server it is observing, it cannot warn you when that server goes offline, since the alert itself depends on the server being up. Point such monitors at infrastructure hosted elsewhere, or spin up a compact secondary instance with another provider to keep an eye on this one. Status pages can still be served from your own domain.
| Workload | Plan | Note |
|---|---|---|
| A few dozen monitors or fewer, each checked every 60 seconds | Starter | Starter plan has comfortable headroom for this. |
| Hundreds of monitors, or intervals shorter than usual | Pro | Each check uses a small amount of resources; many running together need extra CPU and memory headroom. |
The Starter plan provides 1 vCPU, 1 GB of memory, 20 GB of storage and space for up to 2 apps. That gives enough headroom to run Uptime Kuma alongside your existing application on one machine. It is billed monthly, with pricing before 18% GST; current plans and prices are shown on this page.
Install Uptime Kuma
Yes, it can check almost anything reachable from the internet, such as web addresses, DNS records, open ports and more.
It is possible, but if that server fails, the alert has no way to go out. Make sure at least one monitor runs on a separate server.
Back up the /app/data directory; it holds the kuma.db file with all your data.
By default, every 60 seconds. You can shorten this, but checking too often adds load to whatever you are monitoring.
Select an application from the catalogue, decide which app server should host it, then click Install. The app appears at its own HTTPS address right away. Any passwords it needs are generated automatically, shown to you once, and saved for later viewing. The whole process finishes within a minute or two.
Tell us what you plan to run and we will suggest the right setup.