Edge Gateway

Downloading

A static installer per platform, the same for everyone, and an activation bundle per device: one small zip with your design and a licence for that machine.

Product page →

The two downloads

DownloadContentsFor
Installer (Windows x64, Linux x64, Linux ARM64)A zip with the platform's Edge Gateway Console (the runtime inside it) and a README. Made once per release; the same file for every user and every designEvery device, once
Activation bundleA zip of a few kilobytes: manifest.json in the clear, and the design and its licence sealed with a key only that device can deriveOne device: a trial, or a seat of a purchased licence
Production package (also Docker)A zip with the runtime, project.json, flow.json, io-tags.json and a READMEA licensed deployment run or installed by hand

The installer links are in the Devices panel of the design page. Run the console on the device and it shows the device code, sixteen characters in four groups. Enter the code in the same panel, give the device a name if you like, choose Trial or one of your purchased licences, and press Download activation bundle. The design must validate; the bundle holds it exactly as it is at that moment. The panel lists every bundle issued, with the device, the licence and when it ends, and each can be downloaded again unchanged.

WHAT IS IN THE ACTIVATION BUNDLEmanifest.jsonreadabledesign name and versionruntime version it needsa hint of the devicelicence kind and endbundle.encsealedlicense.jsonproject.json · flow.jsonio-tags.json

The key that opens bundle.enc is the device code itself: the device derives it from its own machine id, you typed it into this site, and nobody who merely holds the zip has it. The code appears nowhere in the zip, not in the file name and not in the manifest; the manifest carries a one-way hint the console compares with its own code, so it can say "this bundle is for another device" without trying to open it. The manifest is also authenticated by the cipher, so it cannot be edited or swapped. A bundle can therefore travel by email or on a USB stick, which is how it reaches a device with no internet.

Which installer

DeviceDownload
Windows 10 or 11, Windows Server, x64Windows x64: Edge-Gateway-Console.exe in the zip
Debian, Ubuntu or another dpkg-based Linux on an industrial PC, x64Linux x64: edge-gateway-console-linux-x64.deb in the zip
Raspberry Pi 4 or 5 on Raspberry Pi OS (64-bit), or another ARM64 edge computerLinux ARM64: edge-gateway-console-linux-arm64.deb in the zip
The 32-bit Raspberry Pi OS is not a target; use the 64-bit image. A Linux without dpkg can run the production package's plain binary instead.
Downloading · Edge Gateway documentation | Modbus Logic