How To Deploy Uptime Kuma With One Click

Uptime Kuma is an open source monitoring tool that you can install on your VPS via Docker. Uptime Kuma will help you monitor your website and send alerts when it is down. Now at version 2.4.0, Uptime Kuma has seen massive improvements since its v1 days — including a revamped notification system, new monitor types, Globalping DNS integration, collapsible status page groups, and much more. In this tutorial, we will see how we can install it via Coolify with just 1 click.

If you don’t know, Coolify is a self-hosted Heroku or Netlify alternative that also allows you to deploy various Docker apps. For more details you can check out: Coolify Install A Free Heroku and Netlify Self-Hosted Alternative where we go into more detail.

1. Deploy A VPS server

To host Uptime Kume in a Docker container you need a VPS server, there are a lot of services that can help you with this, the most known are DigitalOcean, Vultr, Hetzner, Hostinger, I also wrote an article and made a video with the benchmarks here: DigitalOcean vs Vultr vs Hetzner you can check it out.

In this tutorial, we are going to use Hetzner for this where we have the VPS created and we can ssh to it to have Coolify installed and then deploy Uptime Kuma.

DigitalOcean $100 Free Vultr $100 Free Hetzner €⁠20 Free Hostinger VPS

2. Installing Coolify

Coolify can be installed with a simple command, you can also check my tutorial for complete steps including the SSL certificate: Coolify Install

We will install Coolify on a Ubuntu server (22.04 or 24.04 LTS recommended). To do this, you just need to SSH to the VPS server and run the following command:

wget -q https://get.coollabs.io/coolify/install.sh \
-O install.sh; sudo bash ./install.sh

If you are interested to see some free cool open source self hosted apps you can check toolhunt.net self hosted section.

If you are interested in how to monitor your CPU and have an automatic email sent when the load is too high, you should have a look at Monitor CPU Usage and Send Email Alerts in Linux

🎥 Uptime Kuma Video with Deployment

3. Deploy the Uptime Kuma service with Coolify

3.1 Point Domain or Subdomain to VPS

We need a domain or subdomain that we can use to access Uptime Kuma, in this tutorial we are going to use CloudFlare and point a subdomain to the VPS server where we have Coolify installed. We will not be using the CloudFlare proxy and will leave it disabled. All you need to do is add an A record and point it to the server IP.

3.2 Create a service

You need to go to Create New Resource and select Service. From there select the UptimeKuma service as shown in the images below:

3.3 Configure Coolify Uptime Kuma

The next thing on the list is to configure the Coolify service, in there you need to add the below:

• Name - here you add the name of your deployment
• Version / Tag - you choose the Uptime Kuma version you want to install
• URL (FQDN) - you add the domain or sudomain that you want to use

After what needs to be done is to hit Save and Deploy button.

3.4 Access Uptime Kuma

After deploy is finished you should go and access Uptime Kuma dashboard with the URL you have added in the configs. The first time you will be prompted to create a user and a password.

After you create the account you can add your website that needs to be monitored and configure the notifications. The configs will be stored on the disks with docker volums and in case you redeploy it you will not lose any data.

What’s New in Uptime Kuma v2.x

Uptime Kuma has evolved significantly since v1. If you’re upgrading or deploying fresh, here are the highlights from the v2.x series:

v2.0 — Major Release (October 2024)

The big rewrite with breaking changes. Key improvements:

• Better performance — completely rewritten backend for faster monitoring
• New notification providers: Nextcloud Talk, Brevo, Evolution API
• Proxy support for notifications via environment variable
• Improved mobile UI — buttons no longer go off-screen on small devices
• 2FA autofocus — smoother two-factor authentication login
• Migration guide available on the Uptime Kuma Wiki

v2.1 — Globalping & Custom Templates (February 2025)

• Globalping DNS support — monitor DNS resolution from distributed probes worldwide
• New providers: Jira Service Management, Google Sheets, Teltonika SMS gateway
• Custom message templates for Discord and ntfy notifications
• Tags in Teams notifications
• Bavarian German language support

v2.2 — WhatsApp & Structured Logging (March 2025)

• WhatsApp (360Messenger) notification provider
• Signal templating — customize your Signal notification messages
• SOCKS proxy for notifications — route alerts through a SOCKS proxy
• Fluxer notification provider
• Structured JSON logging for better log aggregation

v2.3 — WebSocket & OracleDB (May 2025)

• WebSocket monitor improvements — now supports authentication
• OracleDB monitor — monitor Oracle database connectivity
• New providers: Telnyx messaging, VK notifications, MAX messenger
• Collapsible groups on status pages — organize monitors into expandable sections
• SQLite busy_timeout fix — resolves SQLITE_BUSY errors on low-power devices

v2.4 — Latest (May 2026)

• VKTeams bot notification provider
• Incidents in RSS — subscribe to incident updates via RSS feed
• EgoSMS for Uganda SMS notifications
• Bearer token support for WebSocket upgrade monitors
• LiquidJS security fix for notification templates

Conclusions

This is how you can easily deploy Uptime Kuma with the help of Coolify. The config has everything that it needs and you can access it securely with an SSL certificate. With v2.x, Uptime Kuma has grown from a simple uptime monitor into a full-featured monitoring platform with dozens of notification providers, database monitors, DNS probing via Globalping, and a polished status page system. Whether you’re monitoring a single blog or an entire infrastructure, Uptime Kuma covers you.