The questions plant, quality, security and finance teams ask us before a pilot, answered in the first sentence.
No, not by default. AgentMesh runs air-gapped on your factory network, and raw signals, images and models stay on site. The only things that go out are the ones you choose, such as work orders to your maintenance system, over outbound-only connections. AgentNexus, the central rack, can also connect out to Claude and your ERP for business skills such as quotes and quality reports — outbound only, with a named person approving every draft, and switched off on controlled programs.
Nothing changes at the machine. Each AgentMesh pod decides locally and keeps running without a link. Findings for AgentNexus queue up and sync when the link returns.
No. AgentMesh is never on the path that moves equipment and makes no SIL claim. It acts directly only on low-consequence outputs such as a reject gate or rework diverter (Lane A). Anything safety-related is an alarm and a request that your PLC, safety system and operators decide (Lane B).
Unovie's custom-built hardware accelerators, engineered for agentic performance, low latency and high availability. The reference AgentMesh pod is four AMD Ryzen AI Max+ 395 servers in a 3U shelf; NVIDIA Jetson AGX Thor serves robotics and vision at the tool, and NVIDIA DGX Spark serves as the AI engineering lab.
No. Unovie supplies the hardware configured and tested. You can buy it outright or take it as a service with no upfront hardware cost.
The site audit is at no charge: a 1–2 day visit on site, followed by written findings and a pilot plan. The 6-week paid pilot is $40–60K and is credited in full against a production site signed within 90 days.
One domain kit running on your own data, a baseline ROI view, a measured latency report and a signed evidence pack of what the system did and why.
Per monitored asset and domain kit, never per seat or per camera. We quote production after the pilot, when we both know the asset count and the value.
The target is about one quarter from the end of the pilot to a production site, because the pilot's playbook, connections and models carry straight over.
Sensors, robot controllers, vision stations, test rigs, PLCs (read-only, plus listed Lane A outputs), MES and quality systems, historians, and work-order systems such as SAP and Maximo. Industrial protocols include OPC UA, EtherCAT and Modbus.
Not yet: Anthropic's MHS is a research preview, by application, with no public spec, and Unovie isn't in it. AgentMesh already describes every device and output in a machine-checkable reference file with enforced limits, using the open OpenMHS schemas for now, and keeps its own model standard-neutral so we can add Anthropic's format when it is published. One rule holds whichever standard wins: a language model never operates your equipment. The pod enforces the limits itself, and Lane B stays a request your PLC decides.
Unovie is designed against NIST SP 800-53 and the NIST AI RMF and produces evidence for programs such as SP 800-171/CMMC and IEC 62443. Compliance is determined by your assessor, not by a product.
Only through tests. Each night the Kiln proposes small playbook and skill-adapter changes and keeps them only if they beat what is running on held-out cases. Every change is signed, logged and reversible, and the base model never changes.
No. Models improve on your site, from your data, and nothing is shared back to Unovie or to other customers.
Unovie is headquartered in Austin, Texas, with engineers on site across Texas and serving customers nationally.
Site audit: no charge, 1–2 days on site · 6-week paid pilot: $40–60K, credited in full against a production site signed within 90 days
