Sign in
Edge Gateway

Edge Gateway

Design a gateway on this site, in the Edge Logic Editor, and run it on your own device. This guide takes one data flow at a time, from a field device to each output, and then follows the design from the editor to a running service.

Product page →

What Edge Gateway is

Edge Gateway is two things. On this website, a design: the devices you read, how their values are shaped, and where the data goes, drawn as a flow in the Edge Logic Editor. On your device, a runtime: a single program, no dependencies, that executes that design as a service and keeps running whether or not it can reach this site.

THE SHAPE OF EVERY GATEWAYModbus devicePLC · meter · driveEdge Gatewaythe runtime on your devicepolls the device on its intervaldecodes registers into tags with qualityscales, filters, routes and shapes themOutputMQTT · HTTP · SQL · OPC UA · BACnet · WebSocket · Modbus
Every flow reads a source, passes the values through the runtime's tag engine and route pipeline, and delivers them to one or more outputs. Each output has its own chapter.

The runtime carries 28 source protocols (Modbus TCP/RTU/ASCII, Siemens S7, Allen-Bradley, Mitsubishi, Omron, Beckhoff, OPC UA, DNP3, BACnet/IP, SNMP, M-Bus, DLMS and more), seven outputs, a protocol converter, the editor's transform and logic nodes, store & forward, alarms and its own diagnostics. Protocols & capabilities lists every one, and says which protocols have so far been proven only against simulators.

Signing in and your designs

Press Build Gateway in the header, or open /designs/. Sign in with Google, Microsoft or LinkedIn, or with an email address and a password. Every design you make is stored with your account; nothing is kept in the browser.

  • New design asks for a name and opens the editor on an empty canvas.
  • Open editor returns to a design; Clone copies one, with its current flow as version 1 and the same destination settings; Delete removes it and everything built from it.
  • A design's own page holds validation, destination settings, the trial download, the production package, flow versions and its deployments.

How this guide is arranged

FROM AN IDEA TO A RUNNING GATEWAYDesignEdge Logic EditorValidateeditor · io-tags · runtimeDownloadconsole + design.desInstall & activateon the device, onceRuns as a serviceoffline from then on
  • The Edge Logic Editor: the canvas, the palette, what a source node is and what the transform nodes become.
  • One chapter per output: Modbus to MQTT, HTTP, SQL, OPC UA Server, BACnet/IP and WebSocket, any device to Modbus Server, Modbus RTU/ASCII to Modbus TCP, and OPC UA to MQTT for the other direction. Each shows the flow drawn in the editor, the fields that matter, how to try it against the Modbus Simulator, and the same four steps to a running device.
  • Logic and routing nodes: Condition, Join, Inject, Catch, Expression, Cast, Debounce, Batch, JSON template and Throttle, with what the runtime does for each.
  • Then the device side in full: validating, downloading, installing, activation and the licence, and running.
Use the back and next links at the top and bottom of every page to read the guide in order, or the chapter list on the left to jump to the output you need.
Edge Gateway documentation | Modbus Logic