Field & IoT

Ship a sensor. Power it on. It joins your fleet.

Field deployments are where Beacons earns its keep. Cellular IP, eSIM provisioning, brokered MCUs, LoRa gateways, Iridium fallback — all surfaced through one identity model and one billing pipeline.

Cellular-direct

A SIM with a Beacons-private APN is itself a credential. The device behind it does not need any onboarding ritual: power on, attach to cell, route to private APN, and the coordinator enrolls it through the SIM's pre-issued DID.

Brokered MCUs

An ESP32 with $3 of BoM cannot run WireGuard. With Beacons Lite (OAS-aware MQTT/CoAP), it can be a fleet peer through a Raspberry Pi broker. The MCU's DID is derived from the broker's lineage; it appears in audit just like any other peer.

Off-grid fallback

When terrestrial cellular is unavailable, Beacons supports Iridium, Starlink, Swarm, LoRa, and Meshtastic. Same identity, same policy, different wire.

See also: Cellular · eSIM / eUICC · IoT devices · Satellite & off-grid

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