Healthchecksvsmqtt-exporter
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Healthchecks | mqtt-exporter | |
|---|---|---|
| Score | 73/100 | 48/100 |
| Rank in category | #2 of 12 in Uptime Monitoring | #67 of 104 in Monitoring & observability |
| GitHub stars | 10 466 | 168 |
| Stars, last 30 days | +108 | — |
| Stable releases, 12 months | 12 | 6 |
| Latest release | v5.0.3 · 27 Oct 2026 | mqtt-exporter-0.1.4 · 11 May 2026 |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | BSD-3-Clause | MIT |
| Main language | Python | Python |
Which one should you pick?
Healthchecks scores 73/100 against 48/100 for mqtt-exporter, so it is the safer default.
Healthchecks ships more often: 12 stable releases in the past year, against 6 for mqtt-exporter.
If you want the quickest setup, mqtt-exporter is easier to run; Healthchecks needs more configuration.
Healthchecks is growing faster right now (+108 stars in 30 days).
Healthchecks details →mqtt-exporter details →
Swap a project
Keep Healthchecks, compare it with
Keep mqtt-exporter, compare it with