Collect at the site
Read RS485, Modbus, and PLC signals through the network already on site.
Back to solutions
INDUSTRIAL IOT / EDGE-FIRST
Industrial IoT that keeps data close to the operation.
Connect PLCs, sensors, and field devices into an edge layer your team can control, extend, and hand over around the system you already run.
FACTORY DATA PATHLOCAL-FIRSTHANDOVER-READY
INUT / FACTORY DATA PATHLIVE
REFERENCE DATA PATH
01Devices / PLCs
02iNut RS485 or Mesh
03iNut Datalogger / Edge Runtime
04MQTT · REST/JSON · Local API
01 / ARCHITECTURE
Start at the first data point.
iNut does not require a whole-plant replacement. Choose the layer that fits the current site, then expand by point count, protocol, and workflow.
01Devices / PLCs
02iNut RS485 or Mesh
03iNut Datalogger / Edge Runtime
04MQTT · REST/JSON · Local API
05SCADA · App · CRM
02 / WHERE IT FITS
One edge layer for industrial contexts.
Use this page to decide whether the first move is a gateway, a datalogger, or an integration contract.
Keep data local
Store, normalize, and run logic at the edge before sending data elsewhere.
Open the integration path
Expose data to SCADA, apps, CRM, or internal APIs through an agreed contract.
03 / NEXT LAYER
Choose the iNut layer that fits the site.
04 / START FROM THE CURRENT STATE
Discuss the architecture Have a system diagram or PLC cabinet?
Share the current state, point count, and protocols. iNut will help isolate what to keep, what to add, and what to survey.
FAQ / CLARITY BEFORE CONTACT
Questions teams ask before an architecture review.
Does iNut replace the existing SCADA?
Not by default. iNut starts with the missing data and edge layer, then connects to the SCADA or system already in operation.
Where should an industrial IoT project start?
Start with the device diagram, point count, protocols, and receiving system; then choose a gateway, datalogger, or Local API path.