How it works

Create the project. Build it visually. Deploy it locally.

The cloud is the design and control plane. The Edge Runtime is the execution plane. Nothing about running your gateway depends on staying connected to us.

1. Create a project

A project is one deployable gateway design: its device definitions, the Edge Logic flow, destinations, settings, versions and deployments. Creating one needs nothing installed and no device reachable.

2. Build it in the Edge Logic Editor

The editor is where the gateway is constructed. Drag a protocol node onto the canvas, configure the connection, define the tags, add the processing you need, and wire it to a destination.

Source node

Editor-only

You do not have the device in front of you.

The register manual, a CSV or a known tag map is enough. Add a Modbus node in the editor, type or paste the registers, wire the logic and deploy. Nothing in this path needs the Scanner or an io-tags file.

Scanner-assisted

You can reach the device on your own network.

Scan the device locally, push the result into a Gateway project, and the device arrives in the editor with its tags already defined. It saves typing; it is not a prerequisite.

Tags can come from anywhere. Type them in, paste them from a spreadsheet, import a CSV or an io-tags.json, clone a device you already defined, or start from a saved template. The Scanner is one of those routes, not the only one.

3. Validate before you deploy

Validation checks that the configuration is correct and that the Edge Runtime can actually execute it — required settings, tag definitions and addresses, data types, flow connections, expressions, destination configuration, duplicate identifiers and missing secrets.

It does not pretend to prove a PLC is reachable. A project may be engineered from a register manual for a site nobody has visited. Connectivity is proven by the Scanner when you have the device, or on site by the runtime's commissioning diagnostics.

4. Deploy to the edge

A validated design downloads in one of two forms. The trial is a zip with the Edge Gateway Console for the device and your design sealed inside a small .des file. The first run of the console activates the design with a code from the design page, installs the Edge Runtime as a service and shows it running; every later run is the console of that gateway. Every design on a platform gets the same runtime build — nothing is compiled per design.

The trial download, per platform

pump-house-trial-linux-arm64.zip
  edge-gateway-console-linux-arm64.deb   the Edge Gateway Console, with the Edge Runtime inside
  pump-house.des                         your design, sealed (AES-256-GCM)
  README.txt                             the three steps

Windows x64:   Edge-Gateway-Console.exe + <design>.des
Linux x64:     edge-gateway-console-linux-x64.deb + <design>.des
Linux ARM64:   edge-gateway-console-linux-arm64.deb + <design>.des

Windows x64
Extract the zip, run Edge-Gateway-Console.exe from an administrator terminal, enter the activation code. The gateway becomes a Windows service that starts with the machine.
Linux x64 and ARM64: Debian, Ubuntu, Raspberry Pi OS
sudo dpkg -i the .deb, then sudo edge-gateway-console in the folder with the .des. The gateway becomes a systemd unit enabled at boot. ARM64 is the build for a Raspberry Pi 4 or 5 and other ARM edge computers.
Activated once, offline from then on
The console sends the code and this machine's fingerprint to the site and receives a seven-day licence bound to both. Every later start runs from the local licence file; the site is never contacted again.
The console, whenever you need it
Run it again and it shows the service state, the licence, every device and destination with what is wrong and what to check, opens the web view in a browser (or prints its address on a device without a desktop), and tails the live log. remote enable makes the web view reachable from other computers, over HTTPS with an account.

The production package (also as a Docker target)

pump-house-gateway.zip
  modbuslogic-gateway(.exe)  the Edge Runtime
  project.json               the compiled configuration
  flow.json                  the Edge Logic flow
  io-tags.json               portable tag definitions
  README.txt                 how to run or install it

Run it or install it
In the foreground, as a Windows service or a systemd unit with service install, or in a container with a mounted data volume. A production licence file is installed the same way as a trial one and enforced the same way, offline.
Commission it
The runtime serves local diagnostics on the device: connection state, tag reads with raw and decoded values, response times, protocol exceptions and destination connectivity.
Credentials stay out of every download
Passwords and tokens are never written into a design or a package. You set them on the target, into an encrypted store on that machine.
It keeps running
The runtime does not need Modbus Logic Cloud to operate.

Step by step, with what the console prints and where the files land: downloading, installing on the device and activation in the documentation.

Start with a project

Create one, open the Edge Logic Editor and add a device. You can get to a validated gateway without touching hardware.

Create Gateway Project Protocols & capabilities Documentation