We're looking for pilot partners running real robot cells.Learn more

Orange humanoid robots sorting parcels along a warehouse conveyor line

Understand the behavior of any robot in real time.

Decisions

A robot makes thousands of decisions a shift.

Complexity

Understanding how a robot thinks is complex, iterative and time‑consuming.

Clarity

That's where Momentum comes in.

See how it works

Decisions

A robot makes thousands of decisions a shift.

Complexity

Understanding how a robot thinks is complex, iterative and time‑consuming.

Clarity

That's where Momentum comes in.

See how it works

Every run carries its own evidence. Every failure arrives with its cause attached.

4
SDK entry points: task, decision, controller_switch, fault
1
required dependency: opentelemetry-api
0
changes to your robot's control logic

How it works

An open convention.
An easy to use SDK.
An engine that never forgets.

SDK

Up and running before your coffee's cold.

Add momentum.* calls next to the code you already have. We handle the serialization, the attribute naming, the span lifecycle: you keep total control over what your robot actually does.

pick_and_place.py
import momentum_sdk as momentum

# Root span — the task the robot was asked to perform
with momentum.task("pick_and_place", goal=str(target)):

    with tracer.start_as_current_span("skill.grasp"):
        result = grasp_selector.run(point_cloud)
        momentum.decision(
            type="grasp_selection",
            inputs={"object_id": object_id,
                    "confidence": result.confidence},
            output={"grasp_id": result.id},
        )
        momentum.controller_switch(
            from_mode="position", to_mode="impedance",
            reason="contact_detected",
        )
        arm.execute_grasp(result)

The value curve

Useful in the first hour.
Smarter every month after.

  1. Hour one

    Drop in a recording of a failed run

    run_4412.mcapno code changes

    ✗ Diverges from run #4411 at grasp_selection

    confidence dropped 0.91 → 0.62

  2. Month one

    Your engineers confirm each diagnosis

    Root cause: grasp_selection✓ confirmed

    Remembered, so the next similar failure is recognized in seconds

  3. Month six

    Ask questions across your whole history

    “Why do picks fail on line 2?”

    14 of 17 failures happened below 220 lux, vs 2 of 41 above.

Stop debugging robots in the dark.

Get in touch. We'll walk through what Momentum sees: the decision that went wrong, and the hardware response that gave it away.

Contact us