Ipnops provides inputs, integrations, processing, compute and interfaces for robotics, machines, infrastructure and software.
Sensor nodes with a hardware key sign every reading they take. Commands go out only after a twin has checked them and a person has approved them.


Areas.
What Ipnops runs. All areas.
Rooms and acoustics, buildings and comfort, crowds and humans, weather and earth, physics and robotics, worlds and scenes.
Fine-tuning language models and fitting surrogate models, scored on held-out cases.
Forecasts with intervals, and surrogate models.
Language models, perception, and speech and audio.
Sensors and edge devices, signed readings, open formats, APIs and SDKs, the job interface and the Living Worlds link.
What it integrates with.
Ipnops integrates with Living Worlds for simulation, training and lives in digital worlds. Who it is for, with an example for each.
Robot middleware, bags and robot descriptions, read observe-only.
Industrial servers, motion buses, vehicle buses and register devices, read observe-only; attaching to your machine is scoped with you.
Meters, controllers and monitors through registers, brokers and industrial servers, into twins.
Open file and stream formats and the SensorThings model.
A REST API, an MCP server and an open SDK client under Apache-2.0.

One loop, in both directions.
A living world trains an agent. A twin holds the calibrated state of a real machine or place. Ipnops connects the two to the machine: the agent goes out under checks and approval, and what the machine measures comes back into the twin.
Worlds in, machines out.
Simulation and training results reach a twin as open formats, and nothing reaches a machine except through the gate.
A twin is the calibrated counterpart.
Each real machine or place has a twin, solved for a stated band of operation. Every plan is checked against it.
Ipnops provides the way across.
Readings are verified, graded and admitted into the twin. Commands are checked, gated and approved before they leave.
The physical world keeps the worlds honest.
Every action produces measurements. They return through the same layer and recalibrate the twin and the worlds trained on it.

What Ipnops does, on its own.
Every capability here exists and works without any particular vendor. Compatibility with the tools a team already uses comes after.
Measurement kinds, purposes, system classes and actions, with signed documents crossing it: batch, command, receipt and birth record. Live in production.
Every reading is signed by the device that took it and graded by how that device holds its key: soft, device, se, tee, dice or tpm. A result takes the grade of its weakest input.
BLE sensor nodes, microcontrollers and application-class single-board computers have signed readings into the interface on real hardware.
A reading is admitted into a twin only inside the band the twin was solved for. Outside it the reading is recorded and the twin makes no claim.
A system declares what it is for, what it measures and its safe limits. A check returns every issue it finds, each with a code, before anything acts.
Observe-only bus adapters for ROS 2, OPC UA, EtherCAT, MQTT, SocketCAN and Modbus, and a sensor-pipeline record sink. Each decodes and signs; none can send.
Observe-only, shadow, approved. Every command is bounded, expires and is checked against the twin. A person approves what moves a machine, and an advisory stop sits above the machine's own emergency stop.
Sealed data held by a person's passkey or a node's hardware key, and isolated silos where one agent runs with its own kernel and no network.
Agents, models and jobs run in isolated environments with a signed policy and an identity derived from the node's hardware key, on GPU and CPU machines.
A REST API, an MCP server and an open SDK client (@livingworlds/sdk, Apache-2.0).

Robotics, machines, infrastructure, software, integrations.
The same interface serves every field. An agent is born into a body, a plant, a program or a person's twin through a declared purpose, declared limits and the same approval path.
Humanoids, mobile manipulators, quadrupeds and arms. A trained agent is born into the body through the same interface, controlled through its twin.
Industrial machines, AMRs and AGVs, drones, vehicles, construction and agricultural machines, reached over industrial servers, motion buses and vehicle buses.
Buildings, plants, grids, water and structures. Meters, controllers and monitors feed their twins through registers, brokers and industrial servers.
APIs, services, simulators, agents and other programs. An agent is born into software through a declared interface, a purpose and its limits.
Middleware, buses, industrial servers, brokers and vendor systems. Each is a typed adapter that signs what it reads.
Every industry that moves, senses or computes.
The same interface serves each industry. What we do for each.
Vehicles
Road, heavy, marine and air vehicles over vehicle buses and robot middleware. Adapters read the bus without sending on it.




Robots
Humanoids, quadrupeds, mobile robots and hands, born into through a twin and a command gate.




Energy
Grids, storage, wind and solar: meters and controllers read through registers, brokers and industrial servers.




Infrastructure
Factories, data halls, water and buildings as twins fed by signed readings.





A twin sits between every model and every machine.
Nothing enters a twin that has not been verified. Nothing reaches a machine that has not been checked against its twin.
Readings in, inside the band.
Every reading is signed, graded by its weakest link and admitted into the twin only inside the band the twin was solved for. Outside it, the reading is recorded and the twin makes no claim.
Commands out, checked twice.
A command is checked against the twin's forecast and against the system's declared purpose and safe limits before it is issued.
One gate for every command.
The command gate enforces magnitude, rate, acceleration and duration. Every command expires. Policy is set per tenant and system class.
Shadow first.
A new agent proposes while the real controller acts. The two are compared before the agent has any say.
A person approves what moves a machine.
Levels per tenant and system class: observe-only, shadow, approved. Moving a machine takes a person's approval each time.
An advisory stop above the machine's own.
A supervisory stop cancels queued commands. The machine's own emergency stop and safety system remain the safety function.
Every class of target has a route.
The interface is the same for each. The integration underneath differs.
Joint states, inertial and odometry fields in; trajectories, setpoints and mode changes out.
Body state and gait telemetry in; velocity and mode commands out.
Controller variables and drive process data in; setpoints and trajectories out.
Odometry, battery and fleet state in; routes and speed limits out.
Telemetry and bus signals in; waypoints and mode out.
Machine bus signals and meters in; work limits and modes out.
Meters, controllers and monitors in; setpoints within declared limits out.
Events and state in; calls and messages out, inside a purpose.
Interfaces, integrations, runtimes, applications, tools.
One layer. Each runs the change in the twin first and asks before anything real happens.
The physical interface: kinds, purposes, system classes and actions. Documents cross it signed: batch, command, receipt, birth record.
Observe-only bus adapters and a sensor-pipeline record sink for the buses and middleware sites already run, with open formats and standard interfaces to the simulation tools, engines and models around them.
Secure, isolated environments where agents, models and jobs run, on the machine or in the fleet.
Robotics, machines, infrastructure, software and integrations: each field with its own route in.
Looper, Render, Twin and Programmer: they work inside the software you already use.
In production use.
These run for tenants today.
Scene generation, CAD and 3D conversion jobs run on the Ipnops fleet.
Body motion runs on Ipnops GPU workers.
Identity, data, vault and Programmer hosts serve sign-in and developer access.
The generation service serves vision, reasoning and speech models.
Twins admit measurements inside their solved bands.
Signed device readings flow through the head into the interface.
Kinds, purpose checks and admissions are live in production.
Bring an agent. Bring a machine.
Tell us the agent, the machine or program, and the interfaces involved. We scope the twin, the integration and the approval path with you.
