MQTT

MQTT is a lightweight publish/subscribe message broker for Internet of Things (IoT) and home-automation devices, allowing many clients to exchange small…

  • Databases
  • Home Automation
  • Other
  • Tools & Utilities
MQTT is a lightweight publish/subscribe message broker for Internet of Things (IoT) and home-automation devices, allowing many clients to exchange small messages efficiently over constrained networks.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • 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.

63/100 Good

Maintained
79last commit 14 days ago
Popular
3450 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
100256 MB minimum RAM
Security check
60no serious findings, 22 minor, CI

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

GitHub stars
50
Open issues
1
Last commit
2026-11-07
Latest release
v3.0.0
License
MIT
Activity
rising

Checked 12 days ago - source: GitHub (ditchoom/mqtt)

Resources & Compatibility

Minimum requirements: 256 MB RAM, 1 CPU core(s), 100 MB disk. ARM (e.g. Raspberry Pi) is not supported.

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

First-install notes

  • Fill in connection details before starting Set the broker host (its address), port, a unique client ID (the name the broker uses for your app), and a keep-alive heartbeat (a periodic alive signal). Without these, the client cannot connect or stay connected, so publishing and subscribing will not work. source
  • Allow plain MQTT port 1883 Plain (unencrypted) TCP MQTT commonly uses port 1883, so allow that port between your app and the broker if your firewall or network blocks it. If the port is closed, the client will time out or fail to connect even when the broker is running. source
  • Wait for pending messages when stopping When you stop the MQTT client, use the drain shutdown option so it waits for pending QoS 1/2 (delivery-confirmation) messages to be acknowledged. Without that, the app can exit before the broker confirms delivery, so some messages may be lost. source

Fetched 37 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which MQTT protocol versions does the broker implement?

The broker implements MQTT 5.0, 3.1.1, and 3.1.

What command line client tools are provided by the broker project?

It provides a C library and the mosquitto_pub and mosquitto_sub command line MQTT clients.

Which testing modes can be tried against the Mosquitto test server?

Plain MQTT, MQTT over TLS, MQTT over TLS with a client certificate, WebSockets, and WebSockets with TLS are listed.

What common MQTT gateway failures should be checked during troubleshooting?

Common failure points include TLS certificate issues, topic mismatches, broker connectivity problems, and DNS errors.

What responsibility does self-hosting an MQTT broker place on the operator?

The operator is responsible for installation and maintenance of the hardware and software. This is described as the likely main choice for local MQTT applications and as ideal for testing or learning.

Answers sourced from www.steves-internet-guide.com, docs.chipkin.com, mosquitto.org

Community

Collected 8 days ago - public community threads