Must have
Hard prerequisites
- Linux server running Docker Engine or Node.js >= 18.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).
- Persistent volume for SQLite database storage.
Application hosting
Hosting Uptime Kuma
Lightweight, self-hosted infrastructure and website uptime monitoring tool with customizable public status pages, multi-channel alerting, and ping/HTTP/TCP/DNS checks.
- Min vCPU
- Depends on workload
- Min memory
- Depends on workload
- Min storage
- Depends on workload
Recommended
Documented guidance
- Independent budget VPS separate from your primary application infrastructure.Never host your monitoring system on the same physical server or cluster that it is monitoring.
- Reliable, low-jitter network connectivity with predictable outbound latency.Network blips on the monitoring host cause false positive outage alerts.
Capacity depends on your workload
Extremely resource-efficient. Handles up to 100 monitors checking at 60-second intervals with less than 250 MB RAM consumption using default SQLite backend.
We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.
Deploy with
Supported paths
The host must provide
Runtime
- Docker
- >= 20.10
- SQLite
- Embedded 3.x
Storage
Persistent data
All monitor configurations, response histories, and incident logs are stored inside a single SQLite file at /app/data/kuma.db. Schedule automated daily snapshots of this directory.
Step by step
Quick Docker deployment
-
Create persistent Docker volume
Run docker volume create uptime-kuma to ensure data persists across container updates and host reboots.
Official instructions -
Launch Uptime Kuma container
Execute docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1.
Official instructions -
Configure reverse proxy and initial admin user
Navigate to http://<server-ip>:3001 or set up Nginx/Caddy with WebSocket proxy headers enabled. Complete initial admin registration.
Official instructions
Security
Before you go public
- Enforce HTTPS and WebSocket TLS termination to prevent plaintext credential sniffing.
- Enable 2FA inside the Uptime Kuma settings.
- Do not use internal server root passwords as notification webhook secrets.
Cost
Beyond the server price
- Server cost: Runs comfortably on a $3.50–$5.00/month 1-core / 1 GB VPS (e.g. Hetzner CX22 or Linode Nanode).
- Notification cost: Zero cost when using Telegram, Discord, Slack, or generic webhook integrations.
Matching plans
Plans with published evidence
DigitalOcean
CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB
2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
DigitalOcean
General Purpose Droplet · 2 Dedicated vCPU / 8 GB
2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Hetzner Cloud
Hetzner Cloud CCX53 (Germany and Finland)
32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Hetzner Cloud
Hetzner Cloud CCX63 (Germany and Finland)
48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- Linux server running Docker Engine or Node.js >= 18.This prerequisite has no comparable published plan field.
- Minimum 512 MB RAM (1 GB recommended for 50+ simultaneous monitoring targets).This prerequisite has no comparable published plan field.
- Persistent volume for SQLite database storage.This prerequisite has no comparable published plan field.
Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.