domain_bridge
- Software
- Middleware
- Tool
A ROS 2 bridge that relays ROS communication between different ROS domain IDs, configured by YAML, launch arguments, or a C++ library.
Made by ROS 2.
Source on GitHub: github.com/ros2/domain_bridge (opens in a new tab). Facts read at commit 75cdfae (opens in a new tab).
Licenses
- Code
- Apache-2.0 (opens in a new tab)
Read by Robotheca from LICENSE (opens in a new tab) (Apache-2.0) at commit 75cdfae (opens in a new tab), on 16 Oct 2026.
- Commercial use
- Yes
What it does
- Bridges ROS topics, services and actions between separate ROS domain IDs.
- Runs as a standalone executable that takes a YAML configuration file as its last argument.
- Domain IDs can be overridden on the command line with --from and --to options.
- Can be launched through an XML launch file with config, from_domain, to_domain, reversed and bidirectional arguments.
- Composable nodes can be loaded alongside the bridge for intra-process communication, each with its own domain_id.
- Offers a C++ API that can be integrated into other processes.
Written by Robotheca from the project's README (opens in a new tab) at commit 75cdfae.
Getting started
- Difficulty
- Intermediate
- How to start
- The project's README (opens in a new tab)
Maintenance
- Status
- Maintained: a commit in the last 12 months
- Newest commit
- 27 Apr 2026 on main
- Latest release
- None published on GitHub
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.