OpenMQTTGateway vs ntfy
A side-by-side comparison of two self-hosted home automation options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
OpenMQTTGateway
Bridge for RF, IR, BLE, and sensors to MQTT
VS
ntfy
Send push notifications to your phone via simple HTTP
| Feature | OpenMQTTGateway | ntfy |
|---|---|---|
| Category | Home Automation | Home Automation |
| License | GPL-3.0 | Apache-2.0 |
| Language | C++ | Go |
| Setup difficulty | Medium | Easy |
| Min. RAM | 64 MB | 64 MB |
| Deployment | bare-metal, binary | docker, binary |
| GitHub stars | ★ 4,073 | ★ 33,263 |
| First released | 2016 | 2021 |
| Replaces | SmartThings Hub | Pushover, Pushbullet |
Why pick each one
Choose OpenMQTTGateway if…
- Released under the GPL-3.0 license
- Active community (4.1k GitHub stars)
- Written in C++
- Tiny footprint — runs in 64 MB RAM
Frequently asked questions
Is OpenMQTTGateway or ntfy better?
ntfy is the stronger all-round pick: it has both the larger community and the simpler easy setup. Consider OpenMQTTGateway if its specific feature set fits your needs better.
Are OpenMQTTGateway and ntfy free and open-source?
Yes. OpenMQTTGateway is licensed under GPL-3.0 and ntfy under Apache-2.0. Both can be self-hosted at no software cost.
Can I run OpenMQTTGateway and ntfy with Docker?
OpenMQTTGateway: check the project docs for container support. ntfy: yes.