Ingest From Any Broker
Subscribe with topic filters and wildcards, then map each topic and JSON path to a tag with a unit.
Subscribe to any broker, publish normalized data back out, and keep topics, QoS and retained state under control.

MQTT is a lightweight publish and subscribe protocol. Devices send messages to named topics on a broker, and anything subscribed to a topic receives them. MQTT defines the transport, not the payload, so two vendors can both speak MQTT and still send incompatible data. IoTServa treats a broker as both a source and a destination.
site.factory.line-2.oven-temp
182.4°C
Subscribe with topic filters and wildcards, then map each topic and JSON path to a tag with a unit.
Send clean, consistently named values back out to your own broker or a cloud broker, with the QoS you choose.
Connect over TLS with client certificates or credentials, and keep secrets out of project files.
Read Sparkplug B birth and data messages so metrics arrive with their types and units.
Choose QoS deliberately. QoS 0 can drop messages, QoS 2 costs more than most telemetry needs.
Retained messages make a dashboard show stale data as if it were live unless you track message age.
Agree one topic naming scheme per site before devices multiply.
It connects to the broker you already run, or to one you choose. A broker can also be part of an on-premise deployment.
Yes. Every normalized tag can be published to a broker with a topic pattern you define.
Tell us the make and model of what is on site. We will scope a pilot against your real equipment.