Robotics & autonomous systems

Eldric on the robot,
not in the cloud.

Mobile robots, AGVs, inspection drones, autonomous boats and unmanned platforms. Eldric carries the kernel on-board so perception, voice command, and recovery decisions keep working when the radio link drops. Soft real-time, edge-deployed, no cloud dependency.


Why on-device

The link will drop. The robot still needs to think.

A factory AGV behind a steel rack. An inspection drone inside a turbine hall. A pipeline crawler in a steel pipe. A maritime vessel below deck. The shared property: the radio link is intermittent or absent, and the robot still needs to perceive, decide, and act.

On-device perception

Camera frames, LiDAR scans, IMU streams flow through native inferenced. Object detection, anomaly detection, classification run on the robot's compute box — no round-trip to a base station.

Voice command

STT in, command parsed, action executed, TTS out — all on board. Useful for inspection crews talking to drones, factory operators directing AGVs, field technicians driving service robots.

xLSTM forecasting

The xLSTM forecasting workload handles trajectory forecasting, motion planning, and recovery-policy execution on time-series sensor data. Linear in sequence length — a better fit than transformers for hours-long telemetry windows.

Store-and-forward

The IoT worker buffers telemetry locally during disconnect windows and replays to fleet HQ when the link returns. No lost frames, no lost events.

Edge deployment

Runs on a Pi 4, an industrial gateway, a Jetson, or any Linux compute box on the robot. Same binary as the data-centre Eldric; only the activated modules differ.

Recovery decisions

When the link drops, a pre-loaded policy can drive the robot to a safe state. When the link returns, the fleet HQ reconciles. Soft real-time at the line; hard real-time stays the motor controller's job.


Target platforms

Robots Eldric already runs on.

Mobile industrial robots

AGVs, AMRs, factory floor delivery, parts pickers. Eldric ties into the IoT worker for OPC-UA / Modbus / MQTT, then runs perception + decision locally. Soft real-time tag-to-action on the demo cluster.

Inspection drones & crawlers

Aerial inspection drones (turbine halls, transmission lines), pipeline crawlers, sewer-inspection rovers. Long disconnect windows. xLSTM forecasting tracks link-quality trends in the telemetry to pre-stage a recovery path ahead of a likely disconnect.

Service robots

Hospital delivery robots, hotel concierge bots, retail floor assistants. Voice-in / voice-out, knowledge-base lookup (the duty roster, the policy manual), and the AI inbox to escalate to a human when needed.

Autonomous vehicles & vessels

On-board inference for ADAS-adjacent workloads, fleet-level forecasting, voice interface for operators. Hard real-time control stays with the dedicated controller; Eldric handles the cognitive layer above it.


On-device simulation

Roll the physics forward — on the robot's own CPU.

Beyond perception and control, Eldric can run compact simulation models that roll a known physical system forward step by step, on an ordinary CPU — small enough for a Raspberry Pi, no GPU and no network. A control policy for a 6-axis arm that drives the joints toward a target; the motion of a modelled mechanism rolled forward for on-board what-if. Each is a simulation of a known model, faithful over a bounded window.

What this is — and isn't. A simulation rolls the modelled physics forward; it does not predict a real-world event, and it is not autonomous control. Fidelity holds over a bounded window and then drifts — that's the nature of the method, stated plainly.

Download the compact CPU demo models →


Honest scope.

What Eldric does NOT do on a robot:

What it does well: the cognitive layer of an autonomous platform — perception, voice, decision-making, telemetry summarisation, fleet-level coordination — all on the robot, with sane degradation when the link to base drops.