7 Best Low-Code Platforms for Building Industrial IoT Applications

Last Updated on October 26, 2026 by Sam Thompson

Low-code sounds like one category, but the seven platforms below offer different ways to build applications.

Some focus on visual logic flows, others on operator screens and dashboards, and others on no-code frontline apps. In this article, low-code means most screens, flows and rules are built in visual editors, with code available for the rest.

The platforms are grouped by the editor each vendor leads with and listed alphabetically inside each group. The right choice depends on what the team needs to build, how it connects to industrial equipment and where the application must run.

What are the best low-code platforms for building industrial IoT applications?

No single low-code platform is best for every industrial IoT project. FlowFuse, Losant and ThingsBoard offer logic-flow editors. Ignition, Iotellect and ThingWorx offer screen designers. Tulip offers a no-code app editor.

Selection depends on connectivity to PLCs—programmable logic controllers that control machines—network-loss behaviour and the pricing unit. All seven provide a route for custom code.

What to compare when choosing a low-code industrial IoT platform

PLC connectivity

Which component talks to the PLC: built-in drivers, a separate gateway or an add-on?

OPC UA is a platform-independent architecture from the OPC Foundation for exchanging industrial data and events. Modbus is a simple client-server messaging protocol, first developed by Modicon in 1979. MQTT is a lightweight, open publish-subscribe protocol standardised by OASIS, in which devices exchange messages through a server, often called a broker.

Visual development and dashboards

Does the editor draw screens, flows, rule chains or no-code apps?

This covers dashboards, HMI (human-machine interface) screens and SCADA (supervisory control and data acquisition), a computerised system that gathers and processes data and applies operational controls, often across distant sites.

Automation and code

What is built visually—rules, workflows, alarms—and where does the team switch to scripting, a software development kit (SDK) or custom code?

Edge deployment

Edge computing means running computation on or next to the devices that produce data.

Four properties matter: hosting on premises, logic that runs locally, store-and-forward (holding data on site until the link returns) and a licence to run fully offline.

Licence and ownership

Who owns the product, and which licence covers production use?

Pricing

Which plan or module contains the PLC route, automation and scripting the project needs?

Low-code vs traditional coding vs AI-assisted development

In low-code IoT development, visual editors provide an application-building route alongside custom code. All seven platforms support both. The contrast here is with development organised primarily around source code.

The distinction between low-code, vibe coding and AI-assisted low-code comes down to how teams inspect, test and maintain the result. Visual low-code uses application models and editors, vibe coding relies heavily on AI-generated implementation, and AI-assisted low-code brings AI into the visual development process.

Platform	Device / PLC Connectivity	Visual Development	Dashboards	Automation	Deployment	Pricing	Best Fit
FlowFuse (built on Node-RED)	FlowFuse Edge Certified Nodes for OPC UA, Modbus, S7 and EtherNet/IP	Node-RED browser flow editor	FlowFuse Dashboard nodes	Event-driven flows, Switch rules, Function nodes	FlowFuse Cloud, self-hosted Docker/Kubernetes, edge Device Agent	Edge, Hub and Fleet: contact sales; 30-day Cloud trial	OT teams connecting PLCs, machines and systems
Losant (SUSE Industrial Edge)	Gateway Edge Agent for Modbus, OPC UA, S7 and Allen Bradley	Drag-and-drop Visual Workflow Engine	Drag-and-drop dashboards, custom HTML/chart blocks	Workflows, events, notifications, device commands	Managed cloud, customer cloud, on-premises; edge workflows	Custom pricing; free Developer Sandbox	White-labeled, multi-tenant connected-product applications
ThingsBoard	MQTT, HTTP and CoAP; Modbus/OPC UA/S7 via IoT Gateway	Visual rule chains, widget and SCADA dashboard editors	Widget dashboards and SCADA layouts	Rule Engine, alarm rules, multi-channel notifications	Cloud, Private Cloud, self-hosted; Edge add-on	Cloud $0–$749/month; self-hosted $0–$499/month by device tier	Device management, data collection, processing and visualization
Ignition	Modbus, Siemens S7 and Allen-Bradley drivers; MQTT via Cirrus Link modules	Designer drag-and-drop data binding	Perspective browser screens or Vision HMI screens	Tag alarms; notifications via Alarm Notification module	On-site/multi-site servers, Edge editions, Cloud Edition	Platform estimate: $1,200 USD per server, perpetual; modules separate	SCADA, IIoT, MES and HMI applications
Iotellect	Drivers for OPC UA, Modbus, Siemens S7, Omron FINS and other protocols	Browser Web UI Builder, drag-and-drop workflow blocks	Operator screens, symbol library, browser dashboards	Alerts; workflows from Standard, correlators from Premium	Cloud, on-premises, hybrid; edge nodes with store-and-forward	Basic $99, Standard $499, Premium $1,999 per month per instance	Integrators, OEMs and ISVs building their own applications
ThingWorx (Velotic)	Kepware Server or Kepware Edge as separate products	Mashup Builder drag-and-drop UI canvas	Web mashups with responsive layouts	Alert rules, subscriptions; optional ThingWorx Flow	Managed cloud or on-premises; edge via EMS/SDK/Kepware Edge	Contact sales	Manufacturing asset monitoring and connected field assets
Tulip	Machine Monitoring add-on with OPC UA/MQTT connectors	No-code App Editor and Triggers	Dashboards tab and dashboard apps	App/machine triggers; Automations metered in tasks	Tulip-managed SaaS	Essentials $100/month, Professional $250/month per interface, billed annually; 10-interface minimum	Operator-facing apps on top of existing enterprise systems

