Message Brokers
IoTServa is an MQTT client. It subscribes to and publishes through any standards-compliant MQTT 3.1.1 or MQTT 5 broker, over TLS.
Integrations
Works With What You Already Run
IoTServa connects at the protocol level, so it sits beside your brokers, networks and systems instead of replacing them.
LoRaWAN Networks
Receive uplinks from the network server that manages your gateways, through its MQTT or HTTP integration, and apply a payload decoder per sensor model.
Building Management Systems
Read BACnet controllers directly, or read the Modbus and BACnet gateways that an existing BMS already exposes. Control logic stays in the BMS.
PLCs and Machines
Read PLCs and drives that speak Modbus, and machines that publish MQTT or Sparkplug B, without installing anything on the controller.
Dashboards and Analytics
Pull history over the REST API into the analytics, reporting or dashboard tools your team already uses, or publish live values to a broker they subscribe to.
Notifications and Workflows
Send alert events to email, chat and ticketing tools through webhooks, with escalation when nobody responds.
Integration Questions
Does IoTServa work with my brand of equipment?
IoTServa works at the protocol level, so any device that speaks BACnet, Modbus, KNX, MQTT, LoRaWAN or BLE can be read once it has a device profile. We confirm specific models during the pilot.
Are the third-party names on this page partnerships?
No. They are examples of widely used open or standards-based tools that IoTServa can exchange data with at the protocol level. They are trademarks of their owners.
Name the Systems on Site. We Will Map the Connections.
Tell us which protocols are on site. We will scope a pilot that reads your real devices.