Built first for ROS 2 Humble

Update robot software without breaking the robot.

Fraeno automatically manages and updates robot software dependencies, and tests the complete robotic system before changes are deployed.

essentially, dependabot for robots + integration testing.

Fraeno check

Robot integration

Blocked
robot middleware 1.0.1 2.0.0
Build
Passed
ROS graph
Observed
QoS contract
Incompatible
Robot command rate
20.6 Hz 0 Hz
The code built successfully. Fraeno still blocked the change because the running robot system stopped communicating.

A green build does not mean the robot still works.

Robot software crosses ROS packages, operating system libraries, containers, hardware drivers, and launch files. A small update in one layer can quietly change the whole system.

One update becomes one controlled test.

  1. 1

    Fraeno finds a dependency update

    It opens a focused pull request so the change is easy to review and reverse.

  2. 2

    The old and new systems both run

    Your trusted test plan starts each version in a clean environment.

  3. 3

    Fraeno compares real behavior

    It checks the interfaces and signals that matter to the robot.

  4. 4

    The change passes or stops

    The pull request shows what changed and why Fraeno accepted or blocked it.

The build passed. The robot stopped communicating.

A test update changed how a ROS 2 sensor published messages. The controller still required reliable delivery, so it received nothing. The command topic fell silent and diagnostics worsened.

Fraeno saw the running system change and blocked the pull request.

Before the update Healthy
Code builds Yes Yes
Messages reach controller Yes No
Robot command rate 20.6 Hz 0 Hz
After the update Blocked

A working vertical prototype with a narrow first target.

Fraeno has already run a complete check through its production GitHub App. A safe update passed. A buildable ROS 2 communication regression was blocked.

First target
ROS 2 Humble on Ubuntu 22.04 and amd64
Current proof
A separate ROS 2 repository using the production GitHub App
Next proof
A design partner running Fraeno on a real robot repository

A passing result means the configured target and declared probes passed. It does not claim that every possible robot behavior is safe.

Tell us which robot software update you are afraid to make.

We will help turn that failure risk into a repeatable integration test.

View the GitHub App