Phase 0 through Phase 8.

Foundation

The smallest correct starting point.

• beacons-core — domain types
• beacons-identity — OAS + AEGIS + Arsenal
• beacons-policy — lineage / governance / capability
• beacons-transport — transport trait
• beacons-wg-kernel — Linux WG via netlink
• beacons-coord — single-region coordinator
• beacons-store — PostgreSQL via Silos
• beacons-api — Axum HTTP API
• beacons-cli — bcn CLI
• beacons-agent — Linux daemon

ExitA developer on a fresh Linux box can create a fleet, enroll two peers, and observe a working WireGuard tunnel — exercising all three identity layers.

Universal Core

WASM/WASI compilation target, OCI container, K8s manifests, Hives integration.

• beacons-wasm — WASM/WASI build of beacons-core
• beacons-sdk — Rust SDK for embedding
• OCI image at ghcr.io/l1feai/beacons-agent
• Helm chart for K8s DaemonSet and pod sidecar
• Hives flight integration
• Cloudflare Workers / Wasmtime / Wasmer host validation

ExitA Forge agent compiled to WASM and deployed to a Hives flight auto-joins its org's fleet at startup with two lines of code. Same WASM artifact runs in Cloudflare Workers.

Desktop & Mobile

Native client experience for human fleet operators.

• Tauri 2 desktop app (macOS, Windows, Linux)
• Tauri 2 mobile app (iOS, iPadOS, Android)
• macOS NetworkExtension + Mac App Store submission
• Windows WireGuardNT + signed MSI
• Android VpnService + Play Store + F-Droid
• iOS Network Extension provider + App Store
• TypeScript, Python, Go, Swift SDKs

ExitA non-technical fleet operator on macOS can install the Beacons app, sign in via Locks, join an existing fleet, and see their device on the mesh. Same flow on Windows, Linux, iOS, Android.

Production & Multi-region

Make it real.

• beacons-stun STUN server
• beacons-signal peer rendezvous
• beacons-relay custom Rust TURN-equivalent
• beacons-dns MagicDNS + per-fleet subdomains
• beacons-discovery capability-aware peer discovery
• beacons-audit hash-chained log + Sigil anchoring
• beacons-telemetry per-peer metrics
• mTLS between all internal services
• Console rewrite using shared design system
• Cabbage billing integration

ExitThree regions deployed, 1,000 fleets, 100,000 peers in stress test. Audit chain anchored daily. Failover tested under load.

Cellular & eSIM

The killer differentiator.

• beacons-cellular provider abstraction
• beacons-cellular-telnyx (launch plugin)
• Twilio · Soracom · Hologram · 1NCE · Particle plugins
• beacons-esim eUICC / GSMA RSP orchestration
• Frontend cellular tab in fleet management
• SIM identity (`did:oas:<ns>:tool:sim-<iccid>`) issuance
• Per-SIM Cabbage billing
• Internal API for Locks consumption

ExitA fleet operator orders 100 SIMs through Beacons (via Telnyx), the SIMs ship, devices power on in the field, and they auto-join the fleet without further intervention. Locks issues a hardware-bound identity via eUICC.

Specialty Platforms

The Tier-2 device matrix.

• visionOS spatial fleet management
• watchOS / WearOS companions
• tvOS / Android TV / Fire TV / Tizen / webOS dashboards
• Browser extensions (Chrome, Edge, Brave, Firefox, Safari)
• NAS packages: Synology · QNAP · TrueNAS · UnRAID
• Router packages: OpenWRT · pfSense · OPNsense
• Kotlin SDK for KMP

ExitA Synology user installs from Package Center and joins their fleet in under five minutes. A Pixel Watch approves an enrollment. A browser tab runs as a peer via WASM/WebRTC.

Edge & Embedded

The Tier-3 edge fleet.

• NVIDIA Jetson packages
• Raspberry Pi optimized packages + Pi Imager preset
• RISC-V build for Pine64 Star64, StarFive
• Yocto recipe layer (meta-beacons)
• Home Assistant HACS add-on
• AWS Greengrass · Azure IoT Edge · GCP IoT components
• Robotics SDK packages: ROS2, PX4, DJI

ExitA robotics developer pip installs beacons-ros2 and has the robot's other ROS2 nodes discover it as a peer. A Yocto-built industrial gateway boots and joins a fleet.

Brokered Peers & Off-grid

The Tier-4 IoT and off-grid story.

• Beacons Lite protocol specification
• beacons-mqtt-broker and beacons-coap implementations
• Broker peer model — parent peer mediates fleet of MCUs
• ESP-IDF library for ESP32 series
• nRF Connect SDK library for Nordic chips
• LoRa / Meshtastic gateway support
• Iridium / Starlink / Swarm satellite IP integration
• Matter / Thread border router peer support

ExitAn ESP32 with a $3 BoM joins a fleet through a Raspberry Pi broker, gets a did:oas derived from the broker's lineage, and is auditable in the same OAS lineage tree as a top-tier server peer.

Long-tail

China, automotive, niche.

• HarmonyOS / OpenHarmony native port
• KaiOS lightweight client (PWA)
• Android Automotive OS variant
• Tesla / Rivian (Linux automotive) builds
• QNX automotive build
• Roku / TiVo / Comcast RDK dashboard channels
• Boston Dynamics / NVIDIA Isaac robotics SDKs

ExitAny strategically identified device has a path to join a Beacons fleet.