Sign in
Edge Gateway

Build Edge Software Visually

Stay away from expensive IoT edge gateways. Customize your edge logic online in the Edge Logic Editor, then run it on the device you prefer: an industrial PC, a Raspberry Pi or any Linux or Windows box on the plant floor.

Create Gateway ProjectHow Gateway Works
The Edge Logic Editor. A Modbus source node named Main Meter, polling every second, is wired across the canvas to an MQTT out node publishing platform telemetry. The node palette on the left lists messaging and PLC drivers.
The Edge Logic Editor: a source on the canvas, wired to an output, with the node palette on the left.

A gateway is a flow: a source, what happens to the values, and where they go.

Workflow

Create → Build → Deploy

Step 1

Create

Create a Gateway project in Modbus Logic Cloud. Nothing needs to be installed, and no device needs to be reachable.

Step 2

Build

Use the Edge Logic Editor to add a device, define its tags, shape the values and route them to a destination.

Step 3

Deploy

Download the trial zip for Windows or Linux (.deb for Debian, Ubuntu and Raspberry Pi OS) and run the Edge Gateway Console on the device: the first time it activates the design and installs the Edge Runtime as a service; every time after, it is the console that shows what the gateway is doing and what to check.

Edge deployment

Designed in the Cloud. Runs at the Edge.

Modbus Logic Cloud is where the gateway is designed and versioned. The Edge Runtime is what executes it, on your hardware, on your network.

  • 24×7 local operation
    The runtime runs as a Windows Service, a systemd unit or a container. It starts with the machine and keeps its configuration.
  • Local device connectivity
    Modbus connections are made on the plant network, at full poll rate, without a round trip to anything.
  • Store & Forward
    A bounded on-disk buffer holds data while a destination is unreachable and replays it in order.
  • Offline operation
    The runtime does not need Modbus Logic Cloud to run. A cloud or Internet outage does not stop the gateway.
  • Protocol conversion
    Modbus in; MQTT, REST, SQL, OPC UA, BACnet/IP or WebSocket out.
Field devices stay where they are. The runtime opens the connection to your PLC locally and the connection to your broker or API outbound. Nothing needs an inbound firewall rule, and no PLC is exposed to the Internet.

Windows x64

Runs in the foreground or as a Windows Service.

Linux x64

Foreground or a systemd unit.

Linux ARM64

For edge computers and industrial PCs on ARM.

Docker

A container image with a mounted data volume.

Trial and licensing

Build first. Test it at the plant. License when ready.

The commercial unit is a production deployment licence, not a download. You can create projects and build gateways before you pay for anything.

Building is free

Create projects, use the Edge Logic Editor and validate your configuration without a licence.

Trial on real hardware

A validated project downloads as a trial package using the same production runtime binary, so what you test is what you deploy.

Licence the deployment

A production licence activates a deployment. Re-downloading the same licensed deployment for a reinstall or an update is not another purchase.

How licensing works →

Data Transformers

Common integrations

Modbus to MQTT

Publish Modbus registers to an MQTT broker as engineering values.

Modbus to REST API

POST Modbus values to an HTTP endpoint.

Modbus to OPC UA

Expose Modbus devices as an OPC UA server.

Modbus to BACnet/IP

Present Modbus devices as a BACnet/IP device to a BMS.

Energy meter to MQTT

Get metering data out of Modbus meters and into an energy platform.

PLC to cloud

Move PLC data to a cloud application without exposing the PLC.

Industrial device to REST API

Give any supported industrial device an HTTP interface.

Siemens S7 to MQTT

Siemens S7 data to an MQTT broker.

EtherNet/IP to MQTT

Allen-Bradley CIP / EtherNet/IP data to an MQTT broker.

Modbus to SQL database

Modbus registers as rows in PostgreSQL, MySQL / MariaDB, SQL Server or SQLite.

Modbus to WebSocket dashboard

Live values for a browser dashboard or an application, straight from the gateway.

Modbus RTU to TCP converter

A serial Modbus bus published on a TCP or UDP socket for an Ethernet-only master.

Any device to Modbus

Tags from S7, EtherNet/IP, a meter, anything the gateway reads, served as Modbus registers.

OPC UA to MQTT

Variables from any OPC UA server to an MQTT broker, an API or a database.

Mitsubishi MELSEC to MQTT

Mitsubishi MELSEC MC protocol data to an MQTT broker.

Omron FINS to MQTT

Omron CJ, CS, CP, NJ and NX data over FINS to an MQTT broker.

Beckhoff TwinCAT to MQTT

TwinCAT variables over ADS to an MQTT broker.

DNP3 to MQTT

DNP3 outstation points to an MQTT broker.

BACnet to MQTT

BACnet/IP objects from building equipment to an MQTT broker.

SNMP to MQTT

OIDs from switches, UPSs and infrastructure equipment to an MQTT broker.

Smart meter (M-Bus, DLMS) to MQTT

Wired M-Bus and DLMS/COSEM meters to an MQTT broker.

MTConnect to MQTT

Machine-tool data items from an MTConnect agent to an MQTT broker.

Designed today, deployed later

These protocols are in the Edge Logic Editor, so the gateway can be designed and validated now. The current Edge Runtime does not deploy them yet, and a build that uses them is refused rather than producing a package that will not run.

Create the project in the cloud. Build it visually. Deploy it at the edge.

Start a project and open the Edge Logic Editor. You do not need a device in front of you, and you do not need to install anything to begin.

Create Gateway ProjectRead the documentation
Edge Gateway | Modbus Logic