Knowledge Base

Export Runtime to Edge

Duration: ~30 min · Level: Advanced

Prerequisites: An Active workflow using on-prem components (or any workflow you want headless). Operator+ role. Target Windows or Linux machine.

Deploy a validated workflow to an edge PC or factory gateway as a self-contained runtime agent — no Studio UI required on site.

Goal

Export a Modbus-or-file workflow, install it as a Windows service, confirm heartbeats in Studio, and open the local agent dashboard.

Step 1 — Prepare the workflow

  1. Ensure the workflow is Active and passes validation.
  2. If it uses sub-workflows, those must be Active too (embedded automatically).
  3. Set global variables under Jobs → Variables if the edge host needs different URLs — they ship in the manifest.

Step 2 — Export Runtime

  1. Canvas toolbar → Export Runtime (or right-click canvas).
  2. Configure:
    • Runtime name — e.g. Line3-Gateway.
    • Target OS — Windows or Linux matching the edge host.
    • Deployment modeInstall as Service for production; Portable for USB trials.
    • Runtime dashboard port — default 9090.
    • Agent monitoring — this Studio instance or Nodlyn Cloud.
  3. Download the ZIP.

Full option reference: Runtime Export.

Step 3 — Install on the edge host

Windows (service):

  1. Extract the ZIP to e.g. C:\Nodlyn\Line3-Gateway.
  2. Run install\Setup.bat as Administrator.
  3. Service starts automatically; check Windows Services for Nodlyn Runtime - Line3-Gateway.

Linux (systemd):

  1. Extract to /opt/nodlyn/line3-gateway.
  2. Run sudo ./install/install.sh.
  3. systemctl status nodlyn-line3-gateway

Portable: run run.bat or run.sh — no install, ideal for demos.

Step 4 — Verify monitoring

  1. In Studio, open Agents tab — status should show Online with heartbeat.
  2. On the edge host, browse http://localhost:9090 for the built-in dashboard.
  3. Trigger the workflow (cron, file drop, or webhook) and check Jobs → History or the agent dashboard runs list.

See Runtime Monitoring for cloud vs on-prem views and mobile compact layout.

Step 5 — Update deployments

When the workflow changes:

  1. Re-validate and re-activate in Studio.
  2. Export a new ZIP and redeploy (stop service → replace files → start service).
Security: The ZIP contains workflow secrets and an agent token. Store and transfer it like a credential. See README-quickstart.txt inside the package.

Multi-workflow bundles

Export up to 10 Active workflows in one agent — useful when one gateway runs several small automations. Pick Multiple workflows in the export modal.

See also

Nodlyn Assistant
Ask me anything about Nodlyn
Hi! 👋 I'm the Nodlyn assistant. Ask me about the product, workflow components, connectors, agent runtime, agent capabilities, deployment, and more. If I don't know an answer, I'll point you to our contact form.