On the device, any device.
Learning stays on it, with no network.
Reflex runs on the edge devices and robots you already have: controllers, gateways and smart cameras, and the flight, vehicle and bridge computers on board. On CPU, with no GPU and no cloud. It learns on the device itself, inside the bounds you set, and it never phones home.
- Learning on the device
- No GPU
- No cloud
- Offline and air-gapped
- Never phones home
- Licence works offline
Learning stays on the device, bounded, with no network.
One of the five guarantees, on every edge device and robot. It learns on the spot, on the machine itself, inside the bounds you set. No network, no cloud, no training run. What a controller, a gateway or a smart camera learns stays on it, under your control.
An inspector marks a new kind of scratch once, and the camera learns it on the spot.
Any device, on the CPU it already has.
Reflex is device agnostic. It needs no GPU of its own, so it runs on the processors your machines already carry: controllers, gateways and smart cameras at the edge, and the flight, vehicle and bridge computers on robots. Any accelerator stays free for your stack.
In a plant, it runs on the controller, beside its PLC program.
Beside your stack, on the same device.
Reflex works with your autonomy stack, not in its place: a VLA, an MPC, an autopilot, a PLC program or an AI agent. Your stack stays exactly as it is. They share the device: Reflex learns, plans, simulates and decides on the CPU, and every command passes the gate on its way to your stack.
The arm’s camera sees a part it was shown once this morning.
With or without a connection.
Reflex needs nothing outside the machine to start, to decide or to learn. It works offline and air-gapped, never phones home, and its licence works offline too. What it learns is yours, and it stays on your machines.
It needs nothing from outside the device to start.
One machine, or a whole fleet.
Each machine runs Reflex on board and decides for itself, link or no link. When there is a link, a fleet centre at a depot, a ship, a base or a ground station sends each task to the machine best suited to it. Each machine keeps its own rules, and a lesson moves between them only when you choose.
A survey of the north quay goes to the drone, the machine best suited to it.
Common set-ups.
Every deployment is planned with you, in a pilot on your own machines. Most start from one of these, with a little autonomy first.
Set-ups
- One machine, fully on board, with no connection
- A fleet, with a centre at a depot, a ship or a base
- Watched from a control room
- Long missions at sea, under water or in orbit
- Air-gapped, installed and licensed with no network
In every one
- The same five guarantees
- Above your safety systems
- Planned with you, in a pilot
A pilot runs on your own machines, with the stack you already run.
Run Reflex on the machines you have.
Reflex is in beta. What it has shown so far comes from simulation and benchmarks, and we prove it with you, on your machines, in a pilot.