ABOUT US
We build the software that lets robot fleets run themselves.
SUM Innovation makes SwUM: fleets of robots and drones split a goal into jobs, agree who does what, do each job once, prove it and learn from it. No central server, and no reliable network required.
WHY WE EXIST
Fleets should not stop when one link does.
Today almost every fleet of robots and drones depends on one controller and one network link. When either fails, every machine waits, jobs get done twice or not at all, and the only record of the work is the vendor’s own log.
We think coordination belongs on the machines themselves, and that the work should be provable by anyone, not just by whoever sold the robots.
What we build.
SWUM
Swarm coordination for physical AI. Machines share what they know with their neighbors and agree on who does each job, with no server in the loop.
THE RAILS
SUM Chain records finished work, SNIP stores the data, OmniNode runs the models and RUMUS trains them, all in Rust.
WHO IT IS FOR
Teams that run fleets: factories and warehouses first, then defense, then farms, mines and construction.
HOW WE GOT HERE
We built the rails first.
Before SwUM, we built the infrastructure it needs. We went from the first line of code to a live network in eight months, without raising a dollar from anyone.
SwUM came next. Its specification proves thirteen results and passes all thirty-three of its numerical checks, and an early prototype runs in Gazebo simulations, where simulated robots split a goal into jobs and coordinate with no central server.
PROOFS & SPEC →WHAT EXISTS TODAY
Live, and checkable.
10M+
BLOCKS ON SUM CHAIN
8
MONTHS TO A LIVE NETWORK
202
STARS ON RUMUS
$0
RAISED FROM OUTSIDE
AS OF NOVEMBER 2026 · VERIFY: EXPLORER.SUMCHAIN.IO →
WHO WE ARE
Two founders. No outside capital.
One of us is a systems engineer and mathematician who wrote SUM Chain from an empty repository and built RUMUS, our Rust training framework. The other is a product and data leader who has shipped more than thirty data products to over a thousand users.
We are one hundred percent founder owned, and everyone on the team writes code that runs in production.
HOW WE WORK
Three habits we keep.
01
Prove it before we ship it
The rules that keep a swarm safe are theorems with numerical checks, written down before any code.
02
Build it in the open
Our ledger is public, our explorer is public, and RUMUS is open source. Anyone can check our work.
03
Rust down to the robot
Rust first, then C and assembly where the hardware needs it. No Python anywhere in SwUM.
CONTACT
