The technical surface beneath the chat.
The canvas is the node editor where a flow takes shape: read from an OPC-UA server, filter and transform, then write to a database and fire an alert. All without writing a line of code.
A flow is a chain of nodes.
Sources
Field and IT connectors open the flow: PLCs, meters, databases, APIs. Every node exposes the same output format.
Processing
Filter, merge, reshape, conveyor, trigger and cron work on data in transit. Conditions are written in MXL.
Destinations
History, time-series databases, email alerts, ERP or MES. The same reading can go to several places at once.
The flow, node by node.
All the technical power beneath the surface. You just see the conversation.
What you can put in between.
Trigger and Alert evaluate their conditions in MXL, Meddle's expression language: comparisons, AND and OR over numbers, strings and booleans.
What goes in and what comes out.
The rest, in short.
Do I need to know how to code?
No. A flow is composed from nodes. At most you write a condition in MXL, which is a comparison written the way you would say it out loud.
What is MXL?
Meddle's expression language. It evaluates a condition to true or false with comparisons, AND and OR, over numbers, strings and booleans.
Who builds the first flows?
We configure them during onboarding. From you we need one technical point of contact for the first session.
Can one flow write to several destinations?
Yes. The same reading can land in a time-series database, in an alert and in a business system in the same pass.
Want to see a flow built on your own data?
We connect a source and compose the first flow together, in a guided demo.
Book a demo