IoT & embedded
A $3 ESP32 with a real identity.
Constrained MCUs cannot run a full WireGuard stack. So they don't. Beacons Lite — an OAS-aware MQTT and CoAP wire format — joins them to a parent peer that mediates the fleet on their behalf. Their DID is derived from the broker's lineage; they remain auditable peers.
What you get.
- ESP-IDF library for ESP32 / ESP32-S3 / ESP32-C3
- nRF Connect SDK library for Nordic nRF52 / nRF53
- RP2040 / RP2350 (Pico) — same brokered model
- Matter / Thread border-router peers
- Lineage derivation: broker signs MCU identities under its DID
Supported platforms
The full list.
| Platform | Tier | Implementation | Channel |
|---|---|---|---|
| ESP32 / ESP32-S3 / ESP32-C3 (RISC-V) | T4 | Beacons Lite over MQTT, brokered through parent peer | Vendor SDK |
| Raspberry Pi Pico (RP2040, RP2350) | T4 | Same brokered model | Vendor SDK |
| Arduino / Adafruit Feather | T4 | Same brokered model | Library manager |
| Nordic nRF52 / nRF53 (BLE mesh) | T4 | Same brokered model | nRF Connect SDK |
| Particle Argon / Boron | T4-T5 hybrid | Brokered on Wi-Fi, T5 on cellular | Particle cloud |
| Matter / Thread devices | T4 | Brokered through a Matter controller peer | Matter SDK |
The broker pattern means a single Raspberry Pi can mediate dozens of MCUs without any of them ever opening a WireGuard tunnel. The MCUs still appear in your fleet — with DIDs derived from the broker's lineage, full audit trail, and policy-derived access scope.