Looking for a Node-RED alternative?
Meet Loopze.
Loopze is a modern flow-programming runtime built from the ground up for the industrial edge. One Go binary. Native MQTT, Modbus and OPC-UA. Goroutine-per-node parallelism. No node_modules, no Node.js install, no community-package supply chain.
Why people switch from Node-RED to Loopze
1. Single binary, not a Node.js installation
Node-RED is a fantastic tool, but deploying it to an edge gateway means installing Node.js, managing npm, pulling down a tree of community modules and hoping the versions still resolve in two years. Loopze ships as one statically-linked Go binary (~5 MB). Copy it, run it, done. No package manager. No transitive dependencies. No silent breakages when a sub-dependency gets yanked.
2. Native industrial protocols, not community plugins
In Node-RED, MQTT works well — but Modbus, OPC-UA, S7 and friends rely on community npm packages of varying quality and maintenance. Loopze treats industrial protocols as first-class citizens. MQTT, Modbus (TCP & RTU) and OPC-UA are implemented natively in Go inside the runtime, with consistent semantics, reconnect handling and back-pressure.
3. Real parallelism, not a single event loop
Node-RED runs every node on Node.js's single event loop. One slow Modbus poll or blocking transform can stall the entire flow. Loopze runs each node in its own goroutine, scheduled across all CPU cores by the Go runtime. A 200 ms Modbus read on one branch does not delay a 1 kHz MQTT pipeline on another.
4. Type-safe transforms — Go, JavaScript or expr-lang
Write per-message logic in whichever language fits the job. JavaScript covers the everyday case and feels familiar to Node-RED users. expr-lang is a fast expression language for one-liners. Go transforms compile into the binary for hot paths where every microsecond counts.
5. Built-in NATS broker, no external dependency
Loopze embeds a NATS broker for inter-node messaging and external pub/sub. You can publish flow events out to the rest of your stack — or consume external signals — without standing up Redis, RabbitMQ or a separate broker container.
Loopze vs. Node-RED — Quick Comparison
| Loopze | Node-RED | |
|---|---|---|
| Runtime | Single Go binary (~5 MB) | Node.js + npm tree |
| Concurrency | Goroutine per node, multi-core | Single event loop |
| MQTT | Native, built-in | Built-in |
| Modbus | Native, first-class | Community npm package |
| OPC-UA | Native, first-class | Community npm package |
| Transform languages | Go, JavaScript, expr-lang | JavaScript |
| Embedded broker | NATS, built-in | None (external) |
| Edge deployment | scp one binary | Node.js + npm install |
| License | AGPL-3.0 (+ commercial) | Apache-2.0 |
Node-RED is a registered trademark of OpenJS Foundation. This page is an independent comparison written by the Loopze team.
When Node-RED is still the right choice
We are not pretending Loopze fits every use case. Stick with Node-RED if:
- You rely on a large catalogue of community nodes (smart-home integrations, niche cloud SDKs) that no industrial-focused runtime will ever match.
- Your team is deeply invested in Node-RED flows that would take months to port.
- You need IBM/OpenJS commercial support specifically.
Loopze is built for one thing: industrial flow automation at the edge. If that is your use case, the trade-offs above tilt sharply in our direction.
Frequently Asked Questions
Is Loopze a drop-in replacement for Node-RED?
No. Loopze is a fresh implementation, not a fork. Node-RED flow JSON does not import directly. The mental model is the same — nodes, wires, messages — so anyone who used Node-RED will feel at home, but you will be rebuilding flows in Loopze's editor.
Why pick Loopze over Node-RED for industrial use cases?
Native MQTT/Modbus/OPC-UA, true multi-core parallelism, and single-binary deployment. The three together remove most of the friction that shows up when Node-RED leaves the lab and meets a production line.
Can I write custom logic in JavaScript like in Node-RED?
Yes. JavaScript transforms work the way you would expect. You can also drop into expr-lang for fast one-liners or Go for compiled hot paths.
Is Loopze open source?
Yes — AGPL-3.0 on GitHub. A commercial license is available for closed-source embedding.
What platforms does Loopze run on?
Linux, macOS and Windows on amd64 and arm64. The single binary is small enough (~5 MB) to ship onto industrial PCs and ARM gateways.
Try Loopze in 60 seconds
Download the latest release or install with one command:
curl -L loopze.dev/install | sh
loopze --port 1880Then open http://localhost:1880 and build your first flow.