kuma-mieru
Kuma Mieru is a third-party Next.js-based dashboard for visualizing Uptime Kuma monitoring data. It replaces Uptime Kuma's built-in status page with interactive charts, real-time updates, and a modern responsive UI.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | Alice39s/kuma-mieru |
| Owner | Alice39s |
| Primary language | TypeScript |
| License | MPL-2.0 — OSI-approved |
| Stars | 787 |
| Forks | 348 |
| Open issues | 5 |
| Latest release | v1.7.4 (2026-06-27) |
| Last updated | 2026-07-02 |
| Source | https://github.com/Alice39s/kuma-mieru |
What kuma-mieru is
Built on Next.js 16, React 19, TypeScript, and Recharts, Kuma Mieru fetches status data from Uptime Kuma's public endpoints and renders interactive latency graphs and real-time status indicators. Deployable via Vercel, Docker, or local Node/Bun runtime.
Get the kuma-mieru source
Clone the repository and explore it locally.
git clone https://github.com/Alice39s/kuma-mieru.gitcd kuma-mieru# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Verify Uptime Kuma instance is accessible from the deployment environment; status pages must be publicly readable.
- Configure UPTIME_KUMA_URLS environment variable correctly; if using legacy mode, set Uptime Kuma's Display Timezone to UTC+0.
- Choose deployment method (Vercel recommended for simplicity; Docker Compose for self-hosted; local for development).
- Test real-time auto-refresh behavior to confirm WebSocket or polling is not blocked by firewall/CDN policies.
- Plan for Bun package manager installation if deploying locally; Docker alleviates this requirement.
When to avoid it — and what to weigh
- Not a Self-Contained Monitoring Solution — Kuma Mieru is a frontend-only dashboard; it requires an existing Uptime Kuma instance and cannot perform monitoring independently.
- Incompatible with Other Monitoring Platforms — Does not support Uptime Robot, Better Stack, or other monitoring data sources—only Uptime Kuma's public status endpoints.
- Timezone Configuration Dependency — Requires manual timezone configuration (UTC+0) in the backend Uptime Kuma instance to avoid time offset issues; does not auto-detect or compensate.
- Docker Deployment Still Beta — Docker support is marked beta; production deployments should consider Vercel or local Node/Bun deployments as more stable.
License & commercial use
Licensed under Mozilla Public License 2.0 (MPL-2.0), a copyleft license requiring derivative works to disclose source and maintain the same license.
MPL-2.0 permits commercial use, but requires source disclosure of modifications and derivative works. Verify with legal counsel before using in proprietary products or closed-source deployments. Unmodified use (e.g., deploying as-is on Vercel) likely acceptable, but any custom extensions trigger disclosure obligations.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
No authentication layer; the dashboard exposes data as public as the underlying Uptime Kuma status page. Consider placing behind a reverse proxy with authentication if sensitive. No security audits, penetration tests, or CVE disclosures mentioned. Dependencies (Next.js, React, Recharts, HeroUI) should be monitored for vulnerabilities via npm/Bun audit. No encryption or secrets management built-in; environment variables passed via deployment platform.
Alternatives to consider
Uptime Kuma Native Status Page
Built-in and requires no separate deployment, but offers less visual interactivity and fewer charting options than Kuma Mieru.
Grafana with Prometheus Uptime Exporter
Provides more powerful dashboarding and alerting, but requires dedicated infrastructure and learning curve; overkill for simple Kuma status aggregation.
UptimeRobot or Better Stack Public Status Pages
Vendor-managed, no deployment needed, but lock-in to proprietary platforms; not compatible with self-hosted Uptime Kuma.
Build on kuma-mieru with DEV.co software developers
Kuma Mieru transforms raw Uptime Kuma data into an interactive, visually rich status page. Deploy in minutes on Vercel or self-host with Docker.
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.
kuma-mieru FAQ
Does Kuma Mieru monitor services itself?
Why do I see time offsets between Kuma Mieru and Uptime Kuma?
Can I use Kuma Mieru with Uptime Robot or Better Stack?
Is Docker deployment production-ready?
Software developers & web developers for hire
DEV.co helps companies turn open-source tools like kuma-mieru 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 observability stack.
Need a Better Uptime Dashboard?
Kuma Mieru transforms raw Uptime Kuma data into an interactive, visually rich status page. Deploy in minutes on Vercel or self-host with Docker.