ioBroker review 2026: a deep dive into this open-source home and building automation integration platform, its adapters, self-hosting setup and alternatives.
ioBroker is a self-hosted, open-source platform for tying together smart home devices, building automation systems and IoT data sources that would otherwise live in separate, incompatible apps and clouds. Rather than shipping its own hardware, ioBroker runs as software on hardware the user already owns, most commonly a Raspberry Pi, a small home server, or a Docker container, and talks to devices through a large library of community-maintained adapters.
The project grew out of CCU.IO, an earlier tool built for Germany's HomeMatic smart-home ecosystem, and emerged as its own platform around 2014 under the leadership of developer Denis Haev ('Bluefox'), who continues to drive core development today through the small company ioBroker GmbH. Rather than raising venture funding, the project sustains itself through a combination of contract development work, an optional paid cloud add-on, and community contributions.
Because it runs entirely on infrastructure the user controls, ioBroker appeals strongly to privacy-conscious users who want smart home automation without routing device data through a manufacturer's cloud, and to hobbyists who want to combine devices from many different ecosystems -- KNX, Zigbee, Z-Wave, MQTT and more -- into a single automation layer.
At the center of ioBroker is the js-controller, a Node.js process that manages the lifecycle of every installed adapter and routes data between them through a shared object and state database. Adapters exist for well over a thousand devices and services, spanning smart home protocols (Zigbee, Z-Wave, KNX, Homematic), voice assistants (Alexa, Google Home), media systems (Sonos, Philips Hue), and industrial or energy-monitoring protocols (Modbus, OPC-UA, MQTT), which is what lets ioBroker act as a universal translation layer across otherwise siloed ecosystems.
Automation and visualization are handled through companion tools: the JavaScript/Blockly scripting adapter lets users write conditional automation rules (for example, dim the lights when a motion sensor and a light-level sensor both fire), while the VIS module provides a drag-and-drop dashboard builder for creating custom control panels viewable from a browser or mobile device.
Administration happens through a web-based Admin interface for installing adapters, configuring instances, and monitoring logs, and the entire system supports multi-instance and multi-host setups, so power users can spread ioBroker across several machines for redundancy or to isolate resource-heavy adapters.
The ioBroker core (js-controller) and the overwhelming majority of its adapters are free and open source under the MIT license, so a self-hosted installation costs nothing beyond the hardware it runs on. A small number of adapters, particularly ones tied to commercial third-party integrations, require a free license issued by ioBroker GmbH for private use, which is used mainly to gauge adoption rather than to charge users.
For users who don't want to manage their own server, ioBroker GmbH offers ioBroker.pro, a paid hosted/cloud convenience service that handles remote access and backups for a subscription fee. This keeps the underlying platform's cost model close to zero for self-hosters while giving the maintaining company a modest, sustainable revenue stream to fund ongoing development, distinct from a typical SaaS pricing ladder.
Yes, the ioBroker core and the vast majority of its adapters are free and open source under the MIT license. An optional paid ioBroker.pro cloud service is available for users who don't want to self-host.
ioBroker runs on any device that supports Node.js with at least 1GB of RAM, including a Raspberry Pi, Docker container, Linux server, Windows PC or Mac.
ioBroker is maintained by developer Denis Haev ('Bluefox') through ioBroker GmbH, alongside a large community of volunteer adapter contributors.
Both are open-source, self-hosted home automation platforms, but ioBroker is built on Node.js/JavaScript with especially strong support for German building-automation standards like KNX and Homematic, while Home Assistant is Python-based with a larger global community.
Yes, ioBroker has dedicated adapters for Zigbee and Z-Wave, alongside KNX, Homematic, MQTT, Modbus and many other protocols.
Yes, ioBroker includes adapters for Amazon Alexa and Google Home, allowing voice control of connected devices.