OpenMQTTGateway vs evcc
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
evcc
Solar-aware electric vehicle charging controller
| Feature | OpenMQTTGateway | evcc |
|---|---|---|
| Category | Home Automation | Home Automation |
| License | GPL-3.0 | MIT |
| Language | C++ | Go |
| Setup difficulty | Medium | Medium |
| Min. RAM | 64 MB | 256 MB |
| Deployment | bare-metal, binary | docker, binary |
| GitHub stars | ★ 4,073 | ★ 7,054 |
| First released | 2016 | 2019 |
| Replaces | SmartThings Hub | SmartThings |
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 evcc better?
Neither is universally better. evcc has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are OpenMQTTGateway and evcc free and open-source?
Yes. OpenMQTTGateway is licensed under GPL-3.0 and evcc under MIT. Both can be self-hosted at no software cost.
Can I run OpenMQTTGateway and evcc with Docker?
OpenMQTTGateway: check the project docs for container support. evcc: yes.