Group A: Flow and rule-engine platforms

Logic is drawn as blocks, or nodes, joined by wires: Node-RED flows, Losant workflows and ThingsBoard rule chains.

1. FlowFuse (built on Node-RED)

FlowFuse is built on Node-RED, an OpenJS Foundation project under the Apache 2.0 licence. FlowFuse itself is made by a company separate from that project, formerly FlowForge. Its PLC protocol nodes for OPC UA, Modbus, Siemens S7 and EtherNet/IP belong to the Edge Certified Nodes catalogue, part of FlowFuse Edge.

Node-RED provides a browser-based flow editor, with JavaScript Function nodes where wiring is not enough. FlowFuse Dashboard nodes build dashboards, and Switch nodes route messages by rules.

FlowFuse runs in its cloud or self-hosted on Docker or Kubernetes. Its Device Agent runs flows on edge hardware. Flows continue running on the device when its connection to FlowFuse is lost.

Edge, Hub and Fleet plans require a sales quote, and FlowFuse Cloud has a 30-day free trial.

Best for: OT teams connecting PLCs, machines and systems. OT means operational technology.

Limitations:

• PLC protocol nodes are not available by default and come with FlowFuse Edge, through sales. Free Node-RED community packages are separate third-party packages.
• Store-and-forward uses a blueprint with local SQLite buffering that the team imports and adapts to its data source and output.
• An unlimited-use licence is not currently available.

2. Losant (SUSE Industrial Edge)

SUSE acquired Losant in February 2026 and introduced SUSE Industrial Edge, built on Losant technology, in April 2026. Losant reaches PLCs through its Gateway Edge Agent, which supports Modbus, OPC UA, Allen Bradley and Siemens S7.

The Visual Workflow Engine is a drag-and-drop editor, and a Function Node runs custom JavaScript. Dashboards are drag-and-drop, with custom HTML and chart blocks. Workflows can trigger email notifications, create events and send device commands.

Losant can be hosted in its managed cloud, a customer’s cloud account or on-premises. Edge Workflows can run without an internet connection and buffer reported data while offline.

Losant’s pricing is based on a tailored quote, and the Developer Sandbox is free.

Best for: White-labeled connected products that use built-in multi-tenancy and user authentication.

Limitations:

• Edge Workflows are required to read and write to devices through the supported industrial protocols.
• The Edge Workflow Function Node cannot keep a persistent controller connection or run a server.
• The edge agent buffers a maximum of 65,000 MQTT messages, then overwrites the oldest.

3. ThingsBoard

Since version 4.4, ThingsBoard is source-available under the Business Source License 1.1: the code is public, but the licence restricts some production use. Earlier releases remain under Apache 2.0.

The platform supports MQTT, CoAP, HTTP, LwM2M and SNMP directly. Logic runs in rule chains, a visual pipeline of Rule Nodes, scripted in TBEL, the default scripting engine, or JavaScript.

Dashboards are built from widgets, including SCADA layouts. Automation uses the Rule Engine, alarm rules and multi-channel notifications.

ThingsBoard runs as Cloud, Private Cloud or self-hosted. ThingsBoard pricing for North America ranges from $0/month for Cloud Free with 5 devices to $749/month for Business with 1,000 devices. Self-hosted plans range from $0/month for Free with 100 devices and 1 production instance to $499/month for Business with 1,000 devices. Hosting is not included in self-hosted plans. Perpetual self-hosted licences start from $4,999.

Best for: Device management, data collection, processing and visualization for an IoT solution.

Limitations:

