HOLOIN
Book a demo
Menu

Platform · connectivity

How devices reach HOLOIN.

Three ways in, one pipeline. Every protocol below is listed from the product's own report of itself, with the acceptance run that proved it.

HOLOIN · three ways in, one pipeline
Radios, through a server inside the install
  • LoRaWAN sensors
  • NB-IoT (LwM2M)
  • Cellular trackers
Straight to HOLOIN
  • MQTT
  • HTTP
  • Monitoring-tool alerts
  • CoAP
  • OCPP
  • Sparkplug B
Through the Field Agent on your OT network
  • BACnet
  • Modbus
  • OPC UA
  • KNX · beta
  • SNMP
  • SunSpec
  • MTConnect · PLC links
One pipeline · on your serverstored first, then decodedthe Field Agent connects out only
Three ways in. Radio devices reach the server inside the install that speaks their network; anything that can push, pushes straight to HOLOIN; controllers on your OT network are read by the Field Agent, which only ever connects outward. All three land on the same pipeline.

How each kind of device connects.

What connectsWay inStatusProved by
LoRaWAN sensorsThrough a server inside the installliverun 36556513192, 2026-09-29 · run 36943905354, 2026-10-02
NB-IoT (LwM2M)Through a server inside the installliverun 38852071304, 2026-10-16 · run 39419450586, 2026-10-20
Cellular trackersThrough a server inside the installliverun 36556513192, 2026-09-29 · run 36943905354, 2026-10-02
MQTTStraight to HOLOINliverun 36994982003, 2026-10-02
HTTPStraight to HOLOINliverun 36994982003, 2026-10-02
Monitoring-tool alertsStraight to HOLOINliverun 39179177486, 2026-10-19
CoAPStraight to HOLOINliverun 39419450586, 2026-10-20
OCPPStraight to HOLOINliverun 38852071304, 2026-10-16
Sparkplug BStraight to HOLOINliverun 39419450586, 2026-10-20
BACnetThrough the Field Agentliverun 37058180386, 2026-10-02
ModbusThrough the Field Agentliverun 37058180386, 2026-10-02
OPC UAThrough the Field Agentliverun 37058180386, 2026-10-02
KNXThrough the Field Agentbetarun 37058180386, 2026-10-02
SNMPThrough the Field Agentliverun 39179177486, 2026-10-19
SunSpecThrough the Field Agentliverun 38852071304, 2026-10-16
MTConnect · PLC linksThrough the Field Agentin developmentnot yet

Generated from the facts file of the release this site was built from; an item shows as live only once its acceptance run passed.

Through a server inside the install.

The tracker server, the LoRaWAN network server and the NB-IoT server ship in the install as options, switched on only where you choose them. Your devices talk to them through ports your IT opens; they hand every reading to the pipeline.

Straight to HOLOIN.

Anything that can push — an MQTT publish, an HTTP or CoAP post, a Sparkplug edge node, a charger over OCPP, your monitoring’s alerts — sends to the app itself, with a token per source. A field map places any JSON by path.

Through the Field Agent.

Controllers and meters on your OT network — BACnet, Modbus, OPC UA, KNX in beta, SNMP, SunSpec — are read by the Field Agent, which runs beside them and only ever connects outward, to your HOLOIN. The agent opens no listening port.

See it running on your kind of asset.

I run the assets

Fifteen minutes on your kind of asset — a truck, a room, a site, a plant, a depot — and the one list behind all of them. Your devices if you bring their maps.

See it on your kind of asset — 15 min →Get demo access →

I run the servers

The install guide and the API reference are public. Read them before we talk.

Read the install guide →