ioBroker is a Node.js-based IoT integration platform that connects smart home devices through a library of community-built adapters covering Zigbee, Z-Wave, MQTT, KNX, Modbus, and hundreds of brand-specific APIs. The platform runs locally on any hardware that supports Node.js and uses an in-memory database to exchange state and events between adapters in real time. It has a particularly large following in German-speaking countries, where its forum and documentation are especially active.
ioBroker
iobroker.net
Our take
ioBroker’s adapter ecosystem is one of its strongest arguments: where some platforms require generic MQTT bridges, ioBroker often has a native adapter that handles quirks specific to a given device family. The JavaScript/Node.js foundation also makes writing custom adapters accessible to developers familiar with that stack. The honest catch is that the management UI and initial setup feel less polished than Home Assistant’s current experience, and the distributed adapter architecture means more moving parts to keep updated. It is the best choice for integrators who want to script custom logic in JavaScript or who need coverage for device protocols that Home Assistant handles poorly; for general home automation newcomers, there are friendlier starting points.
GitHub at a glance
ioBroker/ioBroker
Stars
1,371
Last commit
18d ago
healthy
License
MIT
Latest release
2026-06-03-2
18d ago
Listed in
ioBroker alternatives
Home Assistant Local-first, open-source home automation hub with thousands of device integrations and no mandatory cloud.
openHAB Vendor-neutral, Java-based home automation platform with local control and a large binding ecosystem.
Domoticz Lightweight open-source home automation system that runs well on low-power hardware like a Raspberry Pi.
HomeKit Apple's smart home framework. End-to-end encrypted home data, on-device camera processing.
ioBroker license, in plain English
MIT Permissive
Do almost anything: use, change, and ship it, even inside closed-source products. The only condition is keeping the copyright notice.
Permits
- Commercial use
- Modification
- Distribution
- Private use
Requires
- License and copyright notice
Does not provide
- Liability cover
- Warranty
Why it matters: Permissive licensing lets anyone reuse this, including inside closed products. That is freedom to build on, but no guarantee that downstream copies stay open.
Plain-language summary of the project's license, not legal advice. Read the full text for the exact terms.