Edge AI

Jetson, Pi, and Coral clusters that belong to their org.

Edge AI fleets often live at the awkward intersection of cloud and IoT: too capable to be a sensor, too distributed to be a server. Beacons treats them as full Tier-1 peers with the right transports and the right policy.

Hardware as fleet member

A Jetson Orin, a Raspberry Pi 5, or a Coral dev board is a Tier-1 host in the Beacons matrix. The Rust core builds with CUDA-aware flags on Jetson; on Pi it ships from the Pi Imager preset; on Coral it is a native ARM build.

Co-located inference

When edge inference results need to flow back to a Forge agent or a Hives flight, Beacons provides the secure, identity-rooted transport. No reverse-tunnel ngrok ritual. Just a peer in the fleet.

Bulk fleet ops

Provision via the bcn CLI in CI. Update via a coordinator-pushed configuration. Revoke via a single policy change — every edge node loses access on the next tick.

See also: Edge AI devices · Robotics · CLI

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