Nezha

Nezha is a self-hosted, lightweight monitoring and operations (O&M) platform for your own servers and websites.

  • Automation
  • Monitoring & Logging
  • Tools & Utilities
Nezha is a self-hosted, lightweight monitoring and operations (O&M) platform for your own servers and websites. It tracks system status, HTTP checks (including SSL certificate changes and expirations), TCP, and Ping, and supports push alerts, scheduled tasks, and a web terminal. Self-hosters and server owners use it as a simple all-in-one dashboard for monitoring, alerting, dynamic DNS (DDNS), file management, and API access.

Platform availability

Available on 2 of 10 platforms

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

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.

83/100 Excellent

Maintained
100last commit 23 days ago
Popular
8010,416 GitHub stars
Easy to install
352 install platforms, install notes
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
10,416
Open issues
57
Last commit
2026-10-29
Latest release
v2.6.1
License
WTFPL
Activity
declining

Checked 4 days ago - source: GitHub (nezhahq/nezha)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Set your panel address, port, and secret In the agent installer, replace NZ_SERVER with your panel address and port, NZ_TLS with on/off for HTTPS, NZ_CLIENT_SECRET with the secret from Nezha, and NZ_UUID with that server’s unique ID. If any of these are wrong or missing, the agent cannot connect to Nezha. source
  • Make sure the agent port is reachable Use the port that the panel is actually listening on and make sure it is not blocked by a firewall. If the agent cannot reach that port, it may run but your server will not appear in the dashboard. source
  • Turn on the agent service After installing, start and enable the Nezha agent service so it runs in the background and restarts after reboots. If you skip this, monitoring can stop after a reboot and your server may look offline. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What kinds of monitoring and maintenance features does Nezha support?

It can monitor system status, HTTP and SSL certificate changes, TCP, and Ping. It also supports push alerts, scheduled tasks, and a web terminal.

Does Nezha include remote access capabilities?

Yes, it is described as a lightweight monitoring server with remote access features.

Can Nezha be used in languages other than English?

Yes, the project supports multiple languages.

What must be configured in the Nezha agent for it to connect to the panel?

Set the panel address, port, NZ_CLIENT_SECRET, NZ_UUID, and NZ_TLS for HTTPS in the agent installer. If any of these values are wrong or missing, the agent cannot connect.

Answers sourced from github.com, nezha.wiki, nezha.wiki, www.reddit.com

Community

Collected 48 days ago - public community threads