Node-RED & Crosser

Get data from the machine to where it's needed — with visual data flows instead of custom code. We build integrations with Node-RED and Crosser that your team can understand, adapt and extend.

Where most teams start

  • Every new interface is its own software project with its own code
  • Integrations depend on one person who knows how they work
  • Small changes — a new sensor, one more field — take weeks
  • Data flows at different sites work differently, with no central overview

Node-RED or Crosser?

Node-RED

The open-source tool for visual data flows: quick to set up, flexible to extend, with a large community.

Best for single machines and lines, prototypes and lean integrations.

Crosser

A low-code platform for streaming data and integration at the edge, with central management: flows are built once, then deployed, monitored and updated across many edge nodes.

Best for multiple sites and centrally managed production use.

What we deliver

1

Analysis and tool choice

We work out which data needs to go where and recommend Node-RED, Crosser or a combination — to fit the scope, operations and security requirements.

2

Building the data flows

We connect machines and sensors (OPC UA, MQTT, MODBUS) with MES, ERP, databases and cloud services — including data preparation, filtering and alerting.

3

Running at the edge

The flows run close to the machine, on industrial PCs or edge gateways, and keep working when the network connection drops.

4

Handover and training

Documented, traceable flows and training for your team, so you can make changes yourself.

Technologies we use

Node-REDCrosserOPC UAMQTTMODBUS/TCPREST/APISQLInfluxDBDockerEdge-Gateway

Frequently asked questions

Do we need programming skills to change the flows later?

No. Both tools are visual. After a short training session, your team can make simple changes themselves; we support you with larger extensions.

Can Node-RED and Crosser be used together?

Yes. A project often starts with Node-RED on one machine and is later scaled to several sites with Crosser. We design the architecture from the start so that this step is well prepared.

Which systems can be connected?

Machines and controllers via OPC UA, MQTT or MODBUS, databases, MES and ERP systems via REST interfaces, and common cloud platforms.

What happens if the network goes down?

The flows keep running locally at the edge. Data can be buffered and sent once the connection is back.