• Modbus, OPC UA, BACnet and S7 run through the separately installed ThingsBoard IoT Gateway.
• Free production use covers a commercial organisation with up to 100 devices on one server, with ThingsBoard branding visible and a licence key.
• ThingsBoard Edge runs the rule engine and alarms locally during a disconnection but requires a ThingsBoard server. Fully offline licensing needs a Perpetual licence whose Order authorizes an Offline Deployment.

Group B: Industrial application platforms with screen designers

Operator screens and dashboards are drawn on a canvas and bound to data.

4. Ignition (Inductive Automation)

Ignition reaches PLCs through drivers for Allen-Bradley over EtherNet/IP, Modbus and Siemens S7. These drivers require Ignition’s OPC UA module. Siemens Enhanced is a separately licensed driver. MQTT comes through Cirrus Link modules that Inductive Automation sells but does not develop.

The Designer binds screen components to PLC tags and SQL queries by drag and drop. Scripts run in Jython 2.7, Python running on the Java Virtual Machine. A complete project can be built without scripting, while projects with specific requirements may need some Python.

Screens come from the Perspective browser module or Vision module, and alarm notifications from the Alarm Notification module.

Ignition Edge Panel stores data locally for up to 35 days or 10 million data points, whichever comes first. The Ignition price list gives an estimated price of $1,200 USD for a single Ignition Platform licence, one-time and perpetual.

Best for: Building applications for SCADA, IIoT, MES, HMI and more. MES means manufacturing execution system.

Limitations:

• Licences are per server, and the Perspective, Vision, Alarm Notification and MQTT modules are priced separately. Support is billed annually.
• Cloud Edition is not a SaaS version of Ignition and does not include OPC COM or OPC UA drivers.
• Imported libraries must be compatible with Python 2.7.

5. Iotellect

Iotellect’s drivers reach PLCs over OPC UA, OPC DA/HDA/AE, Modbus, Siemens S7, Omron FINS and dozens of other protocols.

The Siemens S7 driver supports S7-200/200 SMART, S7-300/400 and S7-1200/1500. Compatibility with other S7 types is not guaranteed. EtherNet/IP uses explicit (UCMM) messaging.

In Iotellect, operator screens and dashboards are built in a browser-based Web UI Builder, and application logic in drag-and-drop workflow blocks. Java and Python scripting remain available for unusual requirements that need custom code.

Deployment options are cloud, on-premises or hybrid, with edge nodes that store and forward data. Plans run from $99 per month for Basic to $499 for Standard and $1,999 for Premium, per dedicated platform instance. Enterprise pricing is available on request.

Best for: System integrators, independent software vendors and OEMs building their own IoT applications.

Limitations:

• Iotellect is a development platform rather than an out-of-the-box application. The customer’s own team or a partner builds the application there. Its Low-code Development and DevOps documentation explains the development approach.
• Basic does not include Workflows, Scripts, Machine Learning or EtherNet/IP. Workflows start with Standard, and correlators with Premium.
• Custom plugins are disabled on the managed cloud.
• On-premises deployment has no separate public licence price. Edge pricing requires a quote, with a minimum order of 10 licences per edition.

6. ThingWorx (Velotic)

ThingWorx is a distinct product line in TPG-backed Velotic, following PTC’s sale of its Kepware and ThingWorx businesses to TPG in March 2026.

In the ThingWorx Applications setup, PLC tags and drivers for each piece of equipment are configured within Kepware Server, a separate product.

The Mashup Builder provides a drag-and-drop UI canvas for low-code development. Services are written in JavaScript or SQL, with Java for extensions only. Dashboards are mashups: web pages with responsive layouts. Alert rules are evaluated when new data for a property arrives.

ThingWorx runs as a managed cloud service or on servers at the customer’s site or data centre. Pricing requires a sales quote.

Best for: Manufacturing asset monitoring, connecting brownfield and greenfield assets and monitoring asset health and utilization in real time.

Limitations:

• The ThingWorx Applications PLC route adds Kepware Server to the stack. Other integrations may use different approaches.
• For on-premises installations, ThingWorx Flow is an optional package for Enterprise SCO and SCP editions and requires an existing ThingWorx Foundation instance.
• In Kepware Server’s ThingWorx Native Interface, Store and Forward is disabled by default.

Group C: No-code frontline apps

Operator apps are built in a no-code editor with form-based triggers.

7. Tulip

Tulip is a no-code frontline operations platform. For OPC UA and MQTT machine monitoring, it uses the Machine Monitoring add-on and a Tulip Connector Host connected to the customer’s OPC UA server or MQTT broker.

Tulip supports Kepware-compliant OPC UA servers fully and may support only a subset of functionality for other OPC UA servers.

The App Editor lets teams build operator apps without writing code. Dashboards sit in a Dashboards tab or in apps. Triggers send email or SMS alerts, and Automations are priced based on the number of tasks performed.

Tulip pricing starts at $100/month per interface for Essentials and $250/month per interface for Professional, billed annually, with a 10-interface minimum. The pricing unit is a Monthly Active Interface: a device running Tulip Player. Enterprise and Regulated Industries plans require a quote.

Best for: An operator-facing execution layer on top of existing enterprise systems.

Limitations:

• Machine Monitoring is an add-on and is not included in Essentials. Add-on prices are not published.
• Tulip operates as SaaS and has announced End of Life for traditional on-premises deployments.
• Cloud deployments require a high-quality, stable network connection. If the Player’s app trigger-event queue fills during an outage, new incoming app events are dropped and permanently lost. Its default limit is 100 events.
• MQTT and OPC UA machine data have a listed rate of 1 Hz per machine attribute.

How to choose a low-code IoT platform for a team

Start from what the team will build and how the PLCs are reached:

• FlowFuse: OT teams working in flows.
• Losant: Teams building a white-labeled, multi-tenant connected product.
• ThingsBoard: Device management and visualization, self-hosted if needed.
• Ignition: SCADA, HMI and MES applications licensed per server.
• Iotellect: Integrators and OEMs building their own applications.
• ThingWorx: Asset monitoring with Kepware in the stack.
• Tulip: Operator apps over existing enterprise systems, as SaaS.

Price the plan or module that contains the PLC route, workflows and scripting the project needs. Ask which component holds the buffer when the link drops, how projects are kept in version control such as Git and what leaving would cost.

Before committing, test the actual controllers, expected data rates and network-loss scenarios. Build time, integration effort and exit costs depend on the application and the team maintaining it.

FAQ: PLC integration, edge operation and customization

How do low-code IIoT platforms connect to PLCs?

There are three main routes. Ignition and Iotellect use drivers inside the platform server. ThingWorx, ThingsBoard, Losant and Tulip use a separate gateway or connector: Kepware in ThingWorx’s Applications setup, the ThingsBoard IoT Gateway, Losant’s Gateway Edge Agent, or a Tulip Connector Host to the customer’s OPC UA server or MQTT broker.

FlowFuse uses an add-on node catalogue. A protocol name does not guarantee compatibility with every PLC model or firmware version.

Do these platforms keep working at the edge when the network drops?

Each platform offers a different mix of local logic, data buffering and offline licensing.

On Ignition Edge Panel, local storage holds up to 35 days or 10 million data points, whichever comes first. Losant’s edge agent keeps at most 65,000 MQTT messages before overwriting the oldest. In Kepware Server’s ThingWorx Native Interface, Store and Forward is disabled by default. Tulip, run as SaaS, requires a high-quality, stable network connection.

How much code will a team still write?

All seven platforms provide a way to write code. Ignition uses Python (Jython 2.7), ThingWorx JavaScript or SQL services, ThingsBoard TBEL or JavaScript, Losant and Node-RED JavaScript, and Iotellect Java and Python.

Tulip offers HTML, CSS and JavaScript Custom Widgets on Professional plans and above. The amount of code depends on the application’s integrations, business logic and interface requirements.

Should control or safety logic run in a low-code platform?

The NIST Guide to Operational Technology (OT) Security explains that timing requirements vary by installation and that some systems require reliable, deterministic responses.

Deterministic means the system responds within a predictable time. Before moving logic into an application layer, establish where time-critical control and safety functions run and whether they remain in the controller.

Are any of these platforms open source?

Node-RED is open source under Apache 2.0. The FlowFuse platform repository uses Apache 2.0 outside forge/ee, whose production use requires a subscription.

ThingsBoard 4.4 and later is source-available under BUSL 1.1, and earlier releases remain Apache 2.0. SUSE has announced plans to open source the Losant technology.

Ignition, ThingWorx, Tulip and Iotellect are sold under commercial terms. Ignition Maker Edition is free for personal, non-commercial projects and is not intended for industrial or professional use.

Why can’t the prices in the table be compared directly?

The units differ: a per-server perpetual licence for Ignition, monthly device-tier plans for ThingsBoard, a per-interface price billed annually with a 10-interface minimum for Tulip, or a monthly price per platform instance with plan-dependent features for Iotellect.

ThingWorx, Losant and FlowFuse require quotes for their paid offerings. Modules, add-ons, hosting and support also affect the total cost.

Choosing the right platform

The editor shows how a team will build. The PLC route, edge behaviour and pricing unit show what the project will depend on. Match those requirements to the application before choosing a platform.