---
title: "Deploy Uptime Kuma Self-Hosted (Docker)"
description: "Step-by-step guide to self-hosting Uptime Kuma with Docker Compose. "
---

# Deploy Uptime Kuma

A fancy self-hosted monitoring tool.

<div className="deploy-hero">
  <span className="deploy-hero-item">⭐ 55.0k stars</span>
  <span className="deploy-hero-item">📜 MIT</span>
  <span className="deploy-hero-item">🔴 Advanced</span>
  <span className="deploy-hero-item">⏱ ~20 minutes</span>
  
</div>

<div className="mt-8 mb-4">
  <a 
    href="https://m.do.co/c/2ed27757a361" 
    target="_blank" 
    rel="noopener noreferrer"
    className="flex items-center justify-center w-full px-6 py-4 text-lg font-bold text-white transition-all bg-blue-600 rounded-xl hover:bg-blue-700 hover:scale-[1.02] shadow-lg shadow-blue-500/30"
  >
    🚀 Deploy on DigitalOcean ($200 Free Credit)
  </a>
</div>


## What You'll Get

A fully working Uptime Kuma instance running on your server. Your data stays on your hardware — no third-party access, no usage limits, no surprise invoices.

## Prerequisites

- A server with Docker and Docker Compose installed ([setup guide](/quick-start/choosing-a-server))
- A domain name pointed to your server (optional but recommended)
- Basic terminal access (SSH)

## The Config

Create a directory for Uptime Kuma and add this `docker-compose.yml`:

```yaml
# -------------------------------------------------------------------------
# 🚀 Created and distributed by The AltStack
# 🌍 https://thealtstack.com
# -------------------------------------------------------------------------

# Docker Compose for Uptime Kuma
version: '3.8'

services:
  uptime-kuma:
    image: louislam/uptime-kuma:1 # Official image is standard
    container_name: uptime-kuma
    ports:
      - "3001:3001"
    volumes:
      - uptime_kuma_data:/app/data
    networks:
      - uptime_net
    healthcheck:
      test: [ "CMD", "curl", "-f", "http://localhost:3001/" ]
      interval: 30s
      timeout: 10s
      retries: 3
    restart: unless-stopped

networks:
  uptime_net:
    driver: bridge

volumes:
  uptime_kuma_data:
    name: uptime_kuma_data
```

## Let's Ship It

```bash
# Create a directory
mkdir -p /opt/uptime-kuma && cd /opt/uptime-kuma

# Create the docker-compose.yml (paste the config above)
nano docker-compose.yml

# Pull images and start
docker compose up -d

# Watch the logs
docker compose logs -f
```



## Post-Deployment Checklist

- [ ] Service is accessible on the configured port
- [ ] Admin account created (if applicable)
- [ ] Reverse proxy configured ([Caddy guide](/concepts/reverse-proxies))
- [ ] SSL/HTTPS working
- [ ] Backup script set up ([backup guide](/concepts/backups))
- [ ] Uptime monitor added ([Uptime Kuma](/deploy/uptime-kuma))

## The "I Broke It" Section

**Container won't start?**
```bash
docker compose logs uptime-kuma | tail -50
```

**Port already in use?**
```bash
# Find what's using the port
lsof -i :PORT_NUMBER
```

**Need to start fresh?**
```bash
docker compose down -v  # ⚠️ This deletes volumes/data!
docker compose up -d
```

## Going Further

- [Uptime Kuma on AltStack Directory](https://thealtstack.com/alternative-to/uptime-kuma)
- [Uptime Kuma Self-Hosted Guide](https://thealtstack.com/self-hosted/uptime-kuma)
- [Official Documentation](https://uptime.kuma.pet)
- [GitHub Repository](https://github.com/louislam/uptime-kuma)