Verified software directory

Robotics Software

Official tools for robot middleware, simulation, programming, planning, perception, SLAM, learning and data analysis.

Engineering selection guide

Choose robotics software by the job it owns in the stack

A long feature list is less useful than a clean interface boundary. Decide which software owns device drivers, messaging, simulation, planning, perception, localization, data, and deployment. Then verify version compatibility at each boundary.

Robotics software selection by engineering task
Engineering jobTypical tool classWhat to verify
Robot middlewareROS 2 / middlewareRobot and sensor drivers, DDS/QoS behavior, supported distro, real-time boundary, MCU bridge
SimulationGazebo, Isaac Sim, MuJoCo, Webots, CoppeliaSim, PyBullet, CARLAPhysics/contact needs, ROS 2, sensor models, GPU, synthetic data, headless CI, domain-specific assets
Motion & navigationMoveIt 2, Nav2, Drake and related plannersRobot geometry, collision scene, solver constraints, planning latency, controller interface
PerceptionOpenCV, Open3D, accelerated ROS perception stacksCamera/depth formats, calibration, GPU support, latency, model deployment, recording/replay
SLAMMapping and localization frameworksSensor modality, map scale, loop closure, relocalization, lifecycle, failure visibility
Data & learningLogging, datasets, visualization, robot-learning toolsTimestamp quality, schema, storage cost, replay, labeling, training/export path

A five-step compatibility check

01Write down the exact robot, sensors, controller, operating system, and deployment computer.
02Separate hard real-time motor and safety control from higher-level planning, perception, and AI.
03Verify official support for the ROS distribution, drivers, GPU stack, and operating-system version you will actually deploy.
04Test installation, logging, replay, fault recovery, and upgrades before building the full application around one tool.
05Record license obligations, commercial support, release cadence, and the exit path if the project becomes unmaintained.

24 verified results

Robot offline programming

ABB RobotStudio

Verified source

Developed by ABB

ABB RobotStudio provides simulation, virtual controller and offline programming workflows for ABB robots.

Free and paid options

Last verified:

Simulation

CARLA

Verified source

Developed by CARLA project

CARLA is an open-source simulator for autonomous driving research with configurable towns, sensors and traffic actors.

Open source

Last verified:

Simulation

CoppeliaSim

Verified source

Developed by Coppelia Robotics

CoppeliaSim is a general-purpose robot simulation platform with scripting, remote APIs and multiple physics engines.

Free and commercial editionsROS 2

Last verified:

Robot motion planning

Drake

Verified source

Developed by Toyota Research Institute

Drake is a toolbox for modeling, planning and control of robotic systems with optimization and multibody dynamics.

Open source

Last verified:

Robot data platforms

Foxglove

Verified source

Developed by Foxglove

Foxglove provides visualization, logging and data-management tools for robotics development and operations.

Free and paid optionsROSROS 2

Last verified:

Simulation

Gazebo

Verified source

Developed by Open Robotics

Gazebo is an open-source robot simulator with physics, sensors, rendering and integration tools.

Open sourceROS 2

Last verified:

Robot data platforms

LeRobot

Verified source

Developed by Hugging Face

LeRobot is an open-source library and data ecosystem for robot learning models, datasets and training workflows.

Open source

Last verified:

Robot operating systems

micro-ROS

Verified source

Developed by micro-ROS project

micro-ROS brings selected ROS 2 concepts and APIs to microcontrollers, connecting resource-constrained firmware to a ROS 2 graph through an agent and embedded middleware.

Open sourceROS 2

Last verified:

Robot motion planning

MoveIt 2

Verified source

Developed by MoveIt project

MoveIt 2 is a ROS 2 framework for motion planning, manipulation, kinematics and collision checking.

Open sourceROS 2

Last verified:

Simulation

MuJoCo

Verified source

Developed by Google DeepMind

MuJoCo is an open-source physics engine designed for model-based control, optimization and robotics research.

Open source

Last verified:

Robot motion planning

Nav2

Verified source

Developed by Open Navigation project

Nav2 provides planning, control, recovery and behavior-tree tools for mobile robot navigation in ROS 2.

Open sourceROS 2

Last verified:

Robotics AI

NVIDIA Isaac Lab

Verified source

Developed by NVIDIA

Isaac Lab is an open-source framework for robot learning, reinforcement learning and simulation workflows built on Isaac Sim.

Open sourceROS 2

Last verified:

Open-source and commercial software

Open-source tools expose code and community workflows. Commercial tools may provide vendor support, certified robot libraries, proprietary solvers or deployment features. The license label in each record comes from the official project or vendor.

ROS and ROS 2 compatibility

A ROS label means the developer publishes a documented integration or package. It does not mean every feature works on every ROS distribution, operating system or robot controller.

Official downloads only

Download buttons point to vendor pages, official repositories, package documentation or official release pages. The directory excludes mirrors, republished binaries and shortened links.

Hardware and operating-system requirements

Simulation, perception and AI tools can require specific GPUs, drivers or operating-system versions. Review the official installation guide before selecting software for a robot or workstation.

Frequently asked questions

How should teams choose robotics software?

Start with the robot hardware, operating system, real-time requirements, supported sensors, programming languages and the vendor or community support needed for deployment.

Is open-source robotics software always free to deploy?

The code may be open source, but integration, hardware, cloud services, safety validation, maintenance and engineering time still create costs.

What is the difference between simulation and offline programming?

Simulation models robot behavior and environments. Offline programming focuses on creating and validating production robot programs away from the physical cell. Some tools support both.

Why does ROS 2 compatibility matter?

ROS 2 compatibility can simplify messaging, drivers and tooling, but it does not guarantee support for a specific robot, sensor or production safety requirement.

Guide updated: August 12, 2026. Software records retain their individual verification dates; license and compatibility labels are based on official project or vendor documentation.

Explore the connected robotics directories

ROBOTICS RESEARCH

Go deeper intorobotics

Independent coverage of humanoid robots, Physical AI, industrial robotics, robot hardware and emerging automation systems.

Open the latest technical analysis, robot directories, and deployment guides built around measurable engineering decisions.

service@techniahqservice.com