Skip to content

Conversation

Raynzler
Copy link

@Raynzler Raynzler commented Oct 1, 2025

Adding Uptime Kuma to the Monitoring section. It's a popular self-hosted monitoring solution with 75k+ GitHub stars that was missing from the list.

  • Modern, actively maintained monitoring tool
  • MIT licensed
  • NodeJS based
  • Clean web UI with mobile support

Thank you for taking the time to work on a PR for Awesome-Sysadmin!

To ensure your PR is dealt with swiftly please check the following:

  • Your additions are Free software
  • Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts).
  • Submit one item per pull request. This eases reviewing and speeds up inclusion.
  • Format your submission as follows, where Demo and Clients are optional.
    Do not add a duplicate Source code link if it is the same as the main link.
    Keep the short description under 80 characters and use sentence case
    for it, even if the project's webpage or readme uses another capitalisation.
    Demo links should only be used for interactive demos, i.e. not video demonstrations.
    - [Name](http://homepage/) - Short description, under 250 characters, sentence case. ([Demo](http://url.to/demo), [Source Code](http://url.of/source/code), [Clients](https://url.to/list/of/related/clients-or-apps)) `License` `Language`
  • Additions are inserted preserving alphabetical order.
  • Additions are not already listed at awesome-selfhosted
  • The Language tag is the main server-side requirement for the software. Don't include frameworks or specific dialects.
  • You have searched the repository for any relevant issues or PRs, including closed ones.
  • Any category you are creating has the minimum requirement of 3 items.
  • Any software project you are adding to the list is actively maintained.
  • The pull request title is informative, unlike "Update README.md".
    Suggested titles: "Add aaa to bbb" for adding software aaa to section bbb,
    "Remove aaa from bbb" for removing, "Fix license for aaa", etc.

Please take some time to answer the following questions as best you can:

  • Why is it awesome?

Uptime Kuma provides a modern, user-friendly alternative to traditional monitoring tools. It offers a clean web UI, real-time updates via websockets, and supports 90+ notification services out of the box. With 25k+ GitHub stars and active development, it's become a go-to solution for many sysadmins looking for lightweight monitoring.

  • Have you used it? For how long?

Yes, It's been a week now.

  • Is this in a personal or professional setup?

Personal yes, I am exploring and working on some issues to fix here in the service.

  • How many devices/users/services/... do you manage with it?

I don't use it for managing prod level stuff, I am an upcoming indie dev.

  • Biggest pros/cons compared to other solutions?

Pros: Extremely easy to set up (single Docker container), intuitive UI, rich notification options, low resource usage, and active community support.
Cons: Less suitable for enterprise-scale deployments compared to solutions like Zabbix, limited historical data analysis features.

  • Any other comments about your use case, things you've found excellent, limitations you've encountered... ?
    The 2FA support and multiple status page options are excellent for client-facing monitoring. The mobile-responsive design makes it easy to check status on the go. Would benefit from more advanced alerting logic, but the simplicity is also its strength for most use cases.

Copy link
Collaborator

@Technetium1 Technetium1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this PR, it would be an excellent addition. Please update the link to https://uptime.kuma.pet/ and add the GitHub link as Source Code before the license.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants