Self-hostableMIT

Self-Hosted Uptime Kuma

Your own uptime monitoring, fully under your control.

Uptime Kuma is a popular open-source, self-hosted monitoring tool — a privacy-friendly alternative to hosted status services. On Kumo2 you deploy your own Uptime Kuma instance on a dedicated cloud server in one click: we provision the machine and launch it with Docker, so your monitoring data and status pages stay entirely yours.

7-day money-back guarantee

Features

Self-hosted & private

Your checks, incidents, and notification settings live on your own server — no third-party dashboard and no per-monitor pricing.

Monitors HTTP, TCP, ping & DNS

Watch websites, APIs, ports, and DNS records with configurable intervals and retries, plus latency history and uptime percentages.

Status pages & alerts

Publish branded status pages and get notified through 90+ channels — Slack, Telegram, Discord, email, webhooks, and more.

One-click Docker deploy

Kumo provisions a Linux server and starts Uptime Kuma with Docker Compose, on a persistent volume so your data survives restarts and upgrades.

What you can do with it

  • Monitor your production websites and APIs from infrastructure you own.
  • Run a public status page for your product or community.
  • Keep an eye on home-lab services, self-hosted apps, and side projects.

Top articles

Guides and notes for deploying, securing, and operating Uptime Kuma on Kumo2.

System requirements

CPU
1 vCPU
Memory
1 GB
Storage
20 GB
Runtime
Docker Compose
Versions
2, 1
Port
3001

Recommended sizes

Standard

Default

1 vCPU / 1 GB RAM / 20 GB SSD

Comfortably monitors dozens of endpoints — Uptime Kuma stays light.

Resources & documentation

How deployment works

  1. 1

    Pick a plan and a region close to you.

  2. 2

    Choose how you'll sign in and confirm your order.

  3. 3

    Kumo provisions a Linux server and starts the app with Docker — ready in minutes.

Frequently asked questions

What is self-hosted Uptime Kuma?

It's the open-source Uptime Kuma monitoring tool running on a server you own and control, instead of a shared SaaS. You get the full feature set with none of your data leaving your instance.

How do I deploy it on Kumo2?

Pick a plan and region, choose how you'll log in, and click deploy. Kumo provisions the server and launches Uptime Kuma with Docker automatically — it's ready in a few minutes.

Can I use my own domain and HTTPS?

Yes. Point a domain at your server's IP and put Uptime Kuma behind a reverse proxy with TLS, or access it directly on its default port.

What are the system requirements?

Uptime Kuma is lightweight: 1 vCPU, 1 GB of RAM, and 20 GB of disk comfortably monitor dozens of endpoints.

How do I update Uptime Kuma?

Because it runs in Docker, updating means pulling a newer image version and recreating the container; your data persists on its volume.

Ready to deploy your own Uptime Kuma?

Spin it up on a server you control. We handle provisioning and Docker — you keep the keys.

Deploy Uptime Kuma
7-day money-back guarantee

Not happy within 7 days of deploying? Get a full refund — just ask.