← Directory

FluxMQ

FluxMQ is a lightweight message broker in a single Go binary for home labs and event-driven architectures: MQTT 3.1.1 and 5.0 over TCP and WebSocket, AMQP 1.0…

  • Databases
  • Home Automation
  • Network Services
  • Tools & Utilities
FluxMQ is a lightweight message broker in a single Go binary for home labs and event-driven architectures: MQTT 3.1.1 and 5.0 over TCP and WebSocket, AMQP 1.0 and AMQP 0.9.1, durable queues with consumer groups, and BadgerDB storage. Official image from Abstract Machines; the upstream project calls itself experimental. The defaults work without a config file: MQTT 3.1.1 on 1883, MQTT 5.0 on 1884, MQTT over WebSocket on 8083/8084 (path /mqtt), AMQP 1.0 on 5672, AMQP 0.9.1 on 5682, health on 8081 and the admin API on 8082. Data is kept in the appdata folder. Retained messages need the config.yaml from the README (single-node cluster mode). Without it they are stored but not delivered to new subscribers. FluxMQ has no built-in user/password login: clients connect anonymously unless you add an external auth service. Only publish it to networks you trust. A web dashboard is available as the separate FluxMQ-Dashboard template.

Platform availability

Available on 1 of 9 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)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Docker deployment The Docker deployment guide covers building container images, single-node instances, multi-node clusters, volume management, and networking for FluxMQ. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does FluxMQ need separate coordination software such as ZooKeeper or KRaft?

No. It runs as a single binary with embedded storage and does not require Zookeeper or KRaft.

Are MQTT and AMQP handled by the same broker instance?

MQTT transports share a single broker, while AMQP 0.9.1 and AMQP 1.0 run in independent brokers.

Can browser clients connect to FluxMQ?

Yes. FluxMQ supports MQTT over WebSocket for real-time web applications.

Can FluxMQ talk to constrained IoT devices?

Yes. Its CoAP bridge supports UDP and DTLS for constrained IoT hardware.

How does FluxMQ coordinate a multi-node cluster?

Clustered deployments use gRPC-based cross-node routing with embedded etcd coordination.

Answers sourced from github.com

Community

No community discussions collected yet.