OhhO Frame
The robot software stack, pre-wired. Docker, ROS 2, simulation, CI/CD and multi-machine deployment — a production-grade foundation you launch in an afternoon instead of assembling over months.
Your robot stack, ready in one afternoon.
Every robot project starts by rebuilding the same plumbing: a ROS 2 workspace, Docker images, a simulator, message buses, launch files, a CI pipeline. OhhO Frame gives you all of it, already wired together and known-good.
Frame is the chassis your robot's software rides on. It ships the workspace layout, containerized build, Gazebo and Isaac simulation, and single- or multi-machine deployment — robot plus GPU workstation — that the rest of the OhhO products plug straight into.
Built in the open on ROS 2 Jazzy, Frame is the same foundation that powers OhhO's own reference robot — so what you start from is a real, tested production stack, not a toy template.
- Batteries-included workspace. Driver, description (URDF), navigation, perception and bringup packages laid out the way a production robot needs them.
- Containerized everything. Docker images and a DevContainer so 'works on my machine' becomes 'works on every machine' — including CI.
- Simulate before you build. Gazebo Harmonic and Isaac Sim worlds wired to the same topics as the real robot, so you develop with no hardware. Robot description uses URDF and SDF; Isaac Sim scenes use USD (Universal Scene Description) — the same 3D standard Pixar, Omniverse and the digital twin industry settled on.
- MCAP recording. Frame records ROS 2 data in MCAP — the open-source, ROS 2-native bag format — so your logs interoperate with the wider ROS 2 ecosystem's tooling, not a proprietary format.
- CI/CD out of the box. A GitHub Actions pipeline builds the workspace and runs the test suite on every push.
- Single or multi-machine. One configurator switches between all-on-one-workstation and Pi-robot + GPU-desktop topologies, wiring DDS peers for you.
Related: OhhO Build, OhhO Bench, OhhO Fleet, OhhO Connect