LavinMQ
LavinMQ is a lightweight, high-performance message queue and streaming server implementing the AMQP 0-9-1 and MQTT protocols.
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- 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.
75/100 Good
- Maintained
- 100last commit 16 days ago
- Popular
- 601,032 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
- Security check
- 95no serious findings, CI, tests
Based on 4 of 5 factors.
- GitHub stars
- 1,032
- Open issues
- 243
- Last commit
- 2026-11-05
- Latest release
- v2.10.4
- License
- Apache-2.0
- Activity
- rising
Checked 16 days ago - source: GitHub (cloudamqp/lavinmq)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Open ports 5672 and 15672 In the Docker Compose file, keep the mapped ports 5672 (the AMQP message port your apps use) and 15672 (the web console port) before starting. Without these mappings, your apps cannot reach LavinMQ and you cannot open the browser admin UI. source
- Give LavinMQ a data folder When starting LavinMQ, use the data directory flag (for example `lavinmq -D /var/lib/lavinmq`) and make sure that folder exists and is writable. If you skip it or point it somewhere wrong, LavinMQ may fail to start or your queues and settings may not be saved between restarts. source
- Test with the default guest account For a quick first connection, point your client to `localhost:5672` using the examples' default `guest`/`guest` credentials. This confirms AMQP is reachable before you add real app accounts, but avoid exposing that default account beyond local testing. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which ports should I expose for LavinMQ in Docker Compose?
Expose 5672 for AMQP and 15672 for the web console. Without these mappings, apps cannot reach LavinMQ and you cannot open the browser admin UI.
Can I use the default guest account for my first connection?
For a quick first connection, point your client to localhost:5672 using guest/guest. Avoid exposing that default account beyond local testing.
How do I make queues and settings persist across restarts?
Start LavinMQ with a data directory flag such as -D /var/lib/lavinmq and make sure that folder exists and is writable. If you skip it or point it somewhere wrong, LavinMQ may fail to start or your queues and settings may not be saved.
Is LavinMQ described as a RabbitMQ-compatible broker?
A Reddit discussion describes LavinMQ as a RabbitMQ-compatible broker written by CloudAMQP.
Answers sourced from lavinmq.com, lavinmq.com, www.reddit.com
Community
Collected 48 days ago - public community threads