FAQ
Common questions, answered.
The ten questions we are asked most often, with links to where they are answered in detail.
Why not just use Tailscale or NetBird?+
Both are well-engineered. Both were built for human users on long-lived devices. Beacons is line-one designed for agents and humans both, with cryptographic lineage and policy-derived access. See comparisons.What is `did:oas`?+
The L1fe ecosystem\'s W3C-compliant DID method, anchored to a human-rooted lineage tree. Read more.Can I self-host the entire stack?+
Yes. The Rust workspace, SDKs and clients are MIT/Apache-2.0. Hosted control-plane operations and enterprise features are commercial. See pricing.What transports does Beacons support?+
Kernel WireGuard, userspace WireGuard, WebRTC datachannels, MQTT-over-TLS, CoAP, cellular IP, LoRa/Meshtastic, and Iridium/Starlink. See multi-transport.Which cellular providers are supported?+
Telnyx (launch partner), Twilio Super SIM, Soracom, Hologram, 1NCE, Particle, Onomondo, EMnify, and KORE / Aeris / Pelion. See cellular.How does audit work?+
Every coordinator action emits a Blake3 hash-chained event. Per-fleet chains are anchored on Sigil. See audit chain.Where does Locks fit in?+
Locks is the customer-facing identity product. It issues `did:oas` identities that join Beacons fleets, and it consumes the Beacons eUICC orchestration API for hardware-rooted identities.Can I run Beacons inside Kubernetes?+
Yes. Helm charts ship in Phase 1. DaemonSet, sidecar, and Hives flight models are all supported. See Kubernetes.How does the agent SDK pricing work?+
The SDKs are MIT/Apache-2.0. You pay for the hosted control plane per peer. See pricing.When can I start using Beacons?+
Phase 0 is in flight. Design partners are using it today. Public early access opens after Phase 2 closes. See roadmap.