Universal Precision Instrument Interface — sensors and field cameras today; direct instrument protocols are planned.
Live today: sensor readings over HTTPS/JSON and photos from field cameras flow straight in, and a threshold breach triggers a workflow. Planned: direct industrial protocols (Modbus, OPC-UA, MQTT), pluggable adapters and per-device cryptographic identity.
One workflow engine, from cameras in a plastic tunnel to sensors on a production line. On the Enterprise plan it can run in your own environment.
Five steps: how NEXUPIRA turns photos and readings from the floor into work that has an owner and waits for approval.
These are the scenarios we are planning with partners; they are not available yet. Everything marked Live in the 3D scene above works today.
Today, sensor readings and camera photos come in over REST (HTTPS/JSON). Adapters for the other six protocols are planned and will land in the same ingress, with anomalies going to the same event bus.
TCP / RTU
PLCs · drives · power meters
binary · TLS
industrial controllers · SCADA
pub/sub · QoS 2
IoT sensors · edge devices
HTTPS · JSON
cloud-bridged instruments
HTTP/2 · protobuf
high-throughput streams
RS-232 / RS-485
calipers · balances · spectrometers
HID profile
OCR scanners · readers · particle counters
This is the design contract for the UPII ingress. Items marked Planned are not available yet; sovereign deployment is offered on the Enterprise plan.
One adapter per protocol, schema negotiated on first contact. Plug a new instrument → ingress queries its capability → registers it.
Native frame preserved in storage. The LLM sees a JSON projection — not the frame itself. Same data, two views.
Ingress + storage + inference + decision + egress all inside customer deployment. No third-party cloud hops.
One key pair per device. Telemetry signed. Replay-resistant nonce. Audit log pinned to device ID.
Default deny. TLS / mTLS. Per-frame audit log. Any ingress request is replayable, traceable, and verifiable.
Schema negotiated on first contact, then versioned. Device firmware change → previous data never breaks.
This is the planned ingress design: binary frames kept for long-term storage and replay, a JSON projection for the LLM. The event bus and workflow engine in it are already live.
Adapter → ingress → twin entity → Event Bus → workflow → audit log, all inside your deployment (Enterprise plan).
The raw frame is the audit evidence; the JSON projection is the LLM’s view. Both come from the same signed source. (Planned)
One key pair per device, signed telemetry, replay_nonce rejects duplicates. Cryptographic identity, not an IP allow-list. (Planned)
Three planned industrial chains. They will run on the same workflow engine that is live today; what is still in development is the direct instrument protocol at the front.
Sensors and field cameras connect today. Want a specific instrument wired in directly? Bring your line and talk to us.