JasperNode is a runtime you install on a Linux device — from a small edge gateway up to a server — to automate machinery and processes. It polls field devices, runs your control logic, stores history, exposes data to dashboards and cloud services, and is configured entirely through a browser-based IDE.
Where a traditional PLC gives you a fixed scan, a vendor IDE and a closed I/O system, JasperNode is organised around one in-memory data structure — the tag tree — and three small building blocks that sit around it. If you can read and write tags, you can understand the whole system.
Everything is a tag
A tag is a named value at a path, like factory/line1/temperature. Sensor readings, setpoints,
computed values, connector configuration and system metrics are all tags in one live tree.
There are no separate config files or data stores to learn.
Logic is attached to tags
A tag can carry a small script that recomputes its value when its input tags change. Logic is reactive and event-driven: nothing runs until a value it depends on actually changes.
Connectors bridge the edges
Connectors move values between the tag tree and the outside world — fieldbuses (Modbus, EtherCAT, S7…), networks and clouds (MQTT, InfluxDB…), and built-in services. They are the only things that touch I/O.
An AI agent works on the tags
A built-in AI agent can read the tree, write logic and set up connectors — but changes that affect the running process pass through a test-and-sign-off gate before they take effect.
