UBRobotics · Lisbon
Give any machine a goal.
UBR builds the field brain — a device that mounts on vehicles, robots and gear built before autonomy, takes a goal, and works it onboard. Even when signal, positioning and cloud access fail.
01 — The world breaks first
Signal drops.
Positioning drifts.
Cloud access goes.
02 — And the goal still stands
The machine carries on.
03 — The device
A field brain for machines built before autonomy.
One unit — compute, sensors, comms — that fits the machine you already run. You state the goal once. It does the rest, onboard.
-
Goal
Goal in, work out
Small language models run on the device itself. A goal in plain language becomes a plan the machine executes — adapt, retry, continue — with no server in the loop.
-
Sense
Senses like it’s 2026
Cameras, GNSS-denied positioning, environment sensors: a modern perception kit for gear that never had one.
-
Link
Cut off, still on task
LTE when it’s there, LoRa mesh when it isn’t, nothing at all when it comes to it — the goal survives the link. It reports back when the world returns.
In development — first units ride our own testbeds.
04 — What it rides
Vehicles. Robots. Old gear.
If it can be commanded, it can carry the brain. Today that’s our own testbeds — a tracked field platform, a facade rig, a rooftop cleaner. The point is what it rides next: the machines you already own, doing their job without you on the radio.
05 — The system
One console. Every brain.
The field brain wakes one machine up. The system is what commands the many: one operator, one goal, a mixed fleet that divides the work and reports back.
-
Task
One goal, many machines
State the goal once. The system splits it across the fleet — who searches, who carries, who relays — and re-plans as the field changes.
-
Fleet
Mixed by design
Ground robots, drones, fixed sensors and the people alongside them: one picture, one tasking queue, on whatever link survives — LTE, mesh, or a few bytes a second.
-
Open
Ours or not
The console commands any brain that can hold a goal. UBR field brains are first-class; autonomy we didn’t build plugs into the same tasking.
Open the operator console — GCS →
Concept console · simulated mission — the map behind this page is the same system.
06 — Inside the unit
Most machines quit when the infrastructure does. Yours won’t.
Five layers in one unit — perception, autonomy, comms, control, operator — the same brain on every machine it rides. Designed from the failure case backwards.
-
Perception
Sees on its own
Perception runs onboard, at the edge — no inference round-trip to a server, no dependency on a link that may not exist.
-
Autonomy
Keeps the goal
The goal is held on the machine, not in the cloud. When the link goes dark, it continues the task instead of stopping to wait for orders.
-
Comms
Degrades gracefully
LTE when it’s there, LoRa mesh when it isn’t. Command and telemetry survive on whatever bandwidth is left — down to a few bytes per second.
-
Control
Moves as one team
A coordination layer keeps a mixed team — machines, sensors and the people alongside them — working as one, even when GNSS and cloud are denied.
-
Operator
Answers to a human
Command interface, telemetry, maps and mission state on whatever screen the field allows. Operators decide; machines do the dangerous part.
UBR field brain — built for field operations · dual-use by design
07 — Proof · Field notes
Latest from the field.
What was tested, what broke, and what gets tested next — shared as it happens, not polished after.
Tell us which machine to wake up.
If you run machines that go quiet when the network does — emergency response, critical infrastructure, defence — talk to us before the rest of the market catches on.