Skip to main content
Version: 10

Deployment, Commissioning, and Fleet Management

MoveIt Pro provides a robust platform for deploying and operating production-grade robotic systems. It is designed to take your robots from development to real-world environments with reliability, flexibility, and ease of maintenance. Below is a high-level overview of how MoveIt Pro supports robot commissioning, robot deployment, fleet management, and operator interaction in production environments.

Software Deployment​

MoveIt Pro is built for scalable, resilient software deployments. The MoveIt Pro Runtime is Dockerized, allowing customers to deploy and update systems easily using hardened, tested virtual environments. These Docker containers share access with the host system for real-time hardware interfaces, network communications, and file systems.

MoveIt Pro uses multiple Docker images for its Runtime, enabling a distributed, optionally multi-machine architecture. Real-time control processes can be isolated on a dedicated machine or CPU core, separate from your GPU loads. High-level logic and planning processes can operate on a separate machine for optimized performance. Computationally intensive tasks (e.g., GPU-enabled machine learning inference) can be offloaded to specialized hardware nodes.

MoveIt Pro leverages the popular ROS 2 communication framework to provide flexible network-wide communication between components via topics, services, and actions. Customers often run additional Docker containers alongside MoveIt Pro for supporting tasks like Operator HMIs (Human-Machine Interfaces) and PLC (Programmable Logic Controller) integrations. Using ROS isn’t necessary, however, thanks to our SDK.

For scaling to larger deployments, we recommend using a system configuration management tool like Ansible to manage your installation and updates reliably across multiple systems. To wire releases through to your fleet automatically, see Set Up CI/CD.

Robot Commissioning​

MoveIt Pro uses a concept called a robot_config, a ROS package that contains all critical configuration information for a robot, including:

  • Hardware-specific settings (e.g., IP addresses, serial ports)

  • Robot description files (kinematics, motion planning settings, collision geometry)

  • Calibration files (kinematic and sensor calibration)

  • MoveIt Pro Objectives (Behavior Trees and custom Behaviors)

One key feature is that robot_configs can inherit from other robot_configs, making it easy to manage fleets of similar robots. You can maintain a common base configuration while customizing only specific parameters like individual serial numbers, calibration settings, or hardware-specific ports.

Fleet Management​

MoveIt Pro’s architecture is designed with remote operations in mind. You can place robots behind a VPN or other trusted tunnel, then connect to them with the MoveIt Pro desktop app. We recommend Tailscale for a lightweight solution.

For full-featured fleet management, we recommend integrating with our partner Formant. MoveIt Pro's ROS 2 and SDK interfaces also support fleet tools that you build in-house.

Operator HMI​

MoveIt Pro offers multiple options for building user-facing interfaces:

  • ROS-native communication allows integration with any ROS-based tools.

  • MoveIt Pro desktop app provides the standard operator interface for self-hosted deployments. MoveIt Pro Cloud remains available in a browser, but it is simulation only and cannot be connected to robot hardware, so it is not a deployment option.

  • Custom applications connect through the native ROS 2 client libraries (rclpy, rclcpp).

  • UI-independent operation is fully supported, enabling deployment with your own custom Operator HMI solutions.

Through these flexible options, MoveIt Pro ensures that your operators have the tools they need to run, monitor, and maintain robot systems safely and efficiently.

Long Term Support (LTS) Releases​

MoveIt Pro follows a structured release cycle designed to balance innovation with stability for production deployments:

  • Minor releases are delivered every 2 to 4 weeks, providing new features, improvements, and bug fixes.

  • Major releases are delivered every 3 to 6 months, introducing significant new capabilities and architectural improvements.

  • LTS coverage lasts 1 year for the last minor release version of every major release. This includes critical bug fixes and security patches to ensure production stability.

  • For customers who need more than 1 year of LTS, we can discuss custom support options tailored to your specific requirements.

Example: v7.9.0 is the last release before we announce v8.0. We will provide bug fixes for v7.9 with patch releases for 1 year, ensuring customers have a stable foundation for their production systems while we continue developing v8.x features.