How JasperX works

Two parts. JasperNode runs at the edge: it owns the tags, executes the logic, talks to the field devices, and keeps working with no cloud connection at all. JasperX is the cloud: the browser workspace, the AI, your fleet in one view, and the history of every change ever made.

Neither trusts the other's availability. The node runs the plant. The cloud runs the product.

The AI does the authoring: tags, scripts, connectors. It explains what it changed and why. It is not an autocomplete bolted onto a code editor; it works with the same objects you do, through the same audited interfaces.

Ask-mode is the read-only version: it explains logic it didn't write, helps diagnose faults, and answers questions about the live system without the ability to change anything.

The AI authors freely. Deploying is different. Changes that can affect the field require a human to read them and approve them. The gate knows the difference between a development bench, commissioning, and a production system, and tightens accordingly.

Every change, human or AI, lands in the audit trail: who, when, how, and for AI changes, exactly which model and which conversation produced it.