Fraeno check
Robot integration
- Code builds
- Passed
- Robot nodes start
- Passed
- Messages reach controller
- Failed
- Robot command output
- 0 Hz
Robot software updates tested before deployment
Fraeno automatically manages and updates robot software dependencies, and tests the complete robotic system before changes are deployed.
essentially, dependabot for robots + integration testing.
One dependency update
One complete robot testFraeno check
Why Fraeno exists
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.
How it works
Every update becomes a controlled comparison before it can reach the robot.
The trusted version runs first and records the behavior that matters.
The new version builds, but the live comparison catches the broken message flow.
It opens a focused pull request with one reversible change.
The trusted version and the update start in clean, isolated environments.
Fraeno checks the nodes, messages, services, diagnostics, and rates you declare.
The update passes or stops with the exact behavior that changed.
A real failure caught
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 testReady now
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.
A passing result means the configured target and declared probes passed. It does not claim that every possible robot behavior is safe.
Fraeno is opening its first pilot
We will help turn that failure risk into a repeatable integration test.
Install Fraeno