OpenMQTTGateway vs Homebridge
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
Homebridge
Bring non-HomeKit smart devices into Apple Home
| Feature | OpenMQTTGateway | Homebridge |
|---|---|---|
| Category | Home Automation | Home Automation |
| License | GPL-3.0 | Apache-2.0 |
| Language | C++ | TypeScript |
| Setup difficulty | Medium | Easy |
| Min. RAM | 64 MB | 256 MB |
| Deployment | bare-metal, binary | docker, bare-metal, binary |
| GitHub stars | ★ 4,073 | ★ 25,444 |
| First released | 2016 | 2014 |
| Replaces | SmartThings Hub | Apple HomeKit hubs |
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 Homebridge better?
Homebridge 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 Homebridge free and open-source?
Yes. OpenMQTTGateway is licensed under GPL-3.0 and Homebridge under Apache-2.0. Both can be self-hosted at no software cost.
Can I run OpenMQTTGateway and Homebridge with Docker?
OpenMQTTGateway: check the project docs for container support. Homebridge: yes.