// the find
Alice39s/kuma-mieru
A 3rd-party Uptime Kuma monitoring dashboard built on Next.js 16, TypeScript and Recharts.
A third-party status page frontend for Uptime Kuma, replacing its built-in public page with something that actually shows latency charts and looks decent. If you're running Uptime Kuma and hate its status page, this is the drop-in replacement. Next.js 15/16 app that proxies data from your existing Kuma instance.
The multi-instance support via pipe-separated URLs in a single env var is a clean solution for people running multiple Kuma instances. The retry/timeout configuration through env vars (REQUEST_RETRY_MAX, REQUEST_TIMEOUT_MS) is production-practical — the defaults are sane and you can tune without rebuilding. The ALLOW_EMBEDDING env var with per-domain whitelist support is a thoughtful touch for teams that embed status pages in their own dashboards. i18n coverage is real: 9 locales including CJK variants, which matters since the README is primarily Chinese.
The UTC+0 timezone workaround is a leaky abstraction — it pushes config burden onto the user (change Uptime Kuma's display timezone globally) to fix a data modeling problem in Kuma's API that this project doesn't control. Docker support is still 'Beta' despite being a common deployment path. Cloudflare Workers is listed as unsupported with no timeline, which will bite anyone who assumed edge deployment was viable given the Next.js stack. Hard coupling to Uptime Kuma v1 data format means the project will break or need significant work if/when Kuma v2 ships a different API.