Supported Platforms
Operating System
The CTRL+R agent requires Ubuntu 18.04 or newer.
Android support is in development. The agent is an adapter layer rather than something tied to a single operating system, so we add new platforms as our customers' fleets require them.
ROS
The agent is compatible with both ROS 1 and ROS 2. On ROS 1 it targets Noetic. On ROS 2 the minimum is Foxy or newer, and for smoother operations we recommend Kilted.
ROS 2 is the fully supported path: movement, video, navigation, pose tracking, GPS position, and custom commands all work. ROS 1 covers movement, video, and navigation, but does not support pose tracking, GPS position, or custom commands. If your robot needs any of those three, run it on ROS 2.
Architectures
| Architecture | Example Hardware |
|---|---|
ARMv7 | Older embedded compute boards |
AArch64 | NVIDIA Jetson, newer Raspberry Pi models |
x86_64 | Standard desktop / server (Intel and AMD) |
Compatible Manufacturers
CTRL+R works with any robot exposing a ROS interface. The manufacturers below publish ROS drivers for their hardware, so they connect through the standard setup.
| Category | Manufacturers |
|---|---|
| Humanoid & legged | AgiBot, Unitree, Booster Robotics, Boston Dynamics, NEURA Robotics |
| Mobile & service robots | Clearpath Robotics, PAL Robotics, Keenon, Husarion, ROBOTIS |
| Industrial & collaborative arms | Universal Robots, KUKA, ABB, FANUC, Franka Robotics, Kinova, Denso, Mitsubishi Electric, Flexiv, igus, UFACTORY |
This is not a closed list. If your hardware exposes a ROS interface, it's very likely already compatible even if the manufacturer isn't named here.
Platforms We Integrate On Request
Some manufacturers ship a proprietary SDK or cloud interface instead of ROS. These aren't supported out of the box, but they're well within reach: we build an adapter for the vendor's interface and the robot then behaves like any other device on the platform, with the same controls, the same fleet view, and the same data capture.
Examples include PUDU and temi, the latter running on Android rather than Linux.
Get in touch. Custom integrations are a normal part of onboarding a fleet, not an exception to it.