Cloud, local or private
Put the system where it belongs.
Network access, data requirements and existing infrastructure shape the right deployment approach.
Five paths to consider.
| Approach | Typical starting point | What it means |
|---|---|---|
| 01Direct device control | Small local integrations | Control a compatible device through its local interface. This mode does not receive upstream device messages. |
| 02Software gateway | An existing local server | Run gateway software on the site network and call its device-control interface. |
| 03Hardware gateway | A dedicated on-site unit | Use a gateway appliance to provide local device-control access. |
| 04Platform broker | A broader private deployment | Deploy a platform broker on your infrastructure and connect through its HTTP interface. |
| 05Your own broker | An existing MQTT architecture | Integrate compatible devices with a broker and the MQTT handling maintained by your team. |
Before implementation
Make the operating
requirements explicit.
- Which functions must continue without internet access?
- Where will device events and operational records be handled?
- Who maintains credentials, updates and recovery procedures?
- Does an existing application or broker need to be retained?