uptime-kuma
Uptime Kuma is a self-hosted monitoring dashboard that tracks uptime for HTTP, TCP, DNS, WebSocket, and other services with a responsive web UI. It sends alerts via 90+ notification channels (Telegram, Discord, Slack, email, etc.) and runs easily on Docker or Node.js.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | louislam/uptime-kuma |
| Owner | louislam |
| Primary language | JavaScript |
| License | MIT — OSI-approved |
| Stars | 88.9k |
| Forks | 8.1k |
| Open issues | 764 |
| Latest release | 2.4.0 (2026-05-31) |
| Last updated | 2026-07-08 |
| Source | https://github.com/louislam/uptime-kuma |
What uptime-kuma is
JavaScript/Node.js application using Vue 3, Vite, Bootstrap 5, and WebSocket for real-time status updates. Stores monitoring data locally; supports 20-second check intervals, certificate inspection, proxy/2FA, and multi-language support. Deployable via Docker or PM2.
Get the uptime-kuma source
Clone the repository and explore it locally.
git clone https://github.com/louislam/uptime-kuma.gitcd uptime-kuma# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Deploy via Docker Compose (recommended) or Node.js 20.4+ with PM2; ensure local volume mount (NFS not supported) for persistent data.
- Configure reverse proxy if exposing beyond localhost; 2FA and optional authentication available, but review security requirements before internet-facing deployment.
- Plan notification channel setup (email SMTP config, Telegram bot tokens, Discord webhooks, etc.); 90+ integrations available but each requires separate credential management.
- Monitor Kuma's own uptime and data durability; local SQLite can be a bottleneck under very high check frequency or alert volume.
- Test multi-language and status page domain mapping early if customer-facing; supports 20-second check intervals but CPU/network impact of many checks should be load-tested.
When to avoid it — and what to weigh
- Require enterprise-grade SLA and dedicated support — This is community-driven open source; no SLAs, vendor support, or commercial support contracts are available. Author explicitly requests no email support.
- Need deep infrastructure or network monitoring — Uptime Kuma focuses on endpoint/service availability checks. It does not provide CPU profiling, memory analysis, network packet inspection, or infrastructure-level metrics (use Prometheus/Grafana instead).
- Cannot host your own infrastructure or need fully managed SaaS — This is self-hosted only; you must manage servers, backups, updates, and uptime of Kuma itself. No cloud-hosted managed version is offered.
- Require complex data retention or compliance archival — Local SQLite/database storage; no built-in support for long-term data export, compliance archival, or multi-region redundancy. Scaling to very high check volumes may require custom work.
License & commercial use
MIT License. Permissive, OSI-approved; allows commercial use, modification, and distribution under MIT terms.
MIT License permits commercial use without royalties or vendor approval. However, no commercial support, SLAs, or liability/warranty are offered by the author. Deploying internally is straightforward; redistributing or embedding requires MIT attribution. Evaluate your tolerance for community-only support.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
Local data storage; no built-in encryption at rest described. SMTP, API keys, and notification credentials stored locally. 2FA available but optional. No audit logging or role-based access control noted. Running on localhost by default safe; internet-facing deployment requires reverse proxy with TLS, firewall rules, and credential rotation discipline. No security audit or CVE history visible in data.
Alternatives to consider
Statping (unmaintained)
Author cited instability and lack of maintenance as reason for creating Uptime Kuma; Statping is now legacy.
Uptime Robot (SaaS)
Commercial cloud monitoring service; no self-hosting required, vendor support included, but ongoing subscription costs and external data dependency.
Prometheus + Grafana + Alertmanager
Enterprise-grade metrics, graphing, and alerting; steeper setup but richer observability, clustering, and data retention; better for large-scale infrastructure.
Build on uptime-kuma with DEV.co software developers
Uptime Kuma is production-ready for small-to-medium teams. Evaluate whether you can host and maintain it yourself, and ensure self-hosted support model fits your compliance needs.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
uptime-kuma FAQ
Can I use Uptime Kuma with a cloud provider like AWS, Azure, or DigitalOcean?
What monitoring intervals are available?
Does Uptime Kuma replace infrastructure monitoring (CPU, disk, memory)?
Is there a managed/hosted version of Uptime Kuma?
Custom software development services
DEV.co helps companies turn open-source tools like uptime-kuma into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source devops stack.
Ready to self-host uptime monitoring?
Uptime Kuma is production-ready for small-to-medium teams. Evaluate whether you can host and maintain it yourself, and ensure self-hosted support model fits your compliance needs.