Architecture

From the field to the enterprise, on a single unit.

EdgeKinect Core runs directly on the gateway. It collects data from LoRaWAN and Modbus devices, stores and visualizes it locally, then forwards it to your SCADA systems, third-party tools, and EdgeKinect Vision — no cloud dependency required.

Self-hosted No cloud dependency Runs on the gateway 6 output protocols

From Field Sensors to Enterprise Systems

EdgeKinect connects remote LoRaWAN sensors directly into enterprise IT, OT, and cloud platforms. Field data is securely ingested, normalized, and streamed into SCADA, SolarWinds, and industrial networks using SNMP, Modbus, DNP3, Sparkplug, MQTT, and HTTP APIs — while simultaneously delivering telemetry to AWS SNS, Azure Service Bus, InfluxDB, and analytics and visualization platforms.

System Overview

The whole system, end to end.

Devices in the field feed a single gateway running EdgeKinect Core, which forwards their data to every system downstream.

EdgeKinect system overview — LoRa and Modbus devices feed a gateway running EdgeKinect Core, which forwards data to SCADA systems, third-party tools, EdgeKinect Vision, and clients.
01

Collect

LoRaWAN sensors transmit wirelessly over the unlicensed 900 MHz band; wired Modbus devices connect directly. The gateway gathers it all in the field.

LoRaWANModbus
02

Process locally

EdgeKinect Core parses packets, stores them in a time-series database, monitors connectivity, and brokers data over MQTT — all on the gateway itself.

Time-seriesConnectivityMQTT broker
03

Distribute

The same normalized stream is pushed out concurrently to every system you run — over industrial protocols or HTTP, with no cloud dependency.

SCADAThird-partyVisionClients
Data Flow

How data moves through Core.

A single ingestion path feeds an internal broker that fans out to outbound connectors — Modbus, DNP3, SNMP and Sparkplug — while the same data is written to the time-series store.

EdgeKinect Core internal data flow — network server and handlers feed a data consumer and broker, which fans out to connectors for Modbus, SNMP, DNP3 and Sparkplug, plus a time-series store.
Why it's built this way

Engineered for the edge.

Self-contained

The full pipeline — ingest, store, visualize, forward — runs on a single gateway unit.

No cloud dependency

Everything operates on your local network. Cloud is optional, never required.

Concurrent protocols

Run many outbound connectors at once, even of different protocols, simultaneously.

Field-ready

Connectivity monitoring, QR onboarding and location-aware devices, built in.

Port Reference

Default ports by integration.

DNP3

SCADA outstation

20000

Modbus

SCADA / PLC

5030

SNMP

IT monitoring

1620

Sparkplug

MQTT · plain / TLS

1883 / 8883

HTTP / HTTPS

Clients & Vision

80 / 443

See the architecture running on your hardware.