ROS 2 in custom manufacturing: connect the machines, not the whole sale

External-source research synthesis, not an OfferSignal client result. Based on the retained October 2026 research and source-specific dates.

A high-mix workshop may know its machines well while still lacking a reliable way to expose current capability to a buyer or quoting process. The difficulty is not simply connecting robots. It is keeping machine identity, drawing revision, tooling, capacity, permissions and safety status aligned before anyone promises a job.

What ROS 2 provides

ROS 2 is an open-source set of libraries and tools for robot applications, not a product catalogue, configure-price-quote system, enterprise resource planning platform or service-management product. Its practical role is a typed communications and runtime layer between drivers, sensors, controllers, planners, fleet services, human-machine interfaces and supervisors. Lyrical Luth was initially released on 22 May 2026, followed by public patches on 23 June and 7 August. That is release evidence, not an industrial performance result; one Jazzy entry also contains a malformed date. 1 2 3

The project has formal governance: the Open Source Robotics Alliance has governed ROS 2 since 2024, while the ROS Project Management Committee handles repository management, reviews, maintenance and technical direction. This does not make every third-party driver or package equally supported. A production team should pin a distribution, package versions and a tested build, checking maintenance, licensing, compatibility and security response package by package. 4

Capability needs identity and authority

ROS 2 topics, services, actions, parameters and standard messages can publish observed state, health, command surfaces and capability metadata. ros2_control adds hardware interfaces and controllers for real-time robot control. These mechanisms can expose supported joints, controller state, modes, limits and faults when the hardware abstraction is correct. They do not determine whether a machine can make a custom part from an approved drawing, has the required tooling, meets a tolerance or has capacity on a requested date. 5 6

SROS2 adds DDS-Security through participant identities, signed governance and permissions files, and authenticated encryption. Permissions can restrict participants to domains and topics. Security is disabled by default, however, and permissive behavior applies when security files are absent; strict enforcement must be selected. Key custody, rotation, revocation, enclave mapping, segmentation, endpoint hardening and incident procedures remain integrator responsibilities. 7 8

Managed lifecycle nodes provide an equipment boundary: a supervisor can keep a node unconfigured or inactive until checks pass, then activate, deactivate, recover or replace it. That supports validation, reservation, human approval, activation and monitoring. It is not a business approval system, electronic signature, safety case or proof that a process is safe. 9

Orchestration is not quoting

Open-RMF describes multi-fleet robot management, facility and workcell adapters, and support for ROS 2 distributions including Humble, Jazzy, Kilted and Rolling. Its repository warns that nightly images may break and recommends a pinned, verified image hash. Open-RMF can coordinate technical resources; it is not a supplier directory, RFQ or quote engine, contract system, invoicing platform or maintenance CRM. 10

ROS-Industrial adds industrial hardware, tools, applications, testing, documentation, support and training. The reviewed pages provide no independently audited revenue, throughput, quote-win, uptime or aftersales result attributable to ROS 2. The evidence supports technical enablement, not commercial success. 11 12

Security is a material limit. An older Alias Robotics red-team study used six Universal Robots CB3.1 robots in a synthetic ROS-Industrial environment across five network levels. It reported four attack groups; all compromised the ROS computational graph, and all but one took control of most endpoints under the study’s assumptions. This is not a current ROS 2 production benchmark and cannot be generalized numerically to Lyrical. It does show how weak identity and permissions can lead to manipulated graph traffic, endpoint compromise and unauthorized commands. 13

An illustrative custom-work architecture

For a no-SKU workshop, an illustrative deployment would keep authoritative records in product lifecycle management, enterprise resource planning, manufacturing execution, quality or customer systems. ROS 2 would carry versioned projections: customer and project identity, drawing and revision references, quantities, material, tolerances, process constraints, delivery window, permissions, status, reservations, telemetry and approval events.

A deterministic service should join those references to approved machine capability, tooling, calibration, certification, maintenance state, capacity and lead-time assumptions. The chain remains: authenticated lookup and revision check; capability and capacity validation; human authority for exceptions, price and offer approval; then external quote, contract, order, production, quality, invoice and aftersales records. ROS 2 does not prove the underlying records or solve currency, tax, Incoterms, sanctions, export controls, certification or warranty obligations.

Test unit and coordinate-frame mismatches, stale revisions, incompatible materials, unavailable machines, expired calibration, restricted drawings and stale prices. Measure eligible requests, validation errors, approved quotes, on-time orders, first-pass quality, uptime and service-resolution time. The retained research found no verified public denominator for ROS 2 custom-work revenue, quote conversion, lead-time reduction, defect rate, uptime or aftersales resolution. A 2025 academic ROS 2 framework demonstrates modular services, simulation and monitoring, but is a research implementation rather than a customer production result. 14

Sources and next reading

ROS 2 main repository · ROS 2 releases · SROS2 · ros2_control · Open-RMF · ROS-Industrial

Explore OfferSignal · Focused Business & AI Workshop · All research

References