Documentation
Concepts, recipes, troubleshooting.
Beacons documentation lives in three layers: concepts that explain the architecture, recipes that show how to do a specific thing, and reference for when you need the exact shape of an API or CLI flag.
Concepts
Mental models.
- The mesh — what Beacons is and is not
- Identity — `did:oas` · AEGIS · Arsenal
- Policy engine — ACLs from governance
- Audit chain — Blake3 chained, Sigil anchored
- Multi-transport — eight wires, one identity
- Cellular — the multi-provider abstraction
- Security model — what we mitigate, what we don't
Recipes
How to do specific things.
- Migrate from Tailscale to Beacons
- Migrate from NetBird to Beacons
- Stand up a self-hosted coordinator on Fly.io or any Linux server
- Add a Hives flight as a peer
- Bind a hardware-rooted identity to an eUICC
- Wire a Cabbage meter into per-SIM billing alerts
- Anchor your audit chain to Sigil testnet for staging
- Add an attestation issuer to your fleet trust set
The full recipe library will live at docs.beacons.sh — it is actively being authored, recipe-by-recipe, alongside the Phase 3 console rewrite.
Reference
When you need the exact shape.
- REST API reference
- bcn CLI reference
- SDK overview
- MCP tool list
- OpenAPI 3.1 spec — published at
api.beacons.sh/v1/openapi.json - Protobuf schemas — published at
github.com/l1feai/beacons-proto