Yet another uptime check tool: u(ptime) + nagi(os) + kuma(Uptime Kuma).
Friendly, self-hosted monitoring: know the moment your websites and servers go down, without the noise.
English · 中文 · हिन्दी · Español · العربية · Français · বাংলা · Português · Русский · Bahasa Indonesia · اردو · Deutsch · 日本語 · Tiếng Việt · 한국어
- Ready in about 30 seconds. Download one file, run it, open your browser.
- One file, nothing else to install. Works on Linux, macOS, Windows and FreeBSD.
- Checks what matters. Websites, servers, ports, ping, DNS, SSL certificates and domain expiry.
- Alerts where you already are. Email, Telegram, Slack, Discord, Feishu, DingTalk, WeCom, webhooks and more.
- One problem, not a flood of alerts. If your own network goes down, Unagikuma notices and doesn't page you for every single monitor.
- Status pages to keep your users in the loop.
- Grows with you. Check from several locations when you need to (preview).
- Easy to switch. Bring your monitors over from Uptime Kuma or Nagios.
- Speaks your language. The interface comes in 15 languages.
1. Download the file for your system from Releases and unpack it.
2. Run it:
./unagikumaOn Windows, run unagikuma.exe.
3. Open http://localhost:8077 in your browser and create your admin account.
4. Click Add monitor, enter a website address, and you're done.
Opening it from another computer? Use
http://<server-address>:8077and enter the Setup token that the program printed when it first started.
docker run -d --name unagikuma -p 8077:8077 -v unagikuma-data:/data ghcr.io/githubflyideas/unagikuma:latestThen open http://localhost:8077. You'll find the Setup token with docker logs unagikuma.
Stop Uptime Kuma, then look first (nothing is changed):
./unagikuma import kuma --dry-run /path/to/uptime-kuma/data/kuma.dbIf it looks right, import:
./unagikuma import kuma /path/to/uptime-kuma/data/kuma.dbThe report lists what was imported, what needs a look and what could not be imported, with what to do. It is also saved in data/import-reports/. Running it again only adds what is new.
Point it at nagios.cfg and look first (nothing is changed):
./unagikuma import nagios --dry-run /etc/nagios4/nagios.cfgIf it looks right, import:
./unagikuma import nagios /etc/nagios4/nagios.cfgThe report lists what was imported, what needs a look and what could not be imported, with what to do. It is also saved in data/import-reports/. Running it again only adds what is new.
On the machine where Unagikuma runs:
./unagikuma reset-password adminType the new password twice (it is not shown). Add --generate to get a random one instead. With Docker:
docker exec -it unagikuma /unagikuma reset-password admin- User manual — everything else, step by step
- Changelog
Apache License 2.0, see LICENSE.

