Where to start

Check our work

If you're investing

← INDUSTRIES

FACTORIES & WAREHOUSES · NOW

One dispatcher. Many vendors. No single point of failure.

Mixed-vendor fleets today run through one fleet manager over one Wi-Fi link. SwUM lets the robots agree among themselves over one-hop radio, so the floor keeps moving when the link or the manager drops, and every finished job carries a proof that no vendor log can give.

1,000,000

ROBOTS AMAZON ROUTES THROUGH ONE CENTRAL TRAFFIC MODEL

3.0

VDA 5050, ADOPTED FEBRUARY 2026, STILL VEHICLE-TO-MANAGER ONLY

100

ROBOTS PER SWARM IN THE FIRST RELEASE

1,000,000 · EWEEK, JULY 2025

VDA 5050 3.0 · VDMA AND VDA, FEBRUARY 2026, VIA BLUEBOTICS AND IDEALWORKS

100 · SWUM SPEC V0.2, DECISION D9

The link can drop. The floor keeps moving.

NO FLEET MANAGER NEEDED

Robots split a goal into a job tree and bid for its leaves over one-hop radio. Nothing waits for a server.

DONE ONCE

Every beacon carries the set of finished jobs, so no robot repeats work another one completed. Exactly one robot starts each job.

PROOF PER JOB

Each finished job is a signed 196-byte record, bundled and anchored on SUM Chain. A customer can check it without trusting any vendor.

WHY IT FITS

Standards stop at the fleet manager.

VDA 5050 describes the link between a vehicle and a fleet manager, and version 3.0 still has no robot-to-robot coordination. ROS 2 discovery floods Wi-Fi at fleet scale. SwUM needs one hop to a neighbor and one radio frame per beacon, and it runs on a microcontroller beside the vendor’s own controller.

SwUM: no controller, no single link Today every fleet hangs on one controller and one radio link, so when either fails every machine stops; with SwUM each machine talks only to neighbors within radio range, there is no central coordinator, and information crosses the swarm by repeated one-hop broadcast. TODAY SWUM ONE LINK Controller ONE HOP NO CENTRAL COORDINATOR NO CONTROLLER · NO RELIABLE NETWORK NEEDED

WHAT CHANGES

Mixed vendors, one shared view.

Each robot keeps the same replicated state: which jobs are done and who claims which. The merge rule is commutative, associative and idempotent, so robots from different vendors converge to one view even when frames are delayed, repeated or lost.

The vehicle controller is treated as a device that accepts velocity or waypoint commands, so SwUM sits beside existing drive stacks rather than replacing them.

THE PILOT

Five to ten robots, two job kinds, pass marks set now.

The first paid pilot runs on a factory or warehouse floor with 5 to 10 robots and two real job kinds. It passes or fails on numbers agreed before it starts: no double starts in 10,000 or more, no duplicate credit in any scenario including partitions, and an allocation worth at least 0.95 of greedy on average.

WHAT YOU GET

Job tree A signed goal becomes tasks and subtasks, up to 1,024 leaves per goal.
Allocation Bidding converges to the greedy assignment within (K-1)D, worth at least half the optimum. Theorem 5.
Proof of completion Bundle hash on SUM Chain, episode data on SNIP, checkable by the customer.
Learning Idle robots train on their own outcomes, and the better models flow back at the next epoch.
Radio Class S (802.15.4), M (ESP-NOW, LoRa) or L (Wi-Fi mesh). Dense floors use class M or L.