For developers
Embed the mesh. Build on top.
Drop beacons-sdk into your service in any of six languages. Use the bcn CLI in your CI pipeline. Add an MCP server so your agents control mesh state directly. Beacons is a library you compose with, not a black box you point at.
A library, not a service
Most VPN products treat the developer as an integrator. Beacons treats the developer as the primary user. The SDK is a first-class artifact: typed, idiomatic in each language, with a conformance suite that guarantees cross-language behavior.
CI/CD
The bcn CLI shares its scope with the console. Drop it in a GitHub Action, a GitLab job, a Buildkite step. Enroll ephemeral CI runners as peers, run tests across regions, revoke at the end. The audit chain records all of it.
MCP-native
Beacons exposes a Model Context Protocol server. Any MCP-fluent agent — Claude, Codex, custom Forge agents — can list fleets, enroll peers, query audit, all under the agent's own capability scope.
See also: Quickstart · API reference · SDK overview · MCP server