Robot software updates tested before deployment

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.

A blue industrial robot arm working on a factory line

One dependency update

One complete robot test

Fraeno check

Robot integration

Blocked
robot middleware 1.0.1 2.0.0
Code builds
Passed
Robot nodes start
Passed
Messages reach controller
Failed
Robot command output
0 Hz
Production GitHub App live
First target ROS 2 Humble
Current release v0.2.0
External test Passed in 1m 38s

A green build can still leave a robot standing still.

Robot software depends on packages, drivers, containers, launch files, and operating system libraries working together. A small update can compile cleanly and still stop messages, sensors, or commands at runtime.

Fraeno tests the old system against the new one.

Every update becomes a controlled comparison before it can reach the robot.

Current system Healthy
Controller receiving data
Sensor 20.6 Hz
Commands 20.6 Hz

The trusted version runs first and records the behavior that matters.

Updated system Communication lost
Controller waiting for data
Sensor still publishing
Commands 0 Hz

The new version builds, but the live comparison catches the broken message flow.

  1. 01

    Fraeno finds an update

    It opens a focused pull request with one reversible change.

  2. 02

    Both robot systems run

    The trusted version and the update start in clean, isolated environments.

  3. 03

    Real behavior is compared

    Fraeno checks the nodes, messages, services, diagnostics, and rates you declare.

  4. 04

    The pull request gets a clear answer

    The update passes or stops with the exact behavior that changed.

The code built. The robot stopped communicating.

A ROS 2 update changed how a sensor sent messages. The controller still expected the old delivery behavior, so it received nothing. The command output dropped from 20.6 Hz to 0 Hz.

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

View the production test
Behavior comparison Update blocked
Before After
Code builds Yes Yes
Messages arrive Yes No
Command output 20.6 Hz 0 Hz
Fraeno decision Do not merge

Narrow enough to trust. Useful enough to run today.

Fraeno is working first for ROS 2 Humble projects on Ubuntu 22.04 and amd64. The production GitHub App has passed a safe update, blocked a communication regression, and completed a fresh external repository test.

What it watches
Nodes, topics, services, actions, transforms, diagnostics, and message rates
Where it reports
On the pull request your team already reviews
What comes next
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.

Which robot software update are you afraid to make?

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

Install Fraeno