Robotics

One ROS2 fleet. Many sites. Same LAN feel.

ROS2 was designed for a single LAN. Multi-site robotics deployments inherit that assumption painfully. Beacons re-uses the LAN-feel by making every robot a peer in your fleet — discoverable, addressable, and policy-gated.

ROS2 discovery across continents

The beacons-ros2 package binds a Beacons peer to a ROS2 node. Other ROS2 nodes in the same fleet discover it through normal DDS — they never see the Beacons layer. Cross-site multicast just works, because MagicDNS resolves the names and the overlay routes the packets.

Drones, ground vehicles, manipulators

PX4 drones, DJI fleets, Boston Dynamics units, NVIDIA Isaac stacks — each ships with an SDK package that embeds beacons-sdk. The robot becomes a fleet peer on power-on; the audit chain records every connection.

Mesh routing for unreliable links

Field robots often work over cellular or satellite. Multi-transport negotiation means a Jetson-equipped robot can use Wi-Fi at the depot, cellular in transit, and satellite when out of cell range — without re-enrolling, without losing its identity.

See also: Robotics devices · Edge AI devices · Cellular

Open a fleet

The mesh that fits agents and humans.

A `did:oas`-rooted private mesh that ships peer configurations to any device, anywhere, by policy — not by hand.

Open consoleRead the quickstart