# RoboStacker: describe your robot, get a ROS 2 stack and a workspace to build (feedback welcome)

**URL:** <https://discourse.openrobotics.org/t/robostacker-describe-your-robot-get-a-ros-2-stack-and-a-workspace-to-build-feedback-welcome/58579>\
**Category:** Projects\
**Tags:** release, ros2\
**Created:** [October 5, 2026, 12:13am UTC](https://discourse.openrobotics.org/t/robostacker-describe-your-robot-get-a-ros-2-stack-and-a-workspace-to-build-feedback-welcome/58579 "2026-10-05T00:13:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lenprovo](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/lenprovo/32/35613_2.png) [@lenprovo](https://discourse.openrobotics.org/u/lenprovo)\
**Post date:** [October 5, 2026, 12:13am UTC](https://discourse.openrobotics.org/t/robostacker-describe-your-robot-get-a-ros-2-stack-and-a-workspace-to-build-feedback-welcome/58579/1 "2026-10-05T00:13:51Z")

</div>

Hi everyone,

I’ve been building **RoboStacker** ([https://robostacker.app](https://robostacker.app)), a free tool that helps you plan the software for a ROS 2 robot, and I’d love to hear from people at every level, from a first robot to a production fleet.

You describe your robot: its base, sensors, computer and what it should do. RoboStacker gives you:

- the ROS 2 packages it needs, in the order to bring them up
- the pieces still to add, like an odometry source for the EKF, a map for Nav2, or a sensor frame
- a workspace to download, with the robot model (URDF/xacro), ros2\_control, EKF, Nav2 settings and launch files

It covers warehouse robots, outdoor rovers (skid-steer and Ackermann), drones (PX4/ArduPilot companion computer) and robot arms (beta), on Humble and Jazzy. Every generated robot is built and tested automatically on each change, and the wheeled ones are driven through Nav2 on simulated motors.

It’s free, and you don’t need an account to plan or download.

I’d love to hear:

1. Was anything unclear, or where did you get stuck?
2. If you downloaded a workspace, did colcon build work for you?
3. Did it miss anything for your robot?
4. What would make it more valuable and useful for you? I’m exploring ideas like a Gazebo simulation of your exact robot, ready configs for common motor controllers, or a check-up script that compares your running robot to its plan. New ideas are very welcome!

Thanks for taking a look. Happy to answer any questions here!