MoveIt (ROS 1)
- Software
- Robot arms and industry
- Framework
MoveIt is an open-source motion planning framework for ROS 1 used to build, prototype, and benchmark robot manipulation applications.
- Discontinued
- Moved
Source on GitHub: github.com/moveit/moveit (opens in a new tab). Facts read at commit fdb79ac (opens in a new tab).
Licenses
- Code
- BSD-3-Clause (opens in a new tab)
Read by Robotheca from LICENSE.txt (opens in a new tab) (BSD-3-Clause) at commit fdb79ac (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Yes
Labels
- DiscontinuedEnded on 31 May 2025: MoveIt for ROS 1 runs only on ROS 1, whose last release (Noetic) reached its end of life on 2025-05-31. Its repository still receives occasional changes (the last on 2026-07-20).
- MovedMoved to MoveIt 2.
What it does
- Provides a platform for developing manipulation applications on robot arms within ROS 1.
- Supports prototyping robot designs and benchmarking motion planning algorithms.
- Development of new features happens on the master branch, while the *-devel branches hold stable releases for specific ROS distributions.
- Bug fixes are occasionally backported to the released *-devel branches.
- The ROS 2 counterpart is maintained separately as MoveIt 2.
Written by Robotheca from the project's README (opens in a new tab) at commit fdb79ac.
Getting started
- Difficulty
- Advanced
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Discontinued: its makers have ended it
- Newest commit
- 20 Jul 2026 on master
- Latest release
- 1.1.11 (9 Jan 2023)
- Discontinued
- Ended on 31 May 2025: MoveIt for ROS 1 runs only on ROS 1, whose last release (Noetic) reached its end of life on 2025-05-31. Its repository still receives occasional changes (the last on 2026-07-20). Source: discourse.openrobotics.org/t/ros-noetic-end-of-life-may-31-… (opens in a new tab)
- Moved
- Its successor or new home: MoveIt 2.
Checked on GitHub on 16 Oct 2026.
Links
Robots on Robotheca that use it
No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.
Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.