Analytics & Monitoring512 MB RAM (Starter or Pro)· Port 3001

Deploy Uptime Kuma with Docker Compose

Self-hosted uptime monitoring dashboard with HTTP, TCP, DNS, and Telegram/Discord alerts.

1. Production docker-compose.yml Configuration

Copy this stack definition or deploy directly from your Vexlo Cloud console with automatic Let's Encrypt TLS and persistent volume mounts.

docker-compose.yml
yaml
services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    restart: unless-stopped
    ports:
      - "3001:3001"
    environment:
      - UPTIME_KUMA_PORT=${UPTIME_KUMA_PORT:-3001}
      - TZ=${TZ:-Asia/Kolkata}
    volumes:
      - app_data:/app/data


volumes:
  app_data:

2. Required Environment Variables

VariableDefault / ExampleDescription
UPTIME_KUMA_PORT3001Listening port for Uptime Kuma web dashboard and WebSocket stream.
TZAsia/KolkataTimezone used for incident logs and status page timestamps.

Uptime Kuma Self-Hosting FAQs

How much RAM is required to self-host Uptime Kuma in production?

Uptime Kuma requires a minimum of 512 MB RAM (Starter or Pro). On Vexlo Cloud Pro (₹149/mo via UPI in India or $5/mo globally), you get 2 vCPU, 3 GB RAM, and 2 managed databases—more than enough headroom for production workloads.

How do I expose Uptime Kuma with automatic HTTPS/SSL on Vexlo Cloud?

Deploy the louislam/uptime-kuma:1 container on Vexlo Cloud, set the exposed port to 3001, and attach your custom domain in the Domains tab. Vexlo automatically provisions and renews Let's Encrypt TLS certificates.

How is persistent data backed up for Uptime Kuma?

Mount /app/data to a persistent Docker volume and connect Vexlo Cloud's automated S3 / Cloudflare R2 backup scheduler to snapshot your database daily or weekly.

More 1-Click Docker Templates

View all 25 templates →