Deploy Uptime Kuma on your own server

What you will build

Uptime Kuma is an open-source status monitor for HTTP endpoints, TCP ports, ping checks, and keyword checks. This tutorial starts with Kumo2's one-click self-hosted app flow, then points out the first settings to review after the app is online.

How this tutorial was checked

This tutorial is maintained against Kumo2's current Uptime Kuma app flow: Docker-based provisioning, persistent app storage, the server details page, and the first-run admin setup in Uptime Kuma. It is intended for a new single-server deployment, not for migrating an existing monitor history from another host.

Before you start

You need a Kumo2 account, a payment method, and a domain or subdomain if you want a friendly public URL. You can also test the deployment directly from the server IP first.

For a small personal monitor, start with a modest server size. Add more CPU or memory later if you plan to track many endpoints or keep long histories.

Deploy the app

Open the Uptime Kuma self-hosted app page, choose a region close to the services you monitor, and confirm the order. Kumo2 creates the server, installs the Docker runtime, and starts Uptime Kuma with persistent storage.

When provisioning finishes, open the app URL from the server details page and create the first admin account in Uptime Kuma.

Add your first monitor

Create an HTTP monitor for your main website or API. Use the public URL, set a reasonable interval, and add a short friendly name so the dashboard remains easy to scan.

If you monitor private services, keep those checks on the same private network or restrict access with firewall rules. A monitor should not require opening broad administrative ports to the public internet.

Verify the deployment

After the first monitor is created, wait for at least one successful check and one full interval. Confirm that the dashboard updates, the monitor history is retained after a page refresh, and the server firewall exposes only the ports you intentionally opened.

Review durability

Check that the app data volume is attached and that the server has enough disk for your retention settings. If Uptime Kuma becomes part of an operational workflow, configure notifications early so failures leave the dashboard and reach the right inbox or chat room.

Next steps

• Point a domain at the server once the app is working.
• Add monitors for the services your users notice first.
• Keep the server firewall narrow: web traffic in, administration from trusted locations only.
• Document who owns the monitor list and notification destinations.