AutoKuma

AutoKuma is a utility that automates the creation of Uptime Kuma monitors based on Docker container labels.

  • Monitoring & Logging
  • Other
  • Productivity
  • Tools & Utilities
AutoKuma is a utility that automates the creation of Uptime Kuma monitors based on Docker container labels. With AutoKuma, you can eliminate the need for manual monitor creation in the Uptime Kuma UI.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

62/100 Good

Maintained
67last commit 156 days ago
Popular
59930 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
84no serious findings, 1 minor, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
930
Open issues
18
Last commit
2026-06-18
Latest release
v2.0.0
License
MIT
Activity
stale

Checked 8 days ago - source: GitHub (BigBoot/AutoKuma)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set AutoKuma's Kuma login details Create AutoKuma's TOML (plain-text settings) file with your Uptime Kuma web address, username, and password. Keep this file safe and correct, because without valid login details AutoKuma cannot sync your monitors and notifications. source
  • Point Docker monitoring at the right socket If you enable Docker monitoring, set the Docker URL to the correct Docker socket (the local access point Docker uses), such as /var/run/docker.sock, or to a remote Docker host. If the path is wrong, AutoKuma will not be able to see or sync your containers. source
  • Escape @/ path values when needed If a setting is supposed to be a literal string that starts with @/, use the @@/ prefix instead. Otherwise AutoKuma treats it as a file path, which can cause the wrong value to be loaded. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What labels should I add to a Docker container so AutoKuma creates a monitor?

Add labels using the label prefix, a unique monitor identifier, the monitor type, and the property to set. For example, kuma.my-app.http.name and kuma.my-app.http.url create an HTTP monitor in Uptime Kuma.

What minimum configuration does AutoKuma need to sync with Uptime Kuma?

It needs the Uptime Kuma URL, username, and password. The docs show these as AUTOKUMA__KUMA__URL, AUTOKUMA__KUMA__USERNAME, and AUTOKUMA__KUMA__PASSWORD, or in a TOML settings file.

Can AutoKuma create monitors from anything other than Docker labels?

It also supports monitors from JSON or TOML files. Docker Swarm and Kubernetes support are available on an as-is basis because the author is not currently running those setups.

How do I configure a literal value that starts with @/ ?

Use the @@/ prefix so AutoKuma treats the value as a literal string instead of a file path.

Answers sourced from github.com, github.com

Community

Collected 53 days ago - public community threads