Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

update reference

Justin D'Souza15a4becaaf00
diff --git a/CLAUDE.md b/CLAUDE.md
index 9331f680..151b4173 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -26,8 +26,8 @@ Do not recreate or depend on removed `asymptote` mirror trees. Keep new work foc
- Beacon is visibility-first endpoint telemetry for local AI agent runtimes, not a hosted policy service or general endpoint protection product.
- Preserve the local-only default. The public Beacon build must not require a hosted account, remote policy fetch, hosted dashboard, or external network dependency during normal hook execution, and hooks themselves never touch the network.
- `beacon login` is the account-identity channel for interactive users and is required by the interactive `beacon endpoint install` wizard. It uses browser PKCE against beacon.sh and stores the scoped CLI token only in `~/.beacon/auth/session.json` (0600 under a 0700 directory). Signing in alone never starts forwarding. User-mode `beacon endpoint connect` may send that token once to `POST /api/cli/enroll/account` to authorize minting a separate device ingest key, and `beacon mcp token create` may send it to `POST /api/cli/mcp/tokens` (scope `mcp:token:create`, listed on the sign-in page) to mint a personal MCP token that is printed once to stdout and never written to a file; never copy the account token into endpoint config, Vector, hook environments, logs, or command output. System/root/package/MDM/CI/piped-stdin/dry-run installs stay noninteractive and account-free.
-- Beacon Managed forwarding (`cli/beacon/internal/endpoint/asymptote`, `beacon endpoint connect`, `beacon endpoint asymptote`) is Vector-shaped: Beacon writes local JSONL, Vector ships runtime lines only from the connection point forward and reads inventory from the beginning to establish the endpoint's current baseline, and the `bcn_device_*` key stays only in `<BaseDir>/asymptote/vector-secrets.json` via Vector's secret backend. The onboarding wizard preselects Managed, and confirming it connects this endpoint in the same command once the local install has succeeded; an endpoint that is already enrolled is never re-enrolled, because enrollment rotates the device key. Standard mode ships locally sanitized retained content; metadata-only uses local Vector transforms to remove prompts, responses, reasoning, tool arguments/results, command output, raw fields, diffs, inventory content, and MCP definitions before buffering/upload. Keep the ingest URL `https://`, the wire contract aligned with `beacon-ingest` (`/v1/ingest/{runtime,inventory}` and `/v1/ingest/health`), and do not add another endpoint network channel. The cloud-sandbox shuttle is the bounded exception: only with `BEACON_ORIGIN=cloud`, it can upload new runtime lines to GCS, S3, or the same Beacon ingest contract because no Vector/service manager/browser/persistent disk exists there.
-- `beacon endpoint install` has a full-screen onboarding wizard on interactive user TTYs. It signs in, preselects Beacon Managed, requires an explicit choice to opt out to Local, and asks Managed users to choose Standard or Metadata-only privacy. Signing in alone still moves no telemetry. Confirming Managed does: the confirm screen states that it installs Beacon and starts forwarding, and names what the selected privacy mode sends, so that screen is the consent point. The managed destination is recorded only after enrollment succeeds, so a failed enrollment leaves a working local install, prints `beacon endpoint connect` as the retry, and re-offers the question on the next install. The onboarding record is written only after `lifecycle.Install` returns, because a profile written first left a failed install looking onboarded and silently skipped the wizard on the retry. Explicit `install --connect` is unchanged. The wizard is skipped for system/root/CI/piped-stdin/dry-run or `BEACON_ONBOARDING=0`; those unattended paths must never gain an account or browser dependency. Legacy `BEACON_ONBOARDING_EMAIL`/`USAGE` submissions remain only for fleet compatibility. Implementation lives in `cli/beacon/internal/onboarding` and `cli/beacon/cmd/endpoint_onboarding.go`; keep `docs/cli/endpoint-onboarding.mdx` in sync.
+- Beacon Cloud forwarding (`cli/beacon/internal/endpoint/asymptote`, `beacon endpoint connect`, `beacon endpoint asymptote`) is Vector-shaped: Beacon writes local JSONL, Vector ships runtime lines only from the connection point forward and reads inventory from the beginning to establish the endpoint's current baseline, and the `bcn_device_*` key stays only in `<BaseDir>/asymptote/vector-secrets.json` via Vector's secret backend. The onboarding wizard preselects Beacon Cloud, and confirming it connects this endpoint in the same command once the local install has succeeded; an endpoint that is already enrolled is never re-enrolled, because enrollment rotates the device key. Standard mode ships locally sanitized retained content; metadata-only uses local Vector transforms to remove prompts, responses, reasoning, tool arguments/results, command output, raw fields, diffs, inventory content, and MCP definitions before buffering/upload. Keep the ingest URL `https://`, the wire contract aligned with `beacon-ingest` (`/v1/ingest/{runtime,inventory}` and `/v1/ingest/health`), and do not add another endpoint network channel. The cloud-sandbox shuttle is the bounded exception: only with `BEACON_ORIGIN=cloud`, it can upload new runtime lines to GCS, S3, or the same Beacon ingest contract because no Vector/service manager/browser/persistent disk exists there.
+- `beacon endpoint install` has a full-screen onboarding wizard on interactive user TTYs. It signs in, preselects Beacon Cloud, requires an explicit choice to opt out to Local, and asks Managed users to choose Standard or Metadata-only privacy. Signing in alone still moves no telemetry. Confirming Beacon Cloud does: the confirm screen states that it installs Beacon and starts forwarding, and names what the selected privacy mode sends, so that screen is the consent point. The managed destination is recorded only after enrollment succeeds, so a failed enrollment leaves a working local install, prints `beacon endpoint connect` as the retry, and re-offers the question on the next install. The onboarding record is written only after `lifecycle.Install` returns, because a profile written first left a failed install looking onboarded and silently skipped the wizard on the retry. Explicit `install --connect` is unchanged. The wizard is skipped for system/root/CI/piped-stdin/dry-run or `BEACON_ONBOARDING=0`; those unattended paths must never gain an account or browser dependency. Legacy `BEACON_ONBOARDING_EMAIL`/`USAGE` submissions remain only for fleet compatibility. Implementation lives in `cli/beacon/internal/onboarding` and `cli/beacon/cmd/endpoint_onboarding.go`; keep `docs/cli/endpoint-onboarding.mdx` in sync.
- Do not add dependency vulnerability scanning, OSV/GHSA lookups, package remediation, or other vulnerability-enforcement flows to the public hook path.
- Do not add broad runtime enforcement unless explicitly requested. Current control behavior is limited to hook-native approvals/denials exposed by supported agent runtimes.
- Keep destination support shaped like the existing local JSONL and customer-managed forwarding paths. Beacon may render supported packs or token-based endpoint forwarders, but should not add hosted SIEM dependencies or store third-party service credentials beyond the explicit supported configs. Elastic remains a file-tailing pack over local JSONL.
@@ -59,7 +59,7 @@ Supported runtime surfaces today:
- Browser chat telemetry through an optional MV3 extension (`browser-extension/`; Chrome, with a beta Firefox build) covering claude.ai and chatgpt.com. A main-world interceptor tees the streamed response, a per-site adapter parses it into a normalized turn, and the service worker POSTs OTLP GenAI logs to the local collector on `127.0.0.1:4318`; the extension never writes files and never contacts a remote endpoint. `harness.name` resolves to `claude_web` or `chatgpt_web` (already handled by `NormalizeHarnessName` in `pkg/asymptoteobserve/harness.go`, where the browser cases must stay above the generic `claude` rule) and `harness.collection_method` is `otlp`. The one build serves every Chromium browser; each event names the browser it came from in the typed `user_agent.name`/`user_agent.version` fields (OTel semconv, promoted by the exporter so Metadata-only forwarding keeps them), resolved in `browser-extension/src/shared/browser-identity.ts` from UA Client Hints brands, with a UA-string fallback that also names Firefox. Scope is deliberately narrow: only those origins' chat streams, never other tabs or general browsing. Retention defaults to `full`, so prompt and response text is retained by default; this is documented rather than defaulted down, because browser chat telemetry without content has no investigative value. Treat the adapters as experimental, since both sites' stream formats are private and undocumented. Per-browser differences live only in `browser-extension/tools/targets.mjs` (one entry per target, deriving its manifest from `src/manifest.json`; Chrome ships that file verbatim to `dist/`, Firefox gets `dist-firefox/`), and every extension API call goes through the `src/shared/browser.ts` shim (a unit test fails on direct `chrome.*` use). The Firefox Gecko ID `[email protected]` is pinned and must never change.
- `beaconjson` OpenTelemetry Collector exporter that converts OTLP logs, traces, metrics, and resource attributes into Beacon endpoint JSONL.
- Endpoint inventory (`inventory.heartbeat` / `inventory.snapshot` in `inventory_state.jsonl`) is written by a scheduled job, `com.beacon.endpoint.inventory` (`service.InventoryManager`, user LaunchAgent or system LaunchDaemon, `beacon-inventory.timer` on systemd), every six hours and once at load, on by default and reconciled by `lifecycle.ReconcileInventoryJob` on every install, repair and package upgrade (`beacon endpoint inventory install-daemon`). Agent hooks do not trigger inventory any more; the hook binary's `--cli` flag and `inventory-heartbeat` subcommand survive only as no-ops for hook commands written by older versions, and `beacon endpoint inventory heartbeat --trigger hook` is likewise retired. A system-mode run inventories the active console user's home and still writes the liveness heartbeat when nobody is logged in; the scheduled scan has no working directory, so project-scoped config is only in `beacon endpoint inventory`.
-- Beacon Managed forwarding, the one Beacon-hosted network channel for endpoint telemetry: user-mode `beacon endpoint connect` authorizes device enrollment with the signed-in CLI account; system mode uses browser PKCE at `/cli/enroll`. Both store only the per-device key in `<BaseDir>/asymptote/vector-secrets.json` (0600, 0700 dir), render the selected privacy mode into `vector.toml`, validate it, and run Vector as `com.beacon.endpoint.asymptote-forwarder` / `beacon-asymptote-forwarder.service` through `service.ForwarderManager` (refused in supervised mode). `enrollment.json` and `config.json`'s `managed_ingest` block carry only non-secret identity and privacy mode; `beacon endpoint status` reports forwarder state and a live credential check (`GET /v1/ingest/health`, 3 s timeout); `disconnect` and `uninstall` remove the forwarder and credentials but never revoke server-side.
+- Beacon Cloud forwarding, the one Beacon-hosted network channel for endpoint telemetry: user-mode `beacon endpoint connect` authorizes device enrollment with the signed-in CLI account; system mode uses browser PKCE at `/cli/enroll`. Both store only the per-device key in `<BaseDir>/asymptote/vector-secrets.json` (0600, 0700 dir), render the selected privacy mode into `vector.toml`, validate it, and run Vector as `com.beacon.endpoint.asymptote-forwarder` / `beacon-asymptote-forwarder.service` through `service.ForwarderManager` (refused in supervised mode). `enrollment.json` and `config.json`'s `managed_ingest` block carry only non-secret identity and privacy mode; `beacon endpoint status` reports forwarder state and a live credential check (`GET /v1/ingest/health`, 3 s timeout); `disconnect` and `uninstall` remove the forwarder and credentials but never revoke server-side.
- Asymptote Observe TypeScript SDK instrumentation for cloud applications, starting from OpenTelemetry/OpenLLMetry patterns and `observe()` wrappers.
- Elasticsearch/Filebeat content pack generation for forwarding local Beacon JSONL into customer-managed Elastic deployments or the bundled loopback-only development stack.
- A local-only dashboard served by `beacon endpoint dashboard`, bound to loopback by default and backed by the runtime JSONL log.
@@ -67,7 +67,7 @@ Supported runtime surfaces today:
- Local threat detection via `beacon scan`, which runs the open Threat Rules format (`spec/threat-rules`; CEL match conditions over the endpoint event schema, with embedded conformance fixtures) over the runtime JSONL. The engine (`pkg/asymptoteobserve/threatrules`) ships in the binary; the rule corpus is external data loaded from a local store (`~/.beacon/endpoint/rules`) managed by `beacon rules`, so the corpus can grow without enlarging the binary. `scan` is read-only and offline; only the explicit, user-initiated `beacon rules pull <url>` reaches the network. A small frozen baseline is embedded so `scan` works before any rules are installed.
- Session handoff via `beacon handoff list|export|resume` (`cli/beacon/internal/handoff`, `cli/beacon/cmd/handoff*.go`; docs in `docs/cli/handoff.mdx` and `docs/concepts/session-handoff.mdx`). Every runtime is one entry in the registry in `cli/beacon/internal/handoff/runtimes.go`: its session source, the names it answers to, and the commands that reopen it or start it from a brief; `TestRegistryIsConsistent` checks the entries. Handoff reads the session stores of Claude Code, Codex CLI, OpenCode, Cline, Pi, Prime Agent, Factory Droid, GitHub Copilot CLI, Hermes Agent, DeepSeek Harness, fx, Grok Build, OpenClaw Gateway and Cursor read-only and never touches the network. Oh My Pi, Gemini CLI, Qwen Code, Kiro, Antigravity CLI, Devin CLI, Muse Code, OpenHands and goose have no store Beacon reads: their sessions come from the runtime log, and they take a brief as the target of `--agent`. `resume` reopens a session natively with its runtime's own command when it can, and otherwise writes a brief to `~/.beacon/endpoint/handoffs` (0700/0600) and starts a new session pointed at it. DeepSeek Harness cannot be started, and Hermes Agent and fx only reopen their own sessions, so their sessions continue in another runtime. fx, Grok Build and Cursor find a session by the directory they run in, so they are reopened natively only in the session's own directory. The brief is passed by absolute path, never inlined on a command line. Every launch keeps the runtime's approvals on: Beacon never passes a flag that turns them off, names the approval mode that asks where a CLI takes one (Cline always gets `--auto-approve false`, because Cline defaults to approving every tool call), and removes or overrides environment switches that would approve everything (`COPILOT_ALLOW_ALL`, `COPILOT_PLAN_THEN_AUTOPILOT`, `HERMES_YOLO_MODE`, `GOOSE_MODE`); `--print` shows them under `env`. Briefs run every event through `SanitizeEvent`, and quoted content goes in fences longer than any backtick run it contains, with inline fields reduced to one line, so quoted content cannot forge brief structure. A new session's first prompt ends with the `[beacon-handoff from=<harness> session=<id>]` marker (`pkg/asymptoteobserve/handoff.go`). The hook and plugin prompt paths and the session-store mappers record a `session.handoff` event with `handoff.{source_harness,source_session_id}` when they see it; that is an observed claim, not a verified identity.
- Commit-to-session links via `beacon git setup|status|remove|link|notes` (`cli/beacon/internal/gitlink`, `cli/beacon/cmd/git*.go`; docs in `docs/cli/git.mdx`). A link is a `beacon:<harness>/<session-id>` line in a git note under `refs/notes/beacon`; it carries identifiers only, never content, because notes can be pushed. Which sessions to link is inferred from the local runtime log: a session is linked when, between the parent commit and the commit (at least two hours, at most 24), it wrote a file the commit changes (for a merge, only files that differ from every parent, so a clean merge or pull links nothing). Evidence is file write events, write-type `file.operation`s, plainly readable shell targets, and `apply_patch` envelopes; reads never count. Note updates are a compare-and-swap on the notes ref through a private `refs/notes/beacon-tx/` working ref, and every existing note line, a teammate's or a person's, is kept verbatim. `setup` installs post-commit (links HEAD in the foreground with a 3 s budget, silent, never fails the commit, skips rebase/cherry-pick/revert) and post-rewrite (normalizes the note git concatenates on amend) as standalone `beacon-<hook>` scripts called from a marked block inserted after the shebang of the repository's own hook; only shell hooks are edited, `core.hooksPath` is refused without `--hooks-path`, and `notes.rewriteRef` carries links through amend and rebase. `BEACON_GIT_HOOKS=0` disables the hooks for one command. Every link a run adds is also written to the runtime log as one `session.commit_linked` event in the linked session's timeline (`event.fidelity=inferred`, no collection method), with commit id, branch and credential-stripped remote in the OTel-shaped `vcs` block and overlap counts in `vcs.attribution`; the event deliberately carries no file, command or tool fields so it can never become attribution evidence. Sharing is opt-in (`setup --share-notes`, off by default): a non-destructive fetch refspec `+refs/notes/beacon:refs/notes/beacon-remotes/<remote>` so git's own fetch brings teammates' links into a read-only tracking ref that `beacon git notes` unions with the local one (never force-fetch into `refs/notes/beacon`: it would destroy unpushed links), and a pre-push hook that fetches, merges with `cat_sort_uniq` through the same CAS, and pushes only the notes ref with `--no-verify`, within a 10 s budget and never failing the push. That pre-push hook is the only Beacon git hook that touches the network, and only during a push the person started; `beacon git notes push|fetch` do the same by hand.
-- Beacon Managed MCP registration via `beacon mcp connect|disconnect|status` (`cli/beacon/internal/mcpconnect`, `cli/beacon/cmd/mcp_connect.go`; docs in `docs/cli/mcp-connect.mdx`). It registers the Beacon Managed MCP server as `beacon-managed`, a different name from the local stdio server `beacon`, in the user-level config of Claude Code, Codex CLI, Cursor, VS Code, Gemini CLI and OpenCode. It prints manual steps for runtimes without confirmed MCP OAuth support. OAuth is the default and writes only the URL; `--token-env` writes a reference to an environment variable in each harness's own syntax, never a value. `connect` never reads or copies the account token and never writes a token; minting one is the separate, explicit `beacon mcp token create`. It is explicit and interactive: never run by `endpoint install` or onboarding (the install only suggests it after the wizard's Managed choice), refused as root, and refused in CI or without a terminal unless `--yes` is given. Its one network request is the RFC 9728 resource-metadata check of the URL, which `--dry-run` skips. Configs are edited like the Kimi Code writer: never re-serialized, spliced as text, parsed back and compared before an atomic replace, backed up first. What was written is recorded in `~/.beacon/mcp/connections.json`, and `disconnect` removes only entries recorded there that still point at the recorded URL. `cmd/mcp_connect_e2e_test.go` runs the real harness CLIs when they are installed; re-run it when a harness changes its MCP config format.
+- Beacon Cloud MCP registration via `beacon mcp connect|disconnect|status` (`cli/beacon/internal/mcpconnect`, `cli/beacon/cmd/mcp_connect.go`; docs in `docs/cli/mcp-connect.mdx`). It registers the Beacon Cloud MCP server as `beacon-managed`, a different name from the local stdio server `beacon`, in the user-level config of Claude Code, Codex CLI, Cursor, VS Code, Gemini CLI and OpenCode. It prints manual steps for runtimes without confirmed MCP OAuth support. OAuth is the default and writes only the URL; `--token-env` writes a reference to an environment variable in each harness's own syntax, never a value. `connect` never reads or copies the account token and never writes a token; minting one is the separate, explicit `beacon mcp token create`. It is explicit and interactive: never run by `endpoint install` or onboarding (the install only suggests it after the wizard's Managed choice), refused as root, and refused in CI or without a terminal unless `--yes` is given. Its one network request is the RFC 9728 resource-metadata check of the URL, which `--dry-run` skips. Configs are edited like the Kimi Code writer: never re-serialized, spliced as text, parsed back and compared before an atomic replace, backed up first. What was written is recorded in `~/.beacon/mcp/connections.json`, and `disconnect` removes only entries recorded there that still point at the recorded URL. `cmd/mcp_connect_e2e_test.go` runs the real harness CLIs when they are installed; re-run it when a harness changes its MCP config format.
- An optional, off-by-default policy seam in the hook path (`cli/beacon-hooks/internal/policy`) governed by the stable contract in `pkg/asymptoteobserve/policycontract`. When `BEACON_POLICY_PROVIDER` names an executable, the `pre-tool` and `permission-request` hooks send it a JSON request describing the imminent tool call and honor an allow/deny response, returning the runtime's native deny shape and `policy.enforcement=enforce` telemetry on a deny. The seam is inert when unset and fail-open on any error (timeout, non-zero exit, malformed output), so the open build ships no enforcement of its own; all audit/enforce decision logic lives in the external provider. `rules/agent-control/agent-permission-bypass-spawn.rule.yaml` is the open detect twin that flags the same pattern in `beacon scan`.
Current non-goals unless explicitly requested:
diff --git a/README.md b/README.md
index 4160925c..44599b63 100644
--- a/README.md
+++ b/README.md
@@ -46,7 +46,7 @@ Beacon is an open-source memory layer for AI coding agents that learns from your
## 🚀 Quick Start
Beacon is open source and local-first. Interactive endpoint setup signs in through
-beacon.sh and preselects Beacon Managed, with an explicit Local opt-out. Signing in
+beacon.sh and preselects Beacon Cloud, with an explicit Local opt-out. Signing in
forwards nothing; confirming Managed installs Beacon and connects this machine in
the same command, and the confirm screen says so before you accept. System, package,
MDM, and CI installation paths remain noninteractive and account-free.
@@ -148,13 +148,13 @@ Or inspect the raw event stream:
```
> [!NOTE]
-> Signing in does not enable forwarding. Confirming the preselected Beacon Managed
+> Signing in does not enable forwarding. Confirming the preselected Beacon Cloud
> option does: the wizard says so on the confirm screen, names what your chosen
> privacy mode sends, and connects the endpoint after the install succeeds. Choose
> Local to keep everything on this machine, and disconnect any time with
> `beacon endpoint disconnect`.
-If this endpoint forwards to Beacon Managed, your agents can search that history over MCP:
+If this endpoint forwards to Beacon Cloud, your agents can search that history over MCP:
```bash
beacon mcp connect
@@ -346,7 +346,7 @@ You can also forward the same normalized session history into infrastructure you
| Destination | Category | Support Path |
| --- | --- | --- |
| Local JSONL | Local | Default endpoint log and local dashboard source |
-| Beacon Managed | Hosted forwarding | Signed-in device enrollment with Standard or Metadata-only privacy |
+| Beacon Cloud | Hosted forwarding | Signed-in device enrollment with Standard or Metadata-only privacy |
| CrowdStrike Falcon LogScale HEC | SIEM | Endpoint forwarding with LogScale ingest tokens |
| Microsoft Sentinel | SIEM | Azure Monitor Agent and Data Collection Rule content pack |
| Rapid7 InsightIDR | SIEM | Custom Logs webhook content pack |
diff --git a/SECURITY.md b/SECURITY.md
index 7cd4cfd4..e058770c 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -68,7 +68,7 @@ active log rotates at 10 MiB and Beacon keeps up to five numbered local
archives. Normal endpoint collection does not require a hosted account, remote
policy fetch, MDM API credentials, or external network connection.
-The one opt-in network channel for telemetry is Asymptote Managed forwarding:
+The one opt-in network channel for telemetry is Asymptote Beacon Cloud forwarding:
a Vector forwarder on the endpoint posts the local runtime and inventory JSONL
over HTTPS with a per-device key that a member of the organization approved in
the browser. The key lives in a `0600` secrets file outside Beacon
diff --git a/beacon-sandbox/scenarios/i04-vector-forwarding.yaml b/beacon-sandbox/scenarios/i04-vector-forwarding.yaml
index 4b0964ba..de5e4d28 100644
--- a/beacon-sandbox/scenarios/i04-vector-forwarding.yaml
+++ b/beacon-sandbox/scenarios/i04-vector-forwarding.yaml
@@ -1,7 +1,7 @@
id: i04-vector-forwarding
# Does the Vector that the Linux packages bundle actually forward Beacon's events?
#
-# The .deb, .rpm and Linux archives ship Vector at /opt/beacon/bin/vector. It runs Beacon Managed
+# The .deb, .rpm and Linux archives ship Vector at /opt/beacon/bin/vector. It runs Beacon Cloud
# forwarding and six customer-managed destinations, and nothing else in the suite starts it. So a
# pack that Vector rejects, a secret backend that sends the wrong key, or a Vector build that will
# not start on the target host would all go unnoticed.
diff --git a/cli/beacon/.goreleaser.yaml b/cli/beacon/.goreleaser.yaml
index 1a51d45f..c12fb1ac 100644
--- a/cli/beacon/.goreleaser.yaml
+++ b/cli/beacon/.goreleaser.yaml
@@ -148,7 +148,7 @@ nfpms:
dst: /opt/beacon/bin/beacon-otelcol
file_info:
mode: 0755
- # Vector runs every forwarder Beacon renders (Beacon Managed, S3, GCS, CloudWatch, Sumo Logic,
+ # Vector runs every forwarder Beacon renders (Beacon Cloud, S3, GCS, CloudWatch, Sumo Logic,
# Rapid7, Falcon). Same path as the macOS package, which is where FindVector looks. It does not
# run unless one of those is configured. /opt/beacon/bin is not on PATH, so it cannot shadow
# another Vector.
diff --git a/cli/beacon/README.md b/cli/beacon/README.md
index 9181e482..990b4b6d 100644
--- a/cli/beacon/README.md
+++ b/cli/beacon/README.md
@@ -516,7 +516,7 @@ and a `BeaconRuntime_CL` custom Log Analytics table. Store Azure workspace,
DCR, endpoint, and credential details in Azure or customer-managed deployment
tooling, not in Beacon endpoint configuration.
-## Beacon Managed
+## Beacon Cloud
```bash
./beacon endpoint connect
@@ -524,7 +524,7 @@ tooling, not in Beacon endpoint configuration.
./beacon endpoint disconnect
```
-Beacon Managed is the Beacon-hosted forwarding destination. User-mode connect
+Beacon Cloud is the Beacon-hosted forwarding destination. User-mode connect
uses the signed-in account to authorize a separate device key; system mode keeps
browser approval. The account token is never given to Vector. Connect stores the
device key in a `0600` secrets file and runs Vector as the
diff --git a/cli/beacon/cmd/endpoint.go b/cli/beacon/cmd/endpoint.go
index f164967b..98e27142 100644
--- a/cli/beacon/cmd/endpoint.go
+++ b/cli/beacon/cmd/endpoint.go
@@ -428,7 +428,7 @@ func init() {
endpointInstallCmd.Flags().BoolVar(&endpointOpts.noBrowser, "no-browser", false, "During interactive setup, print the sign-in URL instead of opening a browser")
endpointInstallCmd.Flags().StringVar(&endpointOpts.serviceKind, "service", "", "Service manager to use: auto (default), launchd, systemd, or none for a supervised collector process")
endpointInstallCmd.Flags().BoolVar(&endpointOpts.dryRun, "dry-run", false, "Print planned actions without changing endpoint files or services")
- endpointInstallCmd.Flags().BoolVar(&endpointOpts.connect, "connect", false, "After installing, attempt to connect this endpoint to Beacon Managed (user mode uses the signed-in account; system mode opens browser approval)")
+ endpointInstallCmd.Flags().BoolVar(&endpointOpts.connect, "connect", false, "After installing, attempt to connect this endpoint to Beacon Cloud (user mode uses the signed-in account; system mode opens browser approval)")
endpointOnboardingCmd.Flags().BoolVar(&endpointOpts.onboardingReset, "reset", false, "Clear the onboarding record so the question is asked again")
endpointOnboardingCmd.Flags().BoolVar(&endpointOpts.onboardingResend, "resend", false, "Retry a signup that could not be delivered")
endpointOnboardingCmd.Flags().BoolVar(&endpointOpts.jsonOutput, "json", false, "Print the onboarding record as JSON")
diff --git a/cli/beacon/cmd/endpoint_connect.go b/cli/beacon/cmd/endpoint_connect.go
index f5e0b87c..46dc7320 100644
--- a/cli/beacon/cmd/endpoint_connect.go
+++ b/cli/beacon/cmd/endpoint_connect.go
@@ -37,8 +37,8 @@ var (
var endpointConnectCmd = &cobra.Command{
Use: "connect",
- Short: "Forward this endpoint's telemetry to Beacon Managed",
- Long: `Connect this endpoint to Beacon Managed.
+ Short: "Forward this endpoint's telemetry to Beacon Cloud",
+ Long: `Connect this endpoint to Beacon Cloud.
For a user endpoint, uses the signed-in Beacon account to mint a device-specific
ingest key, stores that key in a private secrets file, and starts a Vector
@@ -73,7 +73,7 @@ func init() {
endpointConnectCmd.Flags().StringVar(&connectOpts.dashboardURL, "dashboard-url", "", "Beacon service URL (defaults to "+auth.DefaultDashboardURL+", or "+auth.DashboardURLEnv+")")
endpointConnectCmd.Flags().BoolVar(&connectOpts.noBrowser, "no-browser", false, "System mode: print the device approval URL instead of opening a browser")
endpointConnectCmd.Flags().StringVar(&connectOpts.vectorBin, "vector-bin", "", "Vector binary to run (defaults to "+asymptote.VectorBinEnv+", "+asymptote.PackagedVectorPath+", Homebrew, then PATH)")
- endpointConnectCmd.Flags().StringVar(&connectOpts.privacyMode, "privacy-mode", "", "Managed forwarding privacy: standard or metadata-only (defaults to onboarding choice)")
+ endpointConnectCmd.Flags().StringVar(&connectOpts.privacyMode, "privacy-mode", "", "Beacon Cloud forwarding privacy: standard or metadata-only (defaults to onboarding choice)")
endpointDisconnectCmd.Flags().BoolVar(&connectOpts.keepCredentials, "keep-credentials", false, "Keep the enrollment record and device key so a later connect can reuse this device")
endpointCmd.AddCommand(endpointConnectCmd)
endpointCmd.AddCommand(endpointDisconnectCmd)
@@ -149,7 +149,7 @@ func connectEndpoint(cmd *cobra.Command, userMode bool, logPath string) error {
if endpointOpts.jsonOutput {
return json.NewEncoder(os.Stdout).Encode(result)
}
- fmt.Fprintf(out, "Connected to Beacon Managed as device %s", result.Enrollment.DeviceID)
+ fmt.Fprintf(out, "Connected to Beacon Cloud as device %s", result.Enrollment.DeviceID)
if result.Enrollment.OrganizationName != "" {
fmt.Fprintf(out, " for %s", result.Enrollment.OrganizationName)
}
@@ -286,12 +286,12 @@ func dashboardHomeURL(base string) string {
func managedIngestStatusLine(status asymptote.ManagedIngestStatus) string {
if !status.Enabled {
if status.Message != "" {
- return "Beacon Managed: not connected (" + status.Message + ")"
+ return "Beacon Cloud: not connected (" + status.Message + ")"
}
- return "Beacon Managed: not connected (run `beacon endpoint connect`)"
+ return "Beacon Cloud: not connected (run `beacon endpoint connect`)"
}
var b strings.Builder
- b.WriteString("Beacon Managed: connected")
+ b.WriteString("Beacon Cloud: connected")
if status.OrganizationName != "" {
fmt.Fprintf(&b, " to %s", status.OrganizationName)
}
diff --git a/cli/beacon/cmd/endpoint_install.go b/cli/beacon/cmd/endpoint_install.go
index c60f7f54..16629edb 100644
--- a/cli/beacon/cmd/endpoint_install.go
+++ b/cli/beacon/cmd/endpoint_install.go
@@ -151,7 +151,7 @@ func runEndpointInstall(cmd *cobra.Command, args []string) error {
if err != nil {
return err
}
- // Confirming Beacon Managed connects this endpoint; --connect does the same for
+ // Confirming Beacon Cloud connects this endpoint; --connect does the same for
// the paths the wizard did not own.
connectAfterInstall := onboarded.Connect || endpointOpts.connect
result, err := endpointLifecycleInstall(endpointInstallOptions(selection, serviceKind))
@@ -193,14 +193,14 @@ func runEndpointInstall(cmd *cobra.Command, args []string) error {
return nil
}
-// suggestMCPConnect points a person who just chose Beacon Managed in the wizard at
+// suggestMCPConnect points a person who just chose Beacon Cloud in the wizard at
// `beacon mcp connect`. It only prints: registering the MCP server stays a separate,
// explicit command, and the unattended install paths never reach the wizard at all.
func suggestMCPConnect(out io.Writer, chosenInWizard bool) {
if !chosenInWizard {
return
}
- fmt.Fprintln(out, "To let your agents search this history through Beacon Managed MCP, run `beacon mcp connect`.")
+ fmt.Fprintln(out, "To let your agents search this history through Beacon Cloud MCP, run `beacon mcp connect`.")
}
func runEndpointStatus(cmd *cobra.Command, args []string) error {
diff --git a/cli/beacon/cmd/endpoint_onboarding.go b/cli/beacon/cmd/endpoint_onboarding.go
index 747b4af5..8ad9f403 100644
--- a/cli/beacon/cmd/endpoint_onboarding.go
+++ b/cli/beacon/cmd/endpoint_onboarding.go
@@ -29,7 +29,7 @@ const (
// they just have no terminal to type it into.
onboardingEnvEmail = "BEACON_ONBOARDING_EMAIL"
onboardingEnvUsage = "BEACON_ONBOARDING_USAGE"
- // managedIngestEnvEnabled set to a false-ish value hides the Beacon Managed row
+ // managedIngestEnvEnabled set to a false-ish value hides the Beacon Cloud row
// from the telemetry destination question; Local remains available. Explicit --connect
// is unaffected: the
// variable hides an offer, it does not override an operator's request.
@@ -93,7 +93,7 @@ func defaultOnboardingIsTTY() bool {
// run, CI, a dry run and a redirected stdin all return an outcome that asks the
// installer for nothing.
type onboardingOutcome struct {
- // Connect is true when the wizard confirmed Beacon Managed on an endpoint that
+ // Connect is true when the wizard confirmed Beacon Cloud on an endpoint that
// is not already enrolled, so the installer should connect it after installing.
// An already-connected endpoint is deliberately excluded: enrollment rotates the
// device key, and rotating a working forwarder's key to re-learn a destination
@@ -242,7 +242,7 @@ func runAccountOnboarding(cmd *cobra.Command, profile *onboarding.Profile, desti
}
}
- // Confirming Managed connects this endpoint, unless it already is one. An
+ // Confirming Beacon Cloud connects this endpoint, unless it already is one. An
// endpoint that is already enrolled keeps its device key and simply records the
// destination it has been using.
alreadyConnected := result.Destination == onboarding.DestinationAsymptote && !destinationAskable()
@@ -292,7 +292,7 @@ func runAccountOnboarding(cmd *cobra.Command, profile *onboarding.Profile, desti
// The connect output that follows says where events now go; anticipating it
// here would only be wrong if enrollment then failed.
case result.Destination == onboarding.DestinationAsymptote:
- fmt.Fprintf(cmd.OutOrStdout(), "Beacon Managed with %s privacy. This endpoint is already connected.\n", managedprivacy.Label(privacyMode))
+ fmt.Fprintf(cmd.OutOrStdout(), "Beacon Cloud with %s privacy. This endpoint is already connected.\n", managedprivacy.Label(privacyMode))
case result.Destination == onboarding.DestinationLocal:
fmt.Fprintln(cmd.OutOrStdout(), "Local-only telemetry selected. Open it with `beacon traces`.")
}
@@ -357,7 +357,7 @@ func destinationLabel(value string) string {
case onboarding.DestinationOwnInfra:
return "own infrastructure (forwarding pack)"
case onboarding.DestinationAsymptote:
- return "Beacon Managed"
+ return "Beacon Cloud"
default:
return value
}
diff --git a/cli/beacon/cmd/endpoint_onboarding_test.go b/cli/beacon/cmd/endpoint_onboarding_test.go
index 6e126380..8251c31a 100644
--- a/cli/beacon/cmd/endpoint_onboarding_test.go
+++ b/cli/beacon/cmd/endpoint_onboarding_test.go
@@ -653,7 +653,7 @@ func TestMaybeRunOnboardingConnectsManagedAndRecordsLocal(t *testing.T) {
t.Fatalf("connected endpoint destination = %q, want managed", got)
}
- // Confirming Managed on a fresh endpoint connects it in the same command.
+ // Confirming Beacon Cloud on a fresh endpoint connects it in the same command.
h = newOnboardingHarness(t)
h.askable = true
h.answers.DestinationAsked = true
@@ -860,7 +860,7 @@ func TestEndpointOnboardingShowsDestination(t *testing.T) {
for value, want := range map[string]string{
onboarding.DestinationLocal: "Telemetry destination: local only",
onboarding.DestinationOwnInfra: "Telemetry destination: own infrastructure",
- onboarding.DestinationAsymptote: "Telemetry destination: Beacon Managed",
+ onboarding.DestinationAsymptote: "Telemetry destination: Beacon Cloud",
} {
h := newOnboardingHarness(t)
h.loaded = onboarding.Profile{InstallID: "abc", Onboarding: onboarding.Onboarding{CompletedAt: "2026-08-01T00:00:00Z", Outcome: onboarding.OutcomeSubmitted, Email: "[email protected]", Usage: onboarding.UsageWork, Destination: value}}
diff --git a/cli/beacon/cmd/mcp.go b/cli/beacon/cmd/mcp.go
index 0c4153c1..a3cc7206 100644
--- a/cli/beacon/cmd/mcp.go
+++ b/cli/beacon/cmd/mcp.go
@@ -35,7 +35,7 @@ var mcpCmd = &cobra.Command{
serve and doctor run and check the local "beacon" server, which reads this machine's runtime
log. connect, disconnect and status manage the "beacon-managed" entry that points your harnesses
-at Beacon Managed MCP, which searches the session history this endpoint forwards.`,
+at Beacon Cloud MCP, which searches the session history this endpoint forwards.`,
}
var mcpServeCmd = &cobra.Command{
@@ -158,7 +158,7 @@ func runMCPDoctor(cmd *cobra.Command, args []string) error {
fmt.Println(`}`)
fmt.Println()
fmt.Println(`"beacon" is the local server: it reads this machine's runtime log and approved memory.`)
- fmt.Println(`For session history forwarded to Beacon Managed, run ` + "`beacon mcp connect`" + `, which registers`)
+ fmt.Println(`For session history forwarded to Beacon Cloud, run ` + "`beacon mcp connect`" + `, which registers`)
fmt.Println(`the separate "beacon-managed" server in your harnesses. The two names never overwrite each other.`)
}
return nil
diff --git a/cli/beacon/cmd/mcp_connect.go b/cli/beacon/cmd/mcp_connect.go
index ed342173..ff47cd37 100644
--- a/cli/beacon/cmd/mcp_connect.go
+++ b/cli/beacon/cmd/mcp_connect.go
@@ -23,7 +23,7 @@ import (
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/mcpconnect"
)
-// `beacon mcp connect` registers the Beacon Managed MCP server in the harnesses on this machine.
+// `beacon mcp connect` registers the Beacon Cloud MCP server in the harnesses on this machine.
// It is an explicit, interactive, per-user command: `beacon endpoint install`, onboarding and
// every unattended path (root, system/MDM installs, CI, piped stdin) never run it. It writes no
// secret -- OAuth harnesses get only the URL, and --token-env writes a reference to a variable --
@@ -55,8 +55,8 @@ var mcpConnectOpts struct {
var mcpConnectCmd = &cobra.Command{
Use: "connect",
- Short: "Register Beacon Managed MCP in the harnesses on this machine",
- Long: `Register the Beacon Managed MCP server, as "beacon-managed", in every detected harness that
+ Short: "Register Beacon Cloud MCP in the harnesses on this machine",
+ Long: `Register the Beacon Cloud MCP server, as "beacon-managed", in every detected harness that
supports it: Claude Code, Codex CLI, Cursor, VS Code, Gemini CLI and OpenCode.
By default only the URL is written, and each harness signs in with OAuth the first time it
@@ -64,7 +64,7 @@ connects. With --token-env, each config references an environment variable holdi
MCP token instead; the token itself is never written. Harnesses without confirmed MCP OAuth
support get the steps to add the server by hand.
-The URL is --url, or the Beacon Managed URL recorded by ` + "`beacon endpoint connect`" + `. It is
+The URL is --url, or the Beacon Cloud URL recorded by ` + "`beacon endpoint connect`" + `. It is
checked against the server's OAuth resource metadata before anything is written; that check is
this command's only network request. Every changed file is backed up first, and
` + "`beacon mcp disconnect`" + ` removes exactly what connect added.`,
@@ -75,7 +75,7 @@ this command's only network request. Every changed file is backed up first, and
var mcpDisconnectCmd = &cobra.Command{
Use: "disconnect",
- Short: "Remove the Beacon Managed MCP entries that connect wrote",
+ Short: "Remove the Beacon Cloud MCP entries that connect wrote",
SilenceUsage: true,
Args: cobra.NoArgs,
RunE: runMCPDisconnect,
@@ -83,7 +83,7 @@ var mcpDisconnectCmd = &cobra.Command{
var mcpStatusCmd = &cobra.Command{
Use: "status",
- Short: "Show where Beacon Managed MCP is configured",
+ Short: "Show where Beacon Cloud MCP is configured",
SilenceUsage: true,
Args: cobra.NoArgs,
RunE: runMCPStatus,
@@ -95,7 +95,7 @@ func init() {
c.Flags().StringSliceVar(&mcpConnectOpts.harnesses, "harness", nil, "Harnesses to act on, comma-separated (default: every detected harness)")
}
for _, c := range []*cobra.Command{mcpConnectCmd, mcpStatusCmd} {
- c.Flags().StringVar(&mcpConnectOpts.url, "url", "", "Beacon Managed MCP URL (default: the URL recorded by beacon endpoint connect)")
+ c.Flags().StringVar(&mcpConnectOpts.url, "url", "", "Beacon Cloud MCP URL (default: the URL recorded by beacon endpoint connect)")
}
f := mcpConnectCmd.Flags()
f.StringVar(&mcpConnectOpts.tokenEnv, "token-env", "", "Reference a personal MCP token in this environment variable instead of using OAuth")
@@ -242,7 +242,7 @@ func runMCPConnect(cmd *cobra.Command, args []string) error {
}
url, derived, err := mcpconnect.ResolveURL(mcpConnectOpts.url, mcpIngestURL())
if err != nil {
- return fmt.Errorf("%w (Beacon Managed serves MCP at https://mcp.beacon.sh)", err)
+ return fmt.Errorf("%w (Beacon Cloud serves MCP at https://mcp.beacon.sh)", err)
}
checked := "not checked (--dry-run)"
if !mcpConnectOpts.dryRun {
@@ -263,7 +263,7 @@ func runMCPConnect(cmd *cobra.Command, args []string) error {
return err
}
- fmt.Fprintf(out, "Beacon Managed MCP: %s (%s)\n", url, checked)
+ fmt.Fprintf(out, "Beacon Cloud MCP: %s (%s)\n", url, checked)
fmt.Fprintf(out, "Server name: %s\n", mcpconnect.ServerName)
if opts.TokenEnv != "" {
fmt.Fprintf(out, "Auth: a personal MCP token read from $%s; Beacon writes only the variable's name\n", opts.TokenEnv)
@@ -457,7 +457,7 @@ func runMCPDisconnect(cmd *cobra.Command, args []string) error {
}
}
if removed == 0 && len(failed) == 0 && leftAlone == 0 {
- fmt.Fprintln(out, "Nothing to remove: no Beacon Managed MCP entry written by Beacon was found.")
+ fmt.Fprintln(out, "Nothing to remove: no Beacon Cloud MCP entry written by Beacon was found.")
}
if len(failed) > 0 {
return fmt.Errorf("could not disconnect %s", strings.Join(failed, ", "))
@@ -562,9 +562,9 @@ func runMCPStatus(cmd *cobra.Command, args []string) error {
func printStatus(out io.Writer, home string, report mcpStatusReport) {
fmt.Fprintf(out, "Server name: %s\n", report.ServerName)
if report.URL != "" {
- fmt.Fprintf(out, "Beacon Managed MCP URL: %s\n", report.URL)
+ fmt.Fprintf(out, "Beacon Cloud MCP URL: %s\n", report.URL)
} else {
- fmt.Fprintln(out, "Beacon Managed MCP URL: unknown (run `beacon endpoint connect`, or pass --url)")
+ fmt.Fprintln(out, "Beacon Cloud MCP URL: unknown (run `beacon endpoint connect`, or pass --url)")
}
if report.Check != "" {
fmt.Fprintf(out, "URL check: %s\n", report.Check)
diff --git a/cli/beacon/cmd/mcp_connect_test.go b/cli/beacon/cmd/mcp_connect_test.go
index ba6fbe5f..5a73876f 100644
--- a/cli/beacon/cmd/mcp_connect_test.go
+++ b/cli/beacon/cmd/mcp_connect_test.go
@@ -438,7 +438,7 @@ func TestMCPConnectDerivesTheURLFromTheManagedConnection(t *testing.T) {
if err != nil {
t.Fatal(err)
}
- if !strings.Contains(stdout, "Beacon Managed MCP: "+fx.url+" (checked)") {
+ if !strings.Contains(stdout, "Beacon Cloud MCP: "+fx.url+" (checked)") {
t.Fatalf("output:\n%s", stdout)
}
}
@@ -518,7 +518,7 @@ func TestMCPConnectTokenEnvPrintsTheVariable(t *testing.T) {
func TestMCPServerNamesDoNotCollide(t *testing.T) {
if mcpconnect.ServerName == "beacon" {
- t.Fatal("the Beacon Managed server must not share the local stdio server's name")
+ t.Fatal("the Beacon Cloud server must not share the local stdio server's name")
}
}
@@ -553,7 +553,7 @@ func TestMCPStatusWithoutCheckUsesTheURLConnectWrote(t *testing.T) {
if err != nil {
t.Fatal(err)
}
- if !strings.Contains(stdout, "Beacon Managed MCP URL: "+fx.url) || strings.Contains(stdout, "other URL") {
+ if !strings.Contains(stdout, "Beacon Cloud MCP URL: "+fx.url) || strings.Contains(stdout, "other URL") {
t.Fatalf("status compared against the derived URL:\n%s", stdout)
}
if n := len(fx.requests.all()); n != afterConnect {
@@ -567,7 +567,7 @@ func TestMCPStatusFallsBackToTheRecordedURLWithoutAnEnrollment(t *testing.T) {
t.Fatal(err)
}
stdout, _, err := runMCP(t, "status")
- if err != nil || !strings.Contains(stdout, "Beacon Managed MCP URL: "+fx.url) || strings.Contains(stdout, "other URL") {
+ if err != nil || !strings.Contains(stdout, "Beacon Cloud MCP URL: "+fx.url) || strings.Contains(stdout, "other URL") {
t.Fatalf("err = %v\n%s", err, stdout)
}
}
@@ -580,7 +580,7 @@ func TestMCPStatusCheckUsesTheRecordedURLWithoutAnEnrollment(t *testing.T) {
t.Fatal(err)
}
stdout, _, err := runMCP(t, "status", "--check")
- if err != nil || !strings.Contains(stdout, "URL check: ok") || !strings.Contains(stdout, "Beacon Managed MCP URL: "+fx.url) {
+ if err != nil || !strings.Contains(stdout, "URL check: ok") || !strings.Contains(stdout, "Beacon Cloud MCP URL: "+fx.url) {
t.Fatalf("err = %v\n%s", err, stdout)
}
// With nothing recorded and no enrollment, --check still fails, and says why.
diff --git a/cli/beacon/cmd/mcp_token.go b/cli/beacon/cmd/mcp_token.go
index 81aad96a..b55c3b6d 100644
--- a/cli/beacon/cmd/mcp_token.go
+++ b/cli/beacon/cmd/mcp_token.go
@@ -13,7 +13,7 @@ import (
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/account"
)
-// `beacon mcp token create` mints a personal Beacon Managed MCP token with the signed-in account.
+// `beacon mcp token create` mints a personal Beacon Cloud MCP token with the signed-in account.
// The token goes to stdout exactly once, so it can be captured into a variable for
// `beacon mcp connect --token-env`; everything else goes to stderr. It is never written to a
// file, and the account token that authorizes the request is never printed.
@@ -35,13 +35,13 @@ var mcpTokenOpts struct {
var mcpTokenCmd = &cobra.Command{
Use: "token",
- Short: "Manage personal Beacon Managed MCP tokens",
+ Short: "Manage personal Beacon Cloud MCP tokens",
}
var mcpTokenCreateCmd = &cobra.Command{
Use: "create",
- Short: "Create a personal Beacon Managed MCP token with your Beacon sign-in",
- Long: `Create a personal Beacon Managed MCP token for the account signed in with ` + "`beacon login`" + `.
+ Short: "Create a personal Beacon Cloud MCP token with your Beacon sign-in",
+ Long: `Create a personal Beacon Cloud MCP token for the account signed in with ` + "`beacon login`" + `.
The token is printed to stdout once and cannot be shown again; progress and details go to
stderr. Capture it into a variable and reference that variable with
@@ -50,7 +50,7 @@ stderr. Capture it into a variable and reference that variable with
export BEACON_MCP_TOKEN="$(beacon mcp token create --name laptop)"
beacon mcp connect --token-env BEACON_MCP_TOKEN
-The token reads your Beacon Managed data and counts toward the limit of 25 active tokens.
+The token reads your Beacon Cloud data and counts toward the limit of 25 active tokens.
Revoke it at beacon.sh → Dashboard → MCP Access. Beacon never writes it to a file.`,
SilenceUsage: true,
Args: cobra.NoArgs,
diff --git a/cli/beacon/internal/account/login.go b/cli/beacon/internal/account/login.go
index a2c0b765..e9d2a7ce 100644
--- a/cli/beacon/internal/account/login.go
+++ b/cli/beacon/internal/account/login.go
@@ -34,7 +34,7 @@ const (
CLIGrantVersion = "2026-09-01"
ScopeProfileRead = "profile:read"
ScopeDeviceEnroll = "device:enroll"
- // ScopeMCPTokenCreate lets the account token mint personal Beacon Managed MCP
+ // ScopeMCPTokenCreate lets the account token mint personal Beacon Cloud MCP
// tokens (`beacon mcp token create`). The sign-in page lists it, and beacon.sh
// approves the sign-in only when the permissions it showed match these.
ScopeMCPTokenCreate = "mcp:token:create"
diff --git a/cli/beacon/internal/account/mcp_token.go b/cli/beacon/internal/account/mcp_token.go
index c7de4266..03ef07d9 100644
--- a/cli/beacon/internal/account/mcp_token.go
+++ b/cli/beacon/internal/account/mcp_token.go
@@ -66,7 +66,7 @@ func ValidateMCPTokenRequest(req MCPTokenRequest) error {
return nil
}
-// CreateMCPToken mints a personal Beacon Managed MCP token for the signed-in user. The account
+// CreateMCPToken mints a personal Beacon Cloud MCP token for the signed-in user. The account
// token authorizes the request and is sent only to the session's own auth service.
func CreateMCPToken(ctx context.Context, session Session, req MCPTokenRequest, client *http.Client) (*MCPToken, error) {
req.Name = strings.TrimSpace(req.Name)
diff --git a/cli/beacon/internal/endpoint/asymptote/pack/README.md b/cli/beacon/internal/endpoint/asymptote/pack/README.md
index f8e31522..65264f01 100644
--- a/cli/beacon/internal/endpoint/asymptote/pack/README.md
+++ b/cli/beacon/internal/endpoint/asymptote/pack/README.md
@@ -1,6 +1,6 @@
# Beacon Endpoint Agent Managed Forwarding Pack
-This pack forwards Beacon endpoint JSONL events to Beacon Managed so they appear
+This pack forwards Beacon endpoint JSONL events to Beacon Cloud so they appear
on the Beacon dashboard. Beacon writes runtime
activity to `runtime.jsonl` and configuration inventory to
`inventory_state.jsonl`; Vector tails both files and POSTs gzip-compressed
diff --git a/cli/beacon/internal/endpoint/dashboard/static/app.js b/cli/beacon/internal/endpoint/dashboard/static/app.js
index def77cec..db60c83b 100644
--- a/cli/beacon/internal/endpoint/dashboard/static/app.js
+++ b/cli/beacon/internal/endpoint/dashboard/static/app.js
@@ -1058,7 +1058,7 @@ function inventoryTableForView(view, ctx) {
{ label: "Agent Runtime", render: (row) => inventoryRuntimeCell(inventoryRuntimeValue(row)) },
{ label: "Scope", render: (row) => row.source_scope || row.scope ? badge(row.source_scope || row.scope, "badge-muted") : `<span class="muted">-</span>` },
{ label: "Status", render: (row) => badge(row.status || (row.installed ? "configured" : "not_installed"), row.installed ? "badge-ok" : "badge-muted") },
- { label: "Beacon Managed", render: (row) => row.beacon_managed ? badge("managed", "badge-ok") : `<span class="muted">no</span>` },
+ { label: "Beacon Cloud", render: (row) => row.beacon_managed ? badge("managed", "badge-ok") : `<span class="muted">no</span>` },
{ label: "Modified", className: "nowrap", render: (row) => row.modified_at ? escapeHTML(formatTime(row.modified_at)) : `<span class="muted">-</span>` },
{ label: "Manifest SHA", className: "mono sha-cell", render: (row) => hashCell(row.file_sha256 || row.path_hash) },
{ label: "Manifest", className: "mono path-cell", render: (row) => escapeHTML(row.path || row.path_hash || "") },
@@ -1076,7 +1076,7 @@ function inventoryTableForView(view, ctx) {
{ label: "Kind", render: (row) => escapeHTML(configKindLabel(row.config_kind)) },
{ label: "Parser", render: parserBadge },
{ label: "MCP", render: (row) => escapeHTML(row.mcp_server_count ?? 0) },
- { label: "Beacon Managed", render: (row) => row.beacon_managed ? badge("managed", "badge-ok") : `<span class="muted">no</span>` },
+ { label: "Beacon Cloud", render: (row) => row.beacon_managed ? badge("managed", "badge-ok") : `<span class="muted">no</span>` },
{ label: "Modified", className: "nowrap", render: (row) => row.modified_at ? escapeHTML(formatTime(row.modified_at)) : `<span class="muted">-</span>` },
{ label: "Manifest SHA", className: "mono sha-cell", render: (row) => hashCell(row.file_sha256) },
{ label: "Path", className: "mono path-cell", render: (row) => escapeHTML(row.path || row.path_hash || "") },
@@ -1367,7 +1367,7 @@ function renderHookInventoryCards(hooks, hookConfigs) {
{ label: "Hook Targets", value: hooks.length, hint: "runtimes probed" },
{ label: "Hooks Installed", value: installed, hint: "reporting to Beacon" },
{ label: "Hook Manifests", value: hookConfigs.length, hint: "discovered files" },
- { label: "Beacon Managed", value: managed, hint: "managed manifests" },
+ { label: "Beacon Cloud", value: managed, hint: "managed manifests" },
];
el.innerHTML = cards
.map((card) => `
diff --git a/cli/beacon/internal/endpoint/dashboard/static/inventory-hooks.html b/cli/beacon/internal/endpoint/dashboard/static/inventory-hooks.html
index b9bd064d..07743327 100644
--- a/cli/beacon/internal/endpoint/dashboard/static/inventory-hooks.html
+++ b/cli/beacon/internal/endpoint/dashboard/static/inventory-hooks.html
@@ -74,7 +74,7 @@
<th>Runtime</th>
<th>Status</th>
<th>Scope</th>
- <th>Beacon Managed</th>
+ <th>Beacon Cloud</th>
<th>Binary</th>
<th>Manifest</th>
<th>Message</th>
@@ -99,7 +99,7 @@
<th>Runtime</th>
<th>Scope</th>
<th>Parser</th>
- <th>Beacon Managed</th>
+ <th>Beacon Cloud</th>
<th>Modified</th>
<th>Manifest SHA</th>
<th>Manifest</th>
diff --git a/cli/beacon/internal/mcpconnect/engine.go b/cli/beacon/internal/mcpconnect/engine.go
index c875e184..92774a14 100644
--- a/cli/beacon/internal/mcpconnect/engine.go
+++ b/cli/beacon/internal/mcpconnect/engine.go
@@ -195,7 +195,7 @@ func vscodeInput() ordered {
return ordered{
{"type", "promptString"},
{"id", vscodeInputID},
- {"description", "Beacon Managed MCP token (" + TokenPage + ")"},
+ {"description", "Beacon Cloud MCP token (" + TokenPage + ")"},
{"password", true},
}
}
diff --git a/cli/beacon/internal/mcpconnect/harness_test.go b/cli/beacon/internal/mcpconnect/harness_test.go
index 20ad1c31..81d10d85 100644
--- a/cli/beacon/internal/mcpconnect/harness_test.go
+++ b/cli/beacon/internal/mcpconnect/harness_test.go
@@ -237,7 +237,7 @@ bearer_token_env_var = "BEACON_MCP_TOKEN"
{
"type": "promptString",
"id": "beacon-managed-token",
- "description": "Beacon Managed MCP token (beacon.sh → Dashboard → MCP Access)",
+ "description": "Beacon Cloud MCP token (beacon.sh → Dashboard → MCP Access)",
"password": true
}
]
diff --git a/cli/beacon/internal/mcpconnect/targets.go b/cli/beacon/internal/mcpconnect/targets.go
index 134e122f..d4bbda5c 100644
--- a/cli/beacon/internal/mcpconnect/targets.go
+++ b/cli/beacon/internal/mcpconnect/targets.go
@@ -10,18 +10,18 @@ import (
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/endpoint/harness"
)
-// ServerName is the name Beacon registers the Beacon Managed MCP server under in every harness.
+// ServerName is the name Beacon registers the Beacon Cloud MCP server under in every harness.
// The local stdio server `beacon mcp serve` is "beacon"; the two names differ so neither entry
// overwrites the other.
const ServerName = "beacon-managed"
-// TokenPage is where a person creates a personal Beacon Managed MCP token.
+// TokenPage is where a person creates a personal Beacon Cloud MCP token.
const TokenPage = "beacon.sh → Dashboard → MCP Access"
// vscodeInputID names the VS Code input variable that holds a token in token mode.
const vscodeInputID = "beacon-managed-token"
-// AuthMode is how a harness authenticates to Beacon Managed MCP.
+// AuthMode is how a harness authenticates to Beacon Cloud MCP.
type AuthMode string
const (
diff --git a/cli/beacon/internal/mcpconnect/urlcheck.go b/cli/beacon/internal/mcpconnect/urlcheck.go
index 5dcce653..c914b909 100644
--- a/cli/beacon/internal/mcpconnect/urlcheck.go
+++ b/cli/beacon/internal/mcpconnect/urlcheck.go
@@ -14,11 +14,11 @@ import (
"github.com/asymptote-labs/agent-beacon/cli/beacon/internal/endpoint/asymptote"
)
-// ErrNoURL means neither --url nor a Beacon Managed connection gives an MCP URL.
-var ErrNoURL = errors.New("no Beacon Managed MCP URL: run `beacon endpoint connect` to connect this endpoint to Beacon Managed, or pass --url")
+// ErrNoURL means neither --url nor a Beacon Cloud connection gives an MCP URL.
+var ErrNoURL = errors.New("no Beacon Cloud MCP URL: run `beacon endpoint connect` to connect this endpoint to Beacon Cloud, or pass --url")
// ResolveURL picks the MCP URL: the --url flag, else the ingest URL `beacon endpoint connect`
-// recorded plus /mcp, which is where the Beacon Managed backend serves MCP by default. derived
+// recorded plus /mcp, which is where the Beacon Cloud backend serves MCP by default. derived
// reports the second case; CheckURL then accepts the canonical URL the server names for itself.
func ResolveURL(flag, ingestURL string) (resolved string, derived bool, err error) {
if v := strings.TrimSpace(flag); v != "" {
@@ -46,7 +46,7 @@ func resourceMetadataURL(mcpURL string) (string, error) {
return u.Scheme + "://" + u.Host + "/.well-known/oauth-protected-resource", nil
}
-// CheckURL confirms that mcpURL is a Beacon Managed MCP server before anything is written: its
+// CheckURL confirms that mcpURL is a Beacon Cloud MCP server before anything is written: its
// origin must serve resource metadata whose "resource" is mcpURL. This is `beacon mcp connect`'s
// only network request (two when a derived URL is replaced by the canonical one), and nothing is
// sent with it -- no token, no cookie.
@@ -103,7 +103,7 @@ func fetchResource(ctx context.Context, client *http.Client, mcpURL string) (str
}
defer resp.Body.Close()
if resp.StatusCode != http.StatusOK {
- return "", fmt.Errorf("%s answered HTTP %d; it does not look like a Beacon Managed MCP server", metadataURL, resp.StatusCode)
+ return "", fmt.Errorf("%s answered HTTP %d; it does not look like a Beacon Cloud MCP server", metadataURL, resp.StatusCode)
}
var meta protectedResource
if err := json.NewDecoder(io.LimitReader(resp.Body, 64<<10)).Decode(&meta); err != nil {
diff --git a/cli/beacon/internal/onboarding/profile.go b/cli/beacon/internal/onboarding/profile.go
index 2a2835a2..4568f6ed 100644
--- a/cli/beacon/internal/onboarding/profile.go
+++ b/cli/beacon/internal/onboarding/profile.go
@@ -76,7 +76,7 @@ type Onboarding struct {
// New interactive installs choose local or asymptote; own_infra remains valid for
// profiles written by older versions and unattended/admin-managed deployments.
Destination string `json:"destination,omitempty"`
- // PrivacyMode applies only to Beacon Managed forwarding.
+ // PrivacyMode applies only to Beacon Cloud forwarding.
PrivacyMode string `json:"privacy_mode,omitempty"`
}
diff --git a/cli/beacon/internal/onboarding/wizard.go b/cli/beacon/internal/onboarding/wizard.go
index 31b39874..79e20b88 100644
--- a/cli/beacon/internal/onboarding/wizard.go
+++ b/cli/beacon/internal/onboarding/wizard.go
@@ -612,7 +612,7 @@ func (m wizardModel) View() string {
"account as it happens." +
"\n\nStop any time with `beacon endpoint disconnect`."
case privacyScreen:
- title = "Choose what Beacon Managed receives"
+ title = "Choose what Beacon Cloud receives"
var rows []string
for index, mode := range managedprivacy.Modes {
label, detail := privacyCopy(mode)
@@ -658,7 +658,7 @@ func (m wizardModel) View() string {
func destinationCopy(destination string) (string, string) {
switch destination {
case DestinationAsymptote:
- return "Beacon Managed (recommended)",
+ return "Beacon Cloud (recommended)",
"Free, unlimited cloud-based retention of all your agent sessions. " +
// Non-breaking hyphen: the wrapper treats a plain "-" as a break
// point and split this across lines as "AI-" / "powered".
diff --git a/cli/beacon/internal/onboarding/wizard_test.go b/cli/beacon/internal/onboarding/wizard_test.go
index a55ed3a8..163e5867 100644
--- a/cli/beacon/internal/onboarding/wizard_test.go
+++ b/cli/beacon/internal/onboarding/wizard_test.go
@@ -177,12 +177,12 @@ func TestWizardPresetManagedSkipsDestinationChoice(t *testing.T) {
}
}
-// The destination captions are the only place a first-time user learns why Managed
+// The destination captions are the only place a first-time user learns why Beacon Cloud
// exists. They used to describe the mechanism ("forward new events after you
// connect") and named no benefit at all.
func TestDestinationCaptionsNameTheValueNotTheMechanism(t *testing.T) {
managedLabel, managedDetail := destinationCopy(DestinationAsymptote)
- if !strings.Contains(managedLabel, "Beacon Managed") {
+ if !strings.Contains(managedLabel, "Beacon Cloud") {
t.Fatalf("managed label = %q", managedLabel)
}
for _, want := range []string{"Free, unlimited cloud-based retention", "AI\u2011powered search and analytics on Beacon's hosted dashboard", "Rich findings analyzing your AI usage, coming soon.", "full feature set"} {
@@ -197,7 +197,7 @@ func TestDestinationCaptionsNameTheValueNotTheMechanism(t *testing.T) {
}
// Local is a supported end state, not a penalty, and it is not feature-poor:
// the local dashboard ships the same Findings, Detections, Analytics and Token
- // Usage views. Claiming Managed adds those would be false, so the copy has to
+ // Usage views. Claiming Beacon Cloud adds those would be false, so the copy has to
// differentiate on scope, retention and durability instead.
for _, want := range []string{"this machine", "Nothing leaves your machine", "testing", "agent activity in one place"} {
if !strings.Contains(localDetail, want) {
diff --git a/docs/architecture/architecture.mdx b/docs/architecture/architecture.mdx
index b1f4b2dc..c480dd56 100644
--- a/docs/architecture/architecture.mdx
+++ b/docs/architecture/architecture.mdx
@@ -164,7 +164,7 @@ Beacon collects agent runtime telemetry and local endpoint configuration context
<Card title="Detections" icon="radar" href="/detections">
Run threat rules over local telemetry and review findings.
</Card>
- <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="cloud" href="/deployment/managed">
Review managed ingest, governance, investigations, and rollout support.
</Card>
</Columns>
diff --git a/docs/architecture/system-architecture.mdx b/docs/architecture/system-architecture.mdx
index dd949cc8..19bc4427 100644
--- a/docs/architecture/system-architecture.mdx
+++ b/docs/architecture/system-architecture.mdx
@@ -1,15 +1,15 @@
---
title: "System Architecture"
-description: "Compare the open-source Agent Beacon architecture with the managed Beacon platform architecture"
+description: "Compare the open-source Agent Beacon architecture with the Beacon Cloud architecture"
---
-Beacon supports two architecture paths: the open-source [Agent Beacon](/concepts/core-concepts#agent-beacon) architecture, which collects local, browser, in-code, [CI](/concepts/core-concepts#ci-telemetry), and [cloud telemetry](/concepts/core-concepts#cloud-agent-telemetry) on customer-controlled infrastructure, and the [Beacon Managed](/concepts/core-concepts#beacon-managed) architecture for centralized visibility, governance, detections, and investigations.
+Beacon supports two architecture paths: the open-source [Agent Beacon](/concepts/core-concepts#agent-beacon) architecture, which collects local, browser, in-code, [CI](/concepts/core-concepts#ci-telemetry), and [cloud telemetry](/concepts/core-concepts#cloud-agent-telemetry) on customer-controlled infrastructure, and the [Beacon Cloud](/concepts/core-concepts#beacon-cloud) architecture for centralized visibility, governance, detections, and investigations.
<Columns cols={2}>
<Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">
See how Agent Beacon collects, normalizes, stores, correlates, and detects agent telemetry across every supported surface.
</Card>
- <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="cloud" href="/deployment/managed">
Review managed ingest, governance, investigations, and rollout support.
</Card>
</Columns>
@@ -19,13 +19,13 @@ Beacon supports two architecture paths: the open-source [Agent Beacon](/concepts
| Architecture | Use when |
| --- | --- |
| Open Source Architecture | You want [open-source telemetry](/concepts/core-concepts#beacon) for supported local, CI, and cloud agent surfaces, with customer-controlled records and forwarding. |
-| Managed Architecture | You want [managed ingest](/concepts/core-concepts#beacon-managed), retention, search, detections, fleet visibility, identity mapping, approval visibility, SSO, RBAC, audit trails, and investigation workflows. |
+| Beacon Cloud Architecture | You want [managed ingest](/concepts/core-concepts#beacon-cloud), retention, search, detections, fleet visibility, identity mapping, approval visibility, SSO, RBAC, audit trails, and investigation workflows. |
## Related
<Columns cols={2}>
<Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">
- Choose between Open Source, Managed, and Private Deployment paths.
+ Choose between local Beacon, Beacon Cloud, and private deployment paths.
</Card>
<Card title="Core Concepts" icon="book-open" href="/concepts/core-concepts">
Review the concepts used across Beacon and Agent Beacon docs.
diff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdx
index 2513c42e..37288129 100644
--- a/docs/changelog/cli.mdx
+++ b/docs/changelog/cli.mdx
@@ -135,7 +135,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
is printed before any browser is opened, so it works when none can be, and
<kbd>esc</kbd> during the wait returns to the sign-in screen instead of ending the
install. `beacon endpoint install --no-browser` starts in URL mode.
-- **Choosing Beacon Managed connects the endpoint** · Confirming Managed installs
+- **Choosing Beacon Cloud connects the endpoint** · Confirming Beacon Cloud installs
Beacon and then enrolls the device and starts the forwarder, rather than printing
`beacon endpoint connect` for you to run. The confirm screen states that forwarding
starts and names what the selected privacy mode sends, so that screen is where
@@ -148,7 +148,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
path: that screen offers no alternative until an attempt has actually failed.
- **Clearer, shorter onboarding copy** · The wizard explained itself twice and
repeated the same reassurance on three screens. The destination choice now
- describes what each option gives you: Managed as free, unlimited cloud-based
+ describes what each option gives you: Beacon Cloud as free, unlimited cloud-based
retention of every agent session with AI-powered search and analytics on Beacon's
hosted dashboard, Local as a dashboard for this machine where nothing leaves it,
each saying when to pick it. The managed disclosure is plain language.
@@ -229,10 +229,10 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
- **Account sign-in and safer first-run onboarding** · `beacon login`, `whoami`,
and `logout` add browser PKCE account authentication without enabling forwarding.
Interactive user installs now use a full-screen wizard that requires sign-in,
- preselects Beacon Managed, offers Standard or Metadata-only privacy, and records
+ preselects Beacon Cloud, offers Standard or Metadata-only privacy, and records
intent without moving telemetry. System, package, MDM, CI, dry-run, and
redirected-input installs remain noninteractive and account-free.
-- **Beacon Managed privacy modes** · Managed forwarding can now use `standard` or
+- **Beacon Cloud privacy modes** · Beacon Cloud forwarding can now use `standard` or
`metadata-only`. Metadata-only removes retained prompts, responses, reasoning,
tool arguments and results, command output, raw fields, diffs, inventory
content, and MCP definitions locally before buffering or upload. Connect now
@@ -401,7 +401,7 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
### v1.3.9 · September 9, 2026
-- **Cloud agents can send telemetry to Beacon Managed** · Claude Code cloud sandboxes had two upload targets, a GCS or S3 bucket you own. `BEACON_CLOUD_UPLOAD=asymptote` with `BEACON_CLOUD_INGEST_URL` and a `BEACON_CLOUD_DEVICE_KEY` minted for the environment now posts the sandbox log to managed ingest, the same endpoint the laptop forwarder uses, so cloud-agent sessions appear in the dashboard beside endpoint sessions. New lines are sent on every Stop, in batches under the ingest limits; a revoked key is reported, never retried past the offset. See [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents).
+- **Cloud agents can send telemetry to Beacon Cloud** · Claude Code cloud sandboxes had two upload targets, a GCS or S3 bucket you own. `BEACON_CLOUD_UPLOAD=asymptote` with `BEACON_CLOUD_INGEST_URL` and a `BEACON_CLOUD_DEVICE_KEY` minted for the environment now posts the sandbox log to managed ingest, the same endpoint the laptop forwarder uses, so cloud-agent sessions appear in the dashboard beside endpoint sessions. New lines are sent on every Stop, in batches under the ingest limits; a revoked key is reported, never retried past the offset. See [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents).
### v1.3.8 · September 7, 2026
@@ -493,16 +493,16 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
formula now depends on `vector` so a Homebrew install can connect without a
second step.
- **`beacon endpoint connect` and `disconnect`** · Connect an endpoint to
- Beacon managed ingest from the CLI: it finds Vector (0.56+), opens the
+ Beacon Cloud ingest from the CLI: it finds Vector (0.56+), opens the
dashboard's device approval page, receives a per-device key through a
loopback PKCE exchange, stores it in a `0600` secrets file, renders and
validates the forwarder config, and starts `com.beacon.endpoint.asymptote-forwarder`
(launchd) or `beacon-asymptote-forwarder.service` (systemd) in user or system
- mode. `beacon endpoint status` gains an "Beacon managed ingest" line and a
+ mode. `beacon endpoint status` gains an "Beacon Cloud ingest" line and a
`managed_ingest` JSON object with forwarder state and a live credential check;
`config.json` gains a non-secret `managed_ingest` block; uninstall removes the
forwarder and credentials. Re-running connect rotates the key in place.
-- **Beacon Managed forwarding pack** · `beacon endpoint asymptote` generates a
+- **Beacon Cloud forwarding pack** · `beacon endpoint asymptote` generates a
Vector `http` forwarder that posts the runtime and inventory JSONL to
Beacon's ingest service with a per-device key read from a `0600` secrets
file, plus a credential smoke test and sample events. It is the first Beacon
@@ -1123,14 +1123,14 @@ Stay up to date with the latest changes to the Agent Beacon CLI.
### v0.0.59 · June 13, 2026
-- **Managed ingest commands** · Added `beacon ingest` commands for checking managed ingest status and uploading endpoint telemetry to configured Beacon Managed destinations.
+- **Managed ingest commands** · Added `beacon ingest` commands for checking managed ingest status and uploading endpoint telemetry to configured Beacon Cloud destinations.
- **Endpoint token reporting** · Added `beacon endpoint tokens` for local token, cost, model, session, run, harness, and repository attribution from Beacon runtime logs.
- **Token attribution fixes** · Improved token usage normalization for Claude Code telemetry, cumulative metric batches, composite run IDs, and SDK session attributes.
### v0.0.58 · June 13, 2026
- **Token usage foundation** · Added token usage aggregation, dashboard token views, and trace identity fields so endpoint activity can report usage and cost consistently.
-- **Managed ingest support** · Added the endpoint ingest plumbing that lets authenticated Beacon clients upload endpoint telemetry to Beacon Managed when configured.
+- **Managed ingest support** · Added the endpoint ingest plumbing that lets authenticated Beacon clients upload endpoint telemetry to Beacon Cloud when configured.
- **Telemetry schema updates** · Added trace identity, usage cost, and int64 token count fields while preserving local runtime log workflows.
### v0.0.57 · June 11, 2026
diff --git a/docs/cli/account-auth.mdx b/docs/cli/account-auth.mdx
index f3b37f3b..debe302e 100644
--- a/docs/cli/account-auth.mdx
+++ b/docs/cli/account-auth.mdx
@@ -97,7 +97,7 @@ The CLI uses the versioned `2026-09-01` grant contract:
- `POST /api/cli/auth/init` registers the PKCE challenge, state, loopback port, CLI version, operating system, and architecture.
- `GET /cli/auth?state=...&port=...&scopes=...` authenticates the person, lists every requested scope (space-separated in `scopes`), and redirects to the loopback callback with `state` and a one-time `exchange_code`.
- `POST /api/cli/auth/exchange` accepts the exchange code, state, and PKCE verifier. It returns a scoped access token, expiry, user identity, organization memberships, and optional active organization.
-- `POST /api/cli/mcp/tokens` accepts `{"name": ..., "expires_in_days": ...}` with the access token as a Bearer credential and returns a personal Beacon Managed MCP token (`token`, `access_token` metadata, `mcp_url`). It requires `mcp:token:create`.
+- `POST /api/cli/mcp/tokens` accepts `{"name": ..., "expires_in_days": ...}` with the access token as a Bearer credential and returns a personal Beacon Cloud MCP token (`token`, `access_token` metadata, `mcp_url`). It requires `mcp:token:create`.
- `POST /api/cli/auth/revoke` accepts the access token as a Bearer credential and revokes it.
`beacon login` requests `profile:read`, `device:enroll` and `mcp:token:create`. A later `beacon endpoint connect` can use `device:enroll` to mint a device-specific ingest key without treating the account token as an ingest credential, and `beacon mcp token create` uses `mcp:token:create` to mint a personal MCP token. beacon.sh approves the sign-in only when the permissions its page showed match the ones the CLI registered, so a crafted link cannot hide one. A session from an older `beacon login` lacks `mcp:token:create`; run `beacon login` again to create MCP tokens from the CLI.
diff --git a/docs/cli/asymptote.mdx b/docs/cli/asymptote.mdx
index bd51dae7..7686a7f7 100644
--- a/docs/cli/asymptote.mdx
+++ b/docs/cli/asymptote.mdx
@@ -151,7 +151,7 @@ curl -sS -o /dev/null -w '%{http_code}\n' "$BEACON_ASYMPTOTE_INGEST_URL/v1/inges
## Related
<Columns cols={2}>
- <Card title="Beacon managed forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
+ <Card title="Beacon Cloud forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
Wire contract, what leaves the machine, revocation, and offline behavior.
</Card>
<Card title="Log forwarding" icon="tower-broadcast" href="/log-forwarding">
diff --git a/docs/cli/cloud-gcs-setup.mdx b/docs/cli/cloud-gcs-setup.mdx
index b3692c30..9388d7c5 100644
--- a/docs/cli/cloud-gcs-setup.mdx
+++ b/docs/cli/cloud-gcs-setup.mdx
@@ -14,7 +14,7 @@ beacon cloud gcs setup
The helper creates or validates a bucket, creates a dedicated uploader service account, grants object upload access, creates a service-account key, and prints the `BEACON_CLOUD_GCS_*` environment variables for cloud agents.
<Warning>
- This self-serve flow passes a scoped Google service-account key into the provider-managed cloud agent environment. Use it for proof-of-concept testing and prototyping. For production enterprise deployments, use [Beacon Managed](/deployment/managed) or contact Beacon about secure forwarding in customer-managed infrastructure.
+ This self-serve flow passes a scoped Google service-account key into the provider-managed cloud agent environment. Use it for proof-of-concept testing and prototyping. For production enterprise deployments, use [Beacon Cloud](/deployment/managed) or contact Beacon about secure forwarding in customer-managed infrastructure.
</Warning>
## Examples
diff --git a/docs/cli/cloud-s3-setup.mdx b/docs/cli/cloud-s3-setup.mdx
index 31d7211a..34a28ad2 100644
--- a/docs/cli/cloud-s3-setup.mdx
+++ b/docs/cli/cloud-s3-setup.mdx
@@ -21,7 +21,7 @@ and prints `BEACON_CLOUD_UPLOAD=s3`, `BEACON_CLOUD_S3_BUCKET`,
<Warning>
This self-serve flow passes scoped AWS access keys into the provider-managed
cloud agent environment. Use it for proof-of-concept testing and prototyping.
- For production enterprise deployments, use [Beacon Managed](/deployment/managed)
+ For production enterprise deployments, use [Beacon Cloud](/deployment/managed)
or contact Beacon about secure forwarding in customer-managed infrastructure.
</Warning>
diff --git a/docs/cli/cloud.mdx b/docs/cli/cloud.mdx
index 2586a795..8bf2399f 100644
--- a/docs/cli/cloud.mdx
+++ b/docs/cli/cloud.mdx
@@ -56,7 +56,7 @@ prints the `BEACON_CLOUD_S3_*` and AWS credential variables.
These self-serve flows pass a scoped Google service-account key or AWS access
key into the provider-managed cloud agent environment. Use them for
proof-of-concept testing and prototyping. For production enterprise deployments, use
- [Beacon Managed](/deployment/managed) or contact Beacon about secure
+ [Beacon Cloud](/deployment/managed) or contact Beacon about secure
forwarding in customer-managed infrastructure.
</Warning>
diff --git a/docs/cli/endpoint-config.mdx b/docs/cli/endpoint-config.mdx
index 2431db22..0567a3c2 100644
--- a/docs/cli/endpoint-config.mdx
+++ b/docs/cli/endpoint-config.mdx
@@ -90,7 +90,7 @@ sudo beacon endpoint config validate --system
## Managed ingest block
-When the endpoint is connected to Beacon managed ingest, `config.json` carries a non-secret `managed_ingest` block:
+When the endpoint is connected to Beacon Cloud ingest, `config.json` carries a non-secret `managed_ingest` block:
| Field | Meaning |
|-------|---------|
diff --git a/docs/cli/endpoint-connect.mdx b/docs/cli/endpoint-connect.mdx
index e7191255..54948f25 100644
--- a/docs/cli/endpoint-connect.mdx
+++ b/docs/cli/endpoint-connect.mdx
@@ -1,6 +1,6 @@
---
title: "beacon endpoint connect"
-description: "Connect a Beacon endpoint to Beacon managed ingest, or disconnect it, and understand what the forwarder stores and sends."
+description: "Connect a Beacon endpoint to Beacon Cloud ingest, or disconnect it, and understand what the forwarder stores and sends."
---
## Command overview
@@ -39,7 +39,7 @@ A first connect that fails at `vector validate` or at loading the service saves
Re-running `connect` on a connected machine reuses its install id, so the server rotates the existing device's key in place instead of creating a second device. Because that rotation invalidates the key the running forwarder holds, the new config is validated before enrollment: a re-run whose config Vector rejects leaves the forwarder, its key, and its buffer untouched. Under launchd the new forwarder is loaded only after the old one has exited (Vector drains in-flight requests first), and if the new instance has not started within the wait, `connect` fails and points at `launchctl print` for the job (v1.3.2).
-Some steps can only fail after the server has issued the key: storing it, validating the config that carries the server's ingest URL, writing the service unit, starting the service, and recording the enrollment. `connect` writes `asymptote/connect-pending` as soon as the key arrives and removes it only when every step has succeeded. If a step in between fails, `connect` says the connect is incomplete and names the retry, and `beacon endpoint status` reports Beacon Managed as not connected with `connect_incomplete: true` in `--json`. On a re-connect, the forwarder still running holds the key the server just rotated out, so the previous enrollment record and config are not treated as a working connection. On a first connect, Beacon stops and removes any partial forwarder before returning the error, so a later onboarding retry can safely select local-only telemetry. Run `beacon endpoint connect` again once the cause is fixed. An approval that is cancelled or expires before a key is issued rotates nothing and leaves an existing connection as it was.
+Some steps can only fail after the server has issued the key: storing it, validating the config that carries the server's ingest URL, writing the service unit, starting the service, and recording the enrollment. `connect` writes `asymptote/connect-pending` as soon as the key arrives and removes it only when every step has succeeded. If a step in between fails, `connect` says the connect is incomplete and names the retry, and `beacon endpoint status` reports Beacon Cloud as not connected with `connect_incomplete: true` in `--json`. On a re-connect, the forwarder still running holds the key the server just rotated out, so the previous enrollment record and config are not treated as a working connection. On a first connect, Beacon stops and removes any partial forwarder before returning the error, so a later onboarding retry can safely select local-only telemetry. Run `beacon endpoint connect` again once the cause is fixed. An approval that is cancelled or expires before a key is issued rotates nothing and leaves an existing connection as it was.
## Privacy modes
@@ -114,7 +114,7 @@ beacon endpoint disconnect
`beacon endpoint status` prints one line for managed ingest: whether this endpoint is connected, organization and device identity, active privacy mode, forwarder state, credential validity, and disk-buffer size. `--json` exposes the same under `managed_ingest`.
```text
-Beacon Managed: connected to Beacon Test as device 807c6a11-…; forwarder loaded=true running=true; privacy Metadata only; credential valid
+Beacon Cloud: connected to Beacon Test as device 807c6a11-…; forwarder loaded=true running=true; privacy Metadata only; credential valid
```
`credential revoked` means the key was revoked or expired, or the approving user is no longer a member of the organization; Vector is logging 401s and dropping batches. Run `beacon endpoint connect --dashboard-url https://beacon.sh` again to re-enroll.
@@ -130,7 +130,7 @@ Vector keeps reading into an on-disk buffer (512 MiB for runtime, 256 MiB for in
## Related
<Columns cols={2}>
- <Card title="Beacon Managed forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
+ <Card title="Beacon Cloud forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
Wire contract, what leaves the machine, revocation, and offline behavior.
</Card>
<Card title="beacon endpoint asymptote" icon="terminal" href="/cli/asymptote">
diff --git a/docs/cli/endpoint-install.mdx b/docs/cli/endpoint-install.mdx
index 3636d562..6fd99cfb 100644
--- a/docs/cli/endpoint-install.mdx
+++ b/docs/cli/endpoint-install.mdx
@@ -51,7 +51,7 @@ The `claude` harness writes both Claude Code's OpenTelemetry settings and its us
| `--falcon-sourcetype <type>` | Optional Falcon LogScale parser or sourcetype |
| `--falcon-insecure-skip-verify` | Skip Falcon LogScale HEC TLS certificate verification |
| `--falcon-ca-file <path>` | Optional CA certificate path for Falcon LogScale HEC TLS verification |
-| `--connect` | After a successful install, attempt to connect this endpoint to Beacon managed ingest. User mode uses the signed-in CLI account; system mode opens browser approval. A connection failure does not roll back or fail the completed local install; verify with `beacon endpoint status --json` and retry with [`beacon endpoint connect`](/cli/endpoint-connect) |
+| `--connect` | After a successful install, attempt to connect this endpoint to Beacon Cloud ingest. User mode uses the signed-in CLI account; system mode opens browser approval. A connection failure does not roll back or fail the completed local install; verify with `beacon endpoint status --json` and retry with [`beacon endpoint connect`](/cli/endpoint-connect) |
## Interactive onboarding wizard
@@ -60,10 +60,10 @@ signs in through beacon.sh, then asks where this machine's telemetry should go:
| Answer | What happens |
|--------|--------------|
-| Beacon Managed (default) | Shows what will be sent, asks for Standard or Metadata-only privacy, then installs Beacon and connects this endpoint. The confirm screen states that forwarding starts before you accept. An endpoint that is already enrolled keeps its device key and is not re-enrolled. |
+| Beacon Cloud (default) | Shows what will be sent, asks for Standard or Metadata-only privacy, then installs Beacon and connects this endpoint. The confirm screen states that forwarding starts before you accept. An endpoint that is already enrolled keeps its device key and is not re-enrolled. |
| Local only | Explicitly opts out of managed forwarding. Nothing is sent anywhere. |
-`--connect` presets Beacon Managed and skips the destination question. Whether
+`--connect` presets Beacon Cloud and skips the destination question. Whether
connect was chosen in the wizard or by the flag, a failed enrollment leaves the
completed local install exiting successfully and prints `beacon endpoint connect` as
the retry command. Automation should verify
diff --git a/docs/cli/endpoint-onboarding.mdx b/docs/cli/endpoint-onboarding.mdx
index 2d4d0589..2af11cd6 100644
--- a/docs/cli/endpoint-onboarding.mdx
+++ b/docs/cli/endpoint-onboarding.mdx
@@ -20,12 +20,12 @@ Beacon does not repeat completed setup.
The first interactive `beacon endpoint install` opens a full-screen terminal wizard:
1. Sign in through beacon.sh using the same browser PKCE flow as [`beacon login`](/cli/account-auth).
-2. Choose **Local only** or **Beacon Managed**. Managed offers free, unlimited
+2. Choose **Local only** or **Beacon Cloud**. Beacon Cloud offers free, unlimited
cloud-based retention of every agent session. It adds AI-powered search and
analytics on Beacon's hosted dashboard, with rich findings analyzing your AI
usage coming soon. Local is a dashboard for this machine's telemetry,
kept for as long as the logs are on disk, with nothing leaving the machine.
-3. For Managed, choose **Standard** or **Metadata only** forwarding.
+3. For Beacon Cloud, choose **Standard** or **Metadata only** forwarding.
4. Review the destination and privacy mode, then confirm installation.
Move between choices with the arrow keys, continue with <kbd>enter</kbd>, and cancel
@@ -56,10 +56,10 @@ are:
An SSH session with X11 forwarding (`ssh -X`) counts as having a display.
Signing in establishes account identity only. It does not register a managed endpoint,
-start Vector, or send telemetry. Beacon Managed is preselected; choose Local explicitly
+start Vector, or send telemetry. Beacon Cloud is preselected; choose Local explicitly
to opt out of managed forwarding.
-Choosing Beacon Managed shows a separate disclosure: your agents' activity on this
+Choosing Beacon Cloud shows a separate disclosure: your agents' activity on this
machine will be sent to your Beacon account as it happens, and `beacon endpoint
disconnect` stops it. The screen makes no claim about data already on disk, because
the honest version of that claim needs a caveat: runtime events recorded before you
@@ -72,7 +72,7 @@ prompts, responses, reasoning, tool arguments/results, command output, raw field
diffs, and optional inventory content locally before upload. See
[`beacon endpoint connect`](/cli/endpoint-connect#privacy-modes) for the exact contract.
-Confirming Beacon Managed connects this endpoint in the same command, after the
+Confirming Beacon Cloud connects this endpoint in the same command, after the
local install succeeds. The confirm screen says so before you press enter, and names
what the selected privacy mode sends, so it is the point at which forwarding is
authorized. An endpoint that is already enrolled is not re-enrolled: enrollment
@@ -90,7 +90,7 @@ treating the machine as settled. Verify forwarding with `beacon endpoint status
--json`. The onboarding record itself is written only after the install succeeds, so
a failed install leaves nothing behind and asks again next time.
-The explicit `beacon endpoint install --connect` flag is unchanged: it presets Managed
+The explicit `beacon endpoint install --connect` flag is unchanged: it presets Beacon Cloud
and skips the destination question.
The wizard never appears non-interactively. Package postinstall scripts, MDM
@@ -112,7 +112,7 @@ remain account-free.
Set `BEACON_ONBOARDING=0` to suppress the wizard on an install that would otherwise be
interactive. There is no CLI flag for this: it exists for unattended CI and MDM
-workflows. `BEACON_MANAGED_INGEST=0` hides the Beacon Managed answer; explicit
+workflows. `BEACON_MANAGED_INGEST=0` hides the Beacon Cloud answer; explicit
`beacon endpoint install --connect` remains unaffected.
```bash title="Suppress the prompt"
@@ -148,7 +148,7 @@ since no account authorized that run. `--json` exposes all of them:
| Value | Printed as |
|-------|------------|
| `local` | local only (nothing forwarded) |
-| `asymptote` | Beacon Managed |
+| `asymptote` | Beacon Cloud |
`own_infra` remains readable for profiles created by older Beacon versions. New
interactive installs choose Local and can configure a customer-managed
diff --git a/docs/cli/endpoint-status.mdx b/docs/cli/endpoint-status.mdx
index a610b342..769218a5 100644
--- a/docs/cli/endpoint-status.mdx
+++ b/docs/cli/endpoint-status.mdx
@@ -61,7 +61,7 @@ Status includes:
- Endpoint diagnostics
- Destination configuration in JSON output, including Splunk HEC or Falcon LogScale HEC endpoint, index, source, and sourcetype when configured
- Last Beacon event in the runtime log, when present
-- Beacon Managed: whether this endpoint is connected (a connect that failed after the server issued the device key is reported as not connected, with `connect_incomplete: true` and the retry command), organization and device id, active privacy mode, forwarder service state, whether the device key is still accepted (`valid`, `revoked`, or `unknown` when offline), and disk-buffer size. In `--json` this is the `managed_ingest` object; account and device keys are never included. The line reports the connection for the install mode you asked about (`--user` or `--system`), even when the collector view switches to the system install because it holds the OTLP ports.
+- Beacon Cloud: whether this endpoint is connected (a connect that failed after the server issued the device key is reported as not connected, with `connect_incomplete: true` and the retry command), organization and device id, active privacy mode, forwarder service state, whether the device key is still accepted (`valid`, `revoked`, or `unknown` when offline), and disk-buffer size. In `--json` this is the `managed_ingest` object; account and device keys are never included. The line reports the connection for the install mode you asked about (`--user` or `--system`), even when the collector view switches to the system install because it holds the OTLP ports.
- Inventory heartbeat: whether the scheduled inventory job is enabled and loaded, its interval, and when it last wrote. In `--json` this is the `inventory_heartbeat` object (`enabled`, `scheduled`, `interval`, `job`, `last_emitted_at`, `log_path`), reported for the requested install mode like managed ingest.
When Splunk HEC is configured, `--json` includes a `destinations.splunk_hec` object with `configured: true` and the non-secret destination settings. When Falcon LogScale HEC is configured, `--json` includes `destinations.falcon_hec` with the same non-secret fields. HEC tokens are not printed. File-based destinations such as Wazuh, Elastic, Datadog, Sumo Logic, Rapid7, Microsoft Sentinel, and AWS S3 validate against the configured runtime log path and their generated shipper configuration.
diff --git a/docs/cli/endpoint-uninstall.mdx b/docs/cli/endpoint-uninstall.mdx
index 5eb003f5..94554d02 100644
--- a/docs/cli/endpoint-uninstall.mdx
+++ b/docs/cli/endpoint-uninstall.mdx
@@ -61,7 +61,7 @@ Beacon removes files listed in its install manifest, including managed config, c
On a macOS system install, uninstall also stops and removes the S3, GCS, and Falcon forwarders that the package's MDM helpers install (`com.beacon.endpoint.s3-forwarder`, `gcs-forwarder`, and `falcon-forwarder`). Unless `--keep-config` is set, it deletes `/Library/Application Support/Beacon/Forwarders`, which holds their credentials. `beacon endpoint repair` leaves these forwarders running.
-If the endpoint was connected to Beacon managed ingest, uninstall also stops and removes the `com.beacon.endpoint.asymptote-forwarder` service (or `beacon-asymptote-forwarder.service`) and the `asymptote/` directory holding the Vector config, buffer, enrollment record and device key; `--keep-config` keeps the enrollment record and key. The device stays registered server-side until it is revoked from the dashboard's Beacon Endpoints page.
+If the endpoint was connected to Beacon Cloud ingest, uninstall also stops and removes the `com.beacon.endpoint.asymptote-forwarder` service (or `beacon-asymptote-forwarder.service`) and the `asymptote/` directory holding the Vector config, buffer, enrollment record and device key; `--keep-config` keeps the enrollment record and key. The device stays registered server-side until it is revoked from the dashboard's Beacon Endpoints page.
## Related
diff --git a/docs/cli/index.mdx b/docs/cli/index.mdx
index 45e7270f..2921a28b 100644
--- a/docs/cli/index.mdx
+++ b/docs/cli/index.mdx
@@ -41,7 +41,7 @@ Top-level Agent Beacon CLI commands.
| [`beacon login`](/cli/account-auth) | Sign in through beacon.sh without enabling telemetry forwarding. |
| [`beacon logout`](/cli/account-auth#sign-out) | Revoke and remove the local Beacon account session. |
| [`beacon memory`](/cli/memory) | Evaluate traces, review candidates, and install approved project memory. |
-| [`beacon mcp`](/cli/mcp) | Expose Beacon activity to MCP clients, locally and through Beacon Managed. |
+| [`beacon mcp`](/cli/mcp) | Expose Beacon activity to MCP clients, locally and through Beacon Cloud. |
| [`beacon rules`](/cli/rules) | Manage and author Beacon threat-detection rules. |
| [`beacon scan`](/cli/scan) | Run threat-detection rules over local endpoint telemetry. |
| [`beacon status`](/cli/endpoint-status) | Alias for `beacon endpoint status`. |
@@ -137,9 +137,9 @@ Expose local Beacon runtime activity through MCP.
|---------|-------------|
| [`beacon mcp serve`](/cli/mcp-serve) | Run the local Beacon MCP server over stdio or loopback HTTP JSON-RPC. |
| [`beacon mcp doctor`](/cli/mcp-doctor) | Validate local Beacon MCP setup and print client configuration. |
-| [`beacon mcp connect`](/cli/mcp-connect) | Register Beacon Managed MCP (`beacon-managed`) in every detected harness. |
-| [`beacon mcp disconnect`](/cli/mcp-connect#beacon-mcp-disconnect) | Remove the Beacon Managed MCP entries that connect wrote. |
-| [`beacon mcp status`](/cli/mcp-connect#beacon-mcp-status) | Show where Beacon Managed MCP is configured. |
+| [`beacon mcp connect`](/cli/mcp-connect) | Register Beacon Cloud MCP (`beacon-managed`) in every detected harness. |
+| [`beacon mcp disconnect`](/cli/mcp-connect#beacon-mcp-disconnect) | Remove the Beacon Cloud MCP entries that connect wrote. |
+| [`beacon mcp status`](/cli/mcp-connect#beacon-mcp-status) | Show where Beacon Cloud MCP is configured. |
## beacon endpoint
@@ -176,7 +176,7 @@ Manage the local endpoint agent and inspect supported agent harness telemetry.
| [`beacon endpoint cloudwatch`](/cli/cloudwatch) | Generate AWS CloudWatch Logs forwarding content for Beacon endpoint events. |
| [`beacon endpoint s3`](/cli/s3) | Generate AWS S3 forwarding content for Beacon endpoint events. |
| [`beacon endpoint gcs`](/cli/gcs) | Generate Google Cloud Storage forwarding content for Beacon endpoint events. |
-| [`beacon endpoint asymptote`](/cli/asymptote) | Generate the Vector forwarding pack for Beacon managed ingest and write validation events. |
+| [`beacon endpoint asymptote`](/cli/asymptote) | Generate the Vector forwarding pack for Beacon Cloud ingest and write validation events. |
| [`beacon endpoint hooks`](/cli/hooks) | Manage supported hook-based endpoint telemetry. |
| [`beacon endpoint opencode`](/cli/endpoint-opencode) | Collect endpoint telemetry from OpenCode session records on this machine. |
| [`beacon endpoint pi`](/cli/endpoint-pi) | Collect endpoint telemetry from Pi session records on this machine. |
@@ -332,7 +332,7 @@ Generate Google Cloud Storage forwarding content and validation events for Beaco
beacon endpoint asymptote [command]
```
-Generate the Vector forwarding pack that sends Beacon endpoint events to Beacon managed ingest, and write validation events.
+Generate the Vector forwarding pack that sends Beacon endpoint events to Beacon Cloud ingest, and write validation events.
| Command | Description |
|---------|-------------|
diff --git a/docs/cli/install.mdx b/docs/cli/install.mdx
index 0335f097..528d4a57 100644
--- a/docs/cli/install.mdx
+++ b/docs/cli/install.mdx
@@ -30,7 +30,7 @@ beacon version
`brew trust` is a one-time step for newer Homebrew releases before loading
third-party formulae from the tap.
-On macOS the formula also depends on `asymptote-labs/tap/beacon-vector`, the tap's mirror of Vector's releases (Vector is not in homebrew-core), which runs the optional [Beacon Managed forwarder](/cli/endpoint-connect); Homebrew installs it alongside Beacon so no second step is needed.
+On macOS the formula also depends on `asymptote-labs/tap/beacon-vector`, the tap's mirror of Vector's releases (Vector is not in homebrew-core), which runs the optional [Beacon Cloud forwarder](/cli/endpoint-connect); Homebrew installs it alongside Beacon so no second step is needed.
The mirror is named `beacon-vector` rather than `vector` on purpose. Homebrew allows exactly one keg named `vector` no matter which tap it came from, so a mirror by that name could not be installed at all on a machine that already had Vector from `vectordotdev/brew`. Under its own name it coexists with any Vector you already run, and because it keeps its binary in `libexec` — which Homebrew never links — it stays off your PATH and never shadows one. Beacon finds it by path; you do not need to configure anything.
diff --git a/docs/cli/mcp-connect.mdx b/docs/cli/mcp-connect.mdx
index a9103468..5044d045 100644
--- a/docs/cli/mcp-connect.mdx
+++ b/docs/cli/mcp-connect.mdx
@@ -1,12 +1,12 @@
---
title: "beacon mcp connect"
-description: "Register Beacon Managed MCP in every harness on this machine"
+description: "Register Beacon Cloud MCP in every harness on this machine"
---
## Command overview
-`beacon mcp connect` adds the Beacon Managed MCP server to the MCP configuration of each harness it
-finds, so an agent can search the session history this endpoint forwards to Beacon Managed.
+`beacon mcp connect` adds the Beacon Cloud MCP server to the MCP configuration of each harness it
+finds, so an agent can search the session history this endpoint forwards to Beacon Cloud.
`beacon mcp disconnect` removes exactly what connect added, and `beacon mcp status` shows what is
configured where.
@@ -23,14 +23,14 @@ with different names, so neither entry ever overwrites the other:
| Server name | What it reads | Where it runs | Set up with |
|---|---|---|---|
| `beacon` | This machine's `runtime.jsonl` and approved local memory | Locally, over stdio or loopback HTTP | [`beacon mcp doctor`](/cli/mcp-doctor) prints the config |
-| `beacon-managed` | Session history this endpoint forwarded to Beacon Managed | Beacon Managed, over HTTPS | `beacon mcp connect` |
+| `beacon-managed` | Session history this endpoint forwarded to Beacon Cloud | Beacon Cloud, over HTTPS | `beacon mcp connect` |
-Beacon Managed MCP is read-only. Its tools are `beacon_search_sessions`, `beacon_grep`,
+Beacon Cloud MCP is read-only. Its tools are `beacon_search_sessions`, `beacon_grep`,
`beacon_read_session`, `beacon_get_event`, `beacon_lookup` and `beacon_usage`.
<Note>
`beacon mcp connect` is an explicit, opt-in command. `beacon endpoint install` and the onboarding
- wizard never run it; after you choose Beacon Managed in the wizard, the install only suggests it.
+ wizard never run it; after you choose Beacon Cloud in the wizard, the install only suggests it.
It refuses to run as root, and in CI or without a terminal it runs only with `--yes`.
</Note>
@@ -41,7 +41,7 @@ beacon mcp connect
```
```text title="Example output"
-Beacon Managed MCP: https://mcp.beacon.sh (checked)
+Beacon Cloud MCP: https://mcp.beacon.sh (checked)
Server name: beacon-managed
Auth: OAuth; Beacon writes only the URL, and each harness signs in on first use
@@ -70,8 +70,8 @@ Connect works in these steps:
1. **Harnesses.** Without `--harness`, connect acts on every harness `beacon endpoint discover`
detects. `--harness` accepts the same names as `beacon endpoint install --harness`, such as
`claude`, `codex`, `cursor`, `vscode`, `gemini` and `opencode`.
-2. **URL.** The URL is `--url`, or the Beacon Managed URL recorded by
- [`beacon endpoint connect`](/cli/endpoint-connect) with `/mcp` added. The Beacon Managed backend
+2. **URL.** The URL is `--url`, or the Beacon Cloud URL recorded by
+ [`beacon endpoint connect`](/cli/endpoint-connect) with `/mcp` added. The Beacon Cloud backend
may name its own canonical MCP URL, `https://mcp.beacon.sh` in production. When it does, connect
uses that URL. Without either, connect stops and asks you to run `beacon endpoint connect` or
pass `--url`.
@@ -115,7 +115,7 @@ a comment in the config, because some harnesses rewrite their config files and d
| Flag | Description |
|------|-------------|
| `--harness a,b` | Harnesses to connect. Defaults to every detected harness |
-| `--url URL` | Beacon Managed MCP URL. Defaults to the URL recorded by `beacon endpoint connect` |
+| `--url URL` | Beacon Cloud MCP URL. Defaults to the URL recorded by `beacon endpoint connect` |
| `--token-env NAME` | Use a personal MCP token read from environment variable `NAME` instead of OAuth |
| `--dry-run` | Show the plan without checking the URL or writing anything |
| `--yes` | Write without asking |
@@ -124,7 +124,7 @@ a comment in the config, because some harnesses rewrite their config files and d
## Authentication: OAuth or a token
**OAuth is the default and the recommended mode.** Connect writes only the URL. The first time the
-harness connects, Beacon Managed answers `401` with a pointer to its OAuth metadata. The harness
+harness connects, Beacon Cloud answers `401` with a pointer to its OAuth metadata. The harness
then registers itself, opens a browser, and you approve access on beacon.sh. No secret is written
by Beacon, and access is revoked from the dashboard.
@@ -164,7 +164,7 @@ JSON on stdout instead. Beacon never writes the token to a file.
| `--expires-in-days N` | Days until the token expires, 1 to 366, or 0 for never (default 90) |
| `--json` | Print the token and its details as JSON |
-The token reads your Beacon Managed data, counts toward the limit of 25 active tokens, and is
+The token reads your Beacon Cloud data, counts toward the limit of 25 active tokens, and is
revoked at beacon.sh → Dashboard → MCP Access. It needs the `mcp:token:create` permission, which
`beacon login` requests and the sign-in page lists; a session from an older `beacon login` is
refused with a prompt to sign in again.
@@ -236,7 +236,7 @@ beacon mcp status --json
```text title="Example output"
Server name: beacon-managed
-Beacon Managed MCP URL: https://mcp.beacon.sh
+Beacon Cloud MCP URL: https://mcp.beacon.sh
URL check: ok
HARNESS CONFIGURED URL AUTH BY BEACON FILE
@@ -251,9 +251,9 @@ a variable), or `token` (the entry has a header written outside Beacon, whose va
shown). Status makes no network request unless you pass `--check`, which runs the same URL check
as connect and exits non-zero if it fails.
-## What Beacon Managed MCP can find
+## What Beacon Cloud MCP can find
-Beacon Managed MCP searches what this endpoint forwarded, which limits what it can find:
+Beacon Cloud MCP searches what this endpoint forwarded, which limits what it can find:
- Each retained string is capped at 4 KB before it is written locally. Text past that point in a
long tool output or diff is never forwarded, so it cannot be grepped.
@@ -273,7 +273,7 @@ See [Downstream consumers](/telemetry-schema/normalization#downstream-consumers)
Validate the local server and print its client config.
</Card>
<Card title="beacon endpoint connect" icon="cloud-arrow-up" href="/cli/endpoint-connect">
- Connect this endpoint to Beacon Managed.
+ Connect this endpoint to Beacon Cloud.
</Card>
<Card title="Redaction and size limits" icon="scissors" href="/security/retention-redaction">
What is retained, truncated and forwarded.
diff --git a/docs/cli/mcp-doctor.mdx b/docs/cli/mcp-doctor.mdx
index 35a2e5b1..36c49d93 100644
--- a/docs/cli/mcp-doctor.mdx
+++ b/docs/cli/mcp-doctor.mdx
@@ -51,8 +51,8 @@ With the stdio transport, doctor prints the client configuration for the local s
}
```
-This is not the Beacon Managed server. The session history this endpoint forwards to Beacon
-Managed is served by a separate server, registered as `beacon-managed` by
+This is not the Beacon Cloud server. The session history this endpoint forwards to Beacon
+Cloud is served by a separate server, registered as `beacon-managed` by
[`beacon mcp connect`](/cli/mcp-connect). A harness can have both entries at once, because the
names differ. Doctor checks only the local server; to see where `beacon-managed` is configured and
whether its URL answers, run `beacon mcp status --check`.
@@ -103,7 +103,7 @@ sudo beacon mcp doctor --system
Run the local Beacon MCP server after validation.
</Card>
<Card title="beacon mcp connect" icon="plug" href="/cli/mcp-connect">
- Register the separate Beacon Managed MCP server, `beacon-managed`.
+ Register the separate Beacon Cloud MCP server, `beacon-managed`.
</Card>
<Card title="Test MCP Access" icon="server" href="/guides/local-testing/mcp">
Understand Beacon MCP and test local client access.
diff --git a/docs/cli/mcp.mdx b/docs/cli/mcp.mdx
index d68fc63a..765c6a6b 100644
--- a/docs/cli/mcp.mdx
+++ b/docs/cli/mcp.mdx
@@ -1,6 +1,6 @@
---
title: "beacon mcp"
-description: "Expose Beacon activity to MCP clients, locally and through Beacon Managed"
+description: "Expose Beacon activity to MCP clients, locally and through Beacon Cloud"
---
## Command overview
@@ -19,7 +19,7 @@ and the local `memory.db` store next to the endpoint log base directory. It
supports stdio for desktop MCP clients and loopback HTTP JSON-RPC for local tools
that connect to a running server.
-## Local and Beacon Managed servers
+## Local and Beacon Cloud servers
Beacon has two MCP servers, registered under different names so that neither entry overwrites
the other:
@@ -27,7 +27,7 @@ the other:
| Server name | What it reads | Commands |
|---|---|---|
| `beacon` | This machine's `runtime.jsonl` and approved local memory, served locally over stdio or loopback HTTP | [`serve`](/cli/mcp-serve), [`doctor`](/cli/mcp-doctor) |
-| `beacon-managed` | The session history this endpoint forwards to Beacon Managed, served by Beacon Managed over HTTPS | [`connect`, `disconnect`, `status`, `token create`](/cli/mcp-connect) |
+| `beacon-managed` | The session history this endpoint forwards to Beacon Cloud, served by Beacon Cloud over HTTPS | [`connect`, `disconnect`, `status`, `token create`](/cli/mcp-connect) |
`beacon mcp connect` registers `beacon-managed` in Claude Code, Codex CLI, Cursor, VS Code,
Gemini CLI and OpenCode. By default it writes only the URL, and each harness signs in with OAuth.
@@ -50,7 +50,7 @@ server by hand.
Validate local Beacon MCP setup and print client configuration.
</Card>
<Card title="beacon mcp connect" icon="plug" href="/cli/mcp-connect">
- Register Beacon Managed MCP in every harness, and remove or inspect it with `disconnect` and `status`.
+ Register Beacon Cloud MCP in every harness, and remove or inspect it with `disconnect` and `status`.
</Card>
</Columns>
@@ -95,7 +95,7 @@ see [`beacon mcp connect`](/cli/mcp-connect#flags).
`beacon mcp serve` and `beacon mcp doctor` only read local Beacon runtime logs and
approved local memory. They do not require a Beacon account, and HTTP transport
should remain bound to loopback. `beacon mcp connect` is the one `beacon mcp`
- command that makes a network request: an opt-in check of the Beacon Managed MCP
+ command that makes a network request: an opt-in check of the Beacon Cloud MCP
URL before it writes harness configs.
</Note>
@@ -109,7 +109,7 @@ see [`beacon mcp connect`](/cli/mcp-connect#flags).
Validate local Beacon MCP setup.
</Card>
<Card title="beacon mcp connect" icon="plug" href="/cli/mcp-connect">
- Register Beacon Managed MCP in your harnesses.
+ Register Beacon Cloud MCP in your harnesses.
</Card>
<Card title="Connect Cursor and Claude Code" icon="plug" href="/guides/local-testing/mcp#4-connect-cursor-and-claude-code">
Install Beacon MCP in local assistant clients.
diff --git a/docs/concepts/core-concepts.mdx b/docs/concepts/core-concepts.mdx
index 62522117..5575fd08 100644
--- a/docs/concepts/core-concepts.mdx
+++ b/docs/concepts/core-concepts.mdx
@@ -3,7 +3,7 @@ title: "Core Concepts"
description: "Core concepts for Beacon, Agent Beacon, and agent runtime telemetry"
---
-Beacon observes AI agent runtime activity across supported local endpoints, CI jobs, cloud-agent sandboxes, and SDK-instrumented applications. Agent Beacon is the open-source foundation for local-first collection and customer-controlled forwarding. Beacon Managed builds on that foundation with hosted ingest, retention, search, detections, governance, and investigations.
+Beacon observes AI agent runtime activity across supported local endpoints, CI jobs, cloud-agent sandboxes, and SDK-instrumented applications. Agent Beacon is the open-source foundation for local-first collection and customer-controlled forwarding. Beacon Cloud builds on that foundation with hosted ingest, retention, search, detections, governance, and investigations.
Use this page as a quick reference for terms used across Beacon and Agent Beacon docs.
@@ -11,9 +11,9 @@ Use this page as a quick reference for terms used across Beacon and Agent Beacon
**Beacon** is the open-source, local-first telemetry system for supported AI agent activity. It collects events from local endpoints, CI jobs, and cloud-agent surfaces, normalizes them into consistent records, writes local JSONL, serves a local dashboard, and supports customer-managed forwarding. See [Open Source deployment](/deployment/open-source).
-## Beacon Managed
+## Beacon Cloud
-**Beacon Managed** is the hosted Beacon operating model for centralized ingest, retention, search, detections, fleet visibility, identity mapping, approval visibility, SSO, RBAC, audit trails, and investigation workflows. See [Managed deployment](/deployment/managed).
+**Beacon Cloud** is the hosted Beacon operating model for centralized ingest, retention, search, detections, fleet visibility, identity mapping, approval visibility, SSO, RBAC, audit trails, and investigation workflows. See [Beacon Cloud deployment](/deployment/managed).
## Endpoint agent
@@ -42,7 +42,7 @@ environment becomes available, so early bootstrap turns may precede telemetry.
## Observe SDK
-The **Observe SDK** is the `@asymptote/sdk` TypeScript package for instrumenting cloud-hosted agent applications, services, workers, serverless functions, and agent SDK integrations. It can export to Beacon Managed hosted Observe or to a customer-managed OTLP collector. See [Beacon Observe SDK](/sdk).
+The **Observe SDK** is the `@asymptote/sdk` TypeScript package for instrumenting cloud-hosted agent applications, services, workers, serverless functions, and agent SDK integrations. It can export to Beacon Cloud hosted Observe or to a customer-managed OTLP collector. See [Beacon Observe SDK](/sdk).
## Local collector
@@ -152,7 +152,7 @@ state, Token Usage, and Agent Inventory without requiring a hosted Beacon accoun
<Columns cols={2}>
<Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">
- Compare Beacon, Managed, and Private Deployment paths.
+ Compare local Beacon, Beacon Cloud, and private deployment paths.
</Card>
<Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">
See how runtime telemetry flows through collection, normalization, and local outputs.
diff --git a/docs/concepts/faq.mdx b/docs/concepts/faq.mdx
index 0539d6b4..19b49e86 100644
--- a/docs/concepts/faq.mdx
+++ b/docs/concepts/faq.mdx
@@ -1,6 +1,6 @@
---
title: "FAQ"
-description: "Clear answers about Agent Beacon open source telemetry and Beacon Managed architecture"
+description: "Clear answers about Agent Beacon open source telemetry and Beacon Cloud architecture"
---
This FAQ answers common architecture, telemetry, and deployment questions about
@@ -101,7 +101,7 @@ S3](/guides/fleet-s3-mdm).
For provider-managed cloud-agent proof-of-concept flows, the current self-serve
path uses Google Cloud Storage. Production cloud-agent ingest is handled through
-Beacon Managed or a customer-approved forwarding design.
+Beacon Cloud or a customer-approved forwarding design.
### Can open-source Beacon forward logs to Datadog or a SIEM?
@@ -145,19 +145,19 @@ No. The open-source endpoint path is local-first. Normal local hook execution,
local collection, local JSONL, the local dashboard, local scans, and
customer-managed forwarding do not require a hosted Beacon account.
-## Beacon Managed
+## Beacon Cloud
-Beacon Managed adds centralized ingest, retention, search, detections,
+Beacon Cloud adds centralized ingest, retention, search, detections,
governance, identity, approvals, access control, and investigation workflows on
top of the open-source Beacon foundation.
-### Does Beacon Managed provide a central console?
+### Does Beacon Cloud provide a central console?
-Yes. Beacon Managed provides the centralized operating layer for fleet-wide
+Yes. Beacon Cloud provides the centralized operating layer for fleet-wide
visibility, search, detections, investigations, policy workflows, identity
mapping, approvals, SSO, RBAC, and audit trails.
-Use Managed when local JSONL and customer-managed forwarding are not enough for
+Use Beacon Cloud when local JSONL and customer-managed forwarding are not enough for
company-wide operations.
### Should telemetry point to Beacon or directly to the SIEM?
@@ -166,11 +166,11 @@ Both patterns are valid.
With Agent Beacon open source, telemetry can go directly from local JSONL into
customer-controlled SIEM, log, or object-storage destinations. With Beacon
-Managed, telemetry is sent to Beacon for centralized search, detections,
+Cloud, telemetry is sent to Beacon for centralized search, detections,
governance, and investigations, with downstream forwarding available as part of
the deployment design.
-### Does Beacon Managed replace the SIEM?
+### Does Beacon Cloud replace the SIEM?
No. Beacon is focused on agent-specific visibility, governance, and
investigation workflows. SIEMs and log platforms remain important downstream
@@ -203,16 +203,16 @@ identify the Beacon collector machine.
### Where should a cloud AI tenant send OTLP telemetry?
-In a Managed deployment, the cloud service or tenant can export OTLP to an
-Beacon-managed collector endpoint when that runtime supports it.
+In a Beacon Cloud deployment, the cloud service or tenant can export OTLP to an
+Beacon Cloud collector endpoint when that runtime supports it.
In a private or customer-managed design, the OTLP endpoint may instead point to a
customer-controlled collector or forwarding layer. The right target depends on
the deployment model, data-boundary requirements, and destination architecture.
-### Does managed require a customer-hosted management server?
+### Does Beacon Cloud require a customer-hosted management server?
-Not necessarily. In Beacon Managed, Beacon operates the managed ingest and
+Not necessarily. In Beacon Cloud, Beacon operates the managed ingest and
control-plane services. For private deployments or stricter infrastructure
requirements, Beacon can work with the customer on dedicated or
customer-controlled deployment boundaries.
@@ -223,7 +223,7 @@ and forward through customer-managed shippers.
### Why is telemetry useful for cloud and non-engineering agents?
It is useful when the agent platform, OTLP export, hooks, or SDK instrumentation
-emits prompts, tools, files, commands, approvals, or workflow metadata. Managed
+emits prompts, tools, files, commands, approvals, or workflow metadata. Beacon Cloud
investigations can then reconstruct what the agent did, which tools it used, what
content was retained, and which user or workflow it maps to.
@@ -235,12 +235,12 @@ runtime signals the platform or instrumented application emits.
<Columns cols={2}>
<Card title="System Architecture" icon="diagram-project" href="/architecture/system-architecture">
- Compare the open-source Agent Beacon architecture with Beacon Managed.
+ Compare the open-source Agent Beacon architecture with Beacon Cloud.
</Card>
<Card title="Open Source Architecture" icon="diagram-project" href="/architecture/architecture">
Review local collection, normalization, storage, and forwarding.
</Card>
- <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="cloud" href="/deployment/managed">
Review managed ingest, governance, investigations, and rollout support.
</Card>
<Card title="Log Forwarding" icon="tower-broadcast" href="/log-forwarding">
diff --git a/docs/concepts/vector-forwarding.mdx b/docs/concepts/vector-forwarding.mdx
index 73e03734..70e6e3e0 100644
--- a/docs/concepts/vector-forwarding.mdx
+++ b/docs/concepts/vector-forwarding.mdx
@@ -14,7 +14,7 @@ flowchart LR
vectorPipeline -->|"other sinks"| customerDestinations["GCS, CloudWatch, Sumo, Rapid7, Falcon"]
end
- subgraph managedPath [Beacon Managed]
+ subgraph managedPath [Beacon Cloud]
managedSources["Endpoint, CI, cloud, and SDK telemetry"] -->|"managed ingest"| managedIngest["Beacon ingest"]
managedIngest --> managedPlatform["Hosted search, detections, governance, investigations"]
end
@@ -44,7 +44,7 @@ That is where Vector fits. For open-source deployments, Vector is an optional cu
- Retrying transient failures.
- Holding destination URLs, tokens, IAM roles, cloud credentials, and destination-specific settings.
-In **Beacon Managed**, the main path is different. Managed deployments use Beacon-hosted ingest, retention, search, detections, governance, identity mapping, and investigation workflows. Vector is not the required managed-ingest architecture. You might still use a customer-managed Vector pipeline for an additional archive or downstream copy, but the core managed product provides the central pipeline and operational surface.
+In **Beacon Cloud**, the main path is different. Beacon Cloud deployments use Beacon-hosted ingest, retention, search, detections, governance, identity mapping, and investigation workflows. Vector is not the required managed-ingest architecture. You might still use a customer-managed Vector pipeline for an additional archive or downstream copy, but the core managed product provides the central pipeline and operational surface.
## Why the handoff is local
@@ -299,7 +299,7 @@ Use the official Vector docs when adapting generated templates:
<Card title="Open Source deployment" icon="code-branch" href="/deployment/open-source">
See how Agent Beacon runs local-first with customer-controlled storage and forwarding.
</Card>
- <Card title="Managed deployment" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud deployment" icon="cloud" href="/deployment/managed">
Understand the hosted Beacon ingest, retention, search, detections, governance, and investigation model.
</Card>
<Card title="Endpoint event schema" icon="code" href="/telemetry-schema/event-schema">
diff --git a/docs/deployment/hosting-options.mdx b/docs/deployment/hosting-options.mdx
index 24167058..4d7de9e1 100644
--- a/docs/deployment/hosting-options.mdx
+++ b/docs/deployment/hosting-options.mdx
@@ -1,11 +1,11 @@
---
title: "Hosting Options"
-description: "Choose between local Beacon and Beacon Managed"
+description: "Choose between local Beacon and Beacon Cloud"
---
-Both options are free. Run Beacon locally with full control of your data, or use [Beacon Managed](/concepts/core-concepts#beacon-managed) for hosted storage, search, analytics, and unlimited retention.
+Both options are free. Run Beacon locally with full control of your data, or use [Beacon Cloud](/concepts/core-concepts#beacon-cloud) for hosted storage, search, analytics, and unlimited retention.
-| Capability | Local | Beacon Managed |
+| Capability | Local | Beacon Cloud |
| --- | --- | --- |
| Cross-harness agent telemetry | ✓ | ✓ |
| Local, CI & cloud collection | ✓ | ✓ |
@@ -81,9 +81,9 @@ The local path preserves `runtime.jsonl` on the endpoint and supports optional f
See [Local](/deployment/open-source) for setup details and [Security & IT Rollout Guide](/security) for managed endpoint deployment.
-## Beacon Managed
+## Beacon Cloud
-Use Managed when you want hosted visibility, governance, and enterprise rollout support for agent activity.
+Use Beacon Cloud when you want hosted visibility, governance, and enterprise rollout support for agent activity.
1. [Create a Beacon account](https://beacon.sh/sign-up).
2. Sign the CLI in on each user endpoint:
@@ -101,7 +101,7 @@ beacon endpoint connect --dashboard-url https://beacon.sh
Interactive `beacon endpoint install` performs the sign-in step when needed.
System-mode connect remains account-free and uses browser approval instead.
-Beacon Managed gives you the open-source Agent Beacon experience without having to run the backend yourself.
+Beacon Cloud gives you the open-source Agent Beacon experience without having to run the backend yourself.
For cloud-hosted agent applications, install the [Observe SDK](/concepts/core-concepts#observe-sdk) and initialize hosted export with a Beacon API key:
@@ -117,12 +117,12 @@ Observe.initialize({
});
```
-See [Beacon Managed](/deployment/managed) for managed platform capabilities and [SDK Quickstart](/sdk/quickstart) for cloud instrumentation details.
+See [Beacon Cloud](/deployment/managed) for managed platform capabilities and [SDK Quickstart](/sdk/quickstart) for cloud instrumentation details.
## Related
<Columns cols={2}>
- <Card title="Beacon Managed" icon="key" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="key" href="/deployment/managed">
Review managed ingest, governance, investigations, access control, and rollout support.
</Card>
<Card title="Local" icon="download" href="/deployment/open-source">
@@ -135,7 +135,7 @@ See [Beacon Managed](/deployment/managed) for managed platform capabilities and
Instrument cloud-hosted agent applications with hosted or customer-managed export.
</Card>
<Card title="Beacon Overview" icon="diagram-project" href="/get-started/overview">
- See how local Beacon fits with Beacon Managed.
+ See how local Beacon fits with Beacon Cloud.
</Card>
<Card title="Log Forwarding" icon="tower-broadcast" href="/log-forwarding">
Forward local Beacon events into security and observability platforms.
diff --git a/docs/deployment/managed-mcp.mdx b/docs/deployment/managed-mcp.mdx
index 8e5acc93..87f3bb9e 100644
--- a/docs/deployment/managed-mcp.mdx
+++ b/docs/deployment/managed-mcp.mdx
@@ -1,10 +1,10 @@
---
title: "MCP"
-description: "Search your Beacon Managed agent history from the assistants you already use"
+description: "Search your Beacon Cloud agent history from the assistants you already use"
---
-Beacon Managed MCP lets an assistant search and read the agent history you forward to Beacon
-Managed. Use it to find a past session, recover a command or tool result, revisit work across
+Beacon Cloud MCP lets an assistant search and read the agent history you forward to Beacon
+Cloud. Use it to find a past session, recover a command or tool result, revisit work across
different harnesses, and inspect token usage without leaving your current agent.
The server is read-only. It cannot change endpoint configuration, edit a session, or run a tool
@@ -14,7 +14,7 @@ on your machine.
You need:
-- Beacon installed and [connected to Beacon Managed](/cli/endpoint-connect)
+- Beacon installed and [connected to Beacon Cloud](/cli/endpoint-connect)
- At least one supported MCP client on the machine
- A Beacon account with access to the forwarded history
@@ -39,7 +39,7 @@ harness asks you to sign in with OAuth the first time it connects.
<Accordion title="Example">
```text
-Beacon Managed MCP: https://mcp.beacon.sh (checked)
+Beacon Cloud MCP: https://mcp.beacon.sh (checked)
Server name: beacon-managed
Auth: OAuth; Beacon writes only the URL, and each harness signs in on first use
@@ -64,7 +64,7 @@ the [`beacon mcp connect` reference](/cli/mcp-connect).
## What your agent can do
-Beacon Managed MCP exposes tools for:
+Beacon Cloud MCP exposes tools for:
- searching sessions by text and structured filters
- grepping retained prompts, responses, commands, tool calls, and results
@@ -80,7 +80,7 @@ Try prompts such as:
- “Search my Claude Code and Cursor history for changes to the MCP connection flow.”
- “Summarize token usage for this repository over the past seven days.”
-Results are limited to history your account can access in Beacon Managed.
+Results are limited to history your account can access in Beacon Cloud.
## Privacy and retention
@@ -93,9 +93,9 @@ MCP can return only what the endpoint forwarded.
are therefore limited in this mode.
Beacon caps each retained string at 4 KB before writing it locally. Text beyond that limit is not
-available to Beacon Managed MCP.
+available to Beacon Cloud MCP.
-See [Beacon Managed forwarding](/log-forwarding/asymptote#what-leaves-the-machine) and
+See [Beacon Cloud forwarding](/log-forwarding/asymptote#what-leaves-the-machine) and
[retention and redaction](/security/retention-redaction) for the complete data flow.
## Authentication options
@@ -125,13 +125,13 @@ beacon mcp disconnect
removes only entries previously written by Beacon; it leaves MCP entries you created yourself
untouched.
-## Beacon Managed and local MCP
+## Beacon Cloud and local MCP
Beacon offers two separate MCP servers:
| Server | Data | Connection |
|---|---|---|
-| `beacon-managed` | History forwarded to Beacon Managed across connected endpoints | Hosted HTTPS server configured with `beacon mcp connect` |
+| `beacon-managed` | History forwarded to Beacon Cloud across connected endpoints | Hosted HTTPS server configured with `beacon mcp connect` |
| `beacon` | This machine's local runtime log and approved local memory | Local stdio or loopback server configured with `beacon mcp doctor` |
Use both if you want cross-device managed history and direct access to this machine's local data.
@@ -139,13 +139,13 @@ Use both if you want cross-device managed history and direct access to this mach
## Related
<Columns cols={2}>
- <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="cloud" href="/deployment/managed">
Learn about hosted storage, search, analytics, and long-term agent history.
</Card>
<Card title="beacon mcp connect" icon="plug" href="/cli/mcp-connect">
Review every command, flag, supported harness, and configuration format.
</Card>
- <Card title="Beacon Managed forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
+ <Card title="Beacon Cloud forwarding" icon="tower-broadcast" href="/log-forwarding/asymptote">
Understand what leaves an endpoint and how forwarding works.
</Card>
<Card title="Local Beacon MCP" icon="server" href="/cli/mcp">
diff --git a/docs/deployment/managed.mdx b/docs/deployment/managed.mdx
index a6a868ae..09a41dd3 100644
--- a/docs/deployment/managed.mdx
+++ b/docs/deployment/managed.mdx
@@ -1,17 +1,17 @@
---
-title: "Beacon Managed"
+title: "Beacon Cloud"
description: "Hosted storage, search, and long-term history for your agent sessions"
---
The easiest way to use Beacon without running your own backend.
-Beacon Managed gives individual developers hosted storage, search, and long-term history for their agent sessions.
+Beacon Cloud gives individual developers hosted storage, search, and long-term history for their agent sessions.
Install Beacon, connect your account, and your traces are automatically available in one place across the agents you use.
-## What Beacon Managed gives you
+## What Beacon Cloud gives you
-| Capability | Beacon Managed |
+| Capability | Beacon Cloud |
| --- | --- |
| Hosted ingest | Send Beacon traces to a managed backend |
| Unlimited retention | Keep your agent history over time |
@@ -25,22 +25,22 @@ Install Beacon, connect your account, and your traces are automatically availabl
Your agent history is usually split across different tools and local session files.
-Beacon Managed brings those traces together into one searchable timeline, so you can quickly find past work, revisit how you solved something, and compare sessions across harnesses.
+Beacon Cloud brings those traces together into one searchable timeline, so you can quickly find past work, revisit how you solved something, and compare sessions across harnesses.
## Keep what your agents learn
The more you use agents, the more useful history you create.
-Beacon Managed keeps that history over time so successful workflows, debugging patterns, repeated corrections, and repository knowledge do not disappear when a session ends.
+Beacon Cloud keeps that history over time so successful workflows, debugging patterns, repeated corrections, and repository knowledge do not disappear when a session ends.
## Bring that history back into your agents
-Connect [Beacon Managed MCP](/deployment/managed-mcp) to search and read your forwarded session
+Connect [Beacon Cloud MCP](/deployment/managed-mcp) to search and read your forwarded session
history from Claude Code, Cursor, Codex CLI, and other MCP clients. The server is read-only and
uses OAuth by default, so Beacon writes only its URL into supported harness configurations.
## Start in minutes
-Install Beacon, connect to Beacon Managed, and keep using your existing agents.
+Install Beacon, connect to Beacon Cloud, and keep using your existing agents.
No database, storage bucket, or indexing infrastructure required.
diff --git a/docs/detections/index.mdx b/docs/detections/index.mdx
index cff0a7f7..efc4ea1e 100644
--- a/docs/detections/index.mdx
+++ b/docs/detections/index.mdx
@@ -196,11 +196,11 @@ Use the [Detection YAML Schema](/detections/yaml-schema) page for the rule docum
- `beacon rules pull` is the only rules workflow that reaches the network, and only for the explicit URL you provide.
- The local dashboard mirrors `beacon scan` rule resolution and finding behavior, but stays loopback-only and read-only.
-## Managed detections
+## Beacon Cloud detections
-The open-source Beacon flow runs detections locally over endpoint JSONL. [Beacon Managed](/deployment/managed) builds on the same telemetry foundation with centralized ingest, retention, search, detections, fleet-wide visibility, policy workflows, identity mapping, SSO/RBAC, and investigation workflows.
+The open-source Beacon flow runs detections locally over endpoint JSONL. [Beacon Cloud](/deployment/managed) builds on the same telemetry foundation with centralized ingest, retention, search, detections, fleet-wide visibility, policy workflows, identity mapping, SSO/RBAC, and investigation workflows.
-Use local Beacon detections when you need offline endpoint checks or customer-controlled forwarding. Use Managed when you need centralized review across a fleet or organization.
+Use local Beacon detections when you need offline endpoint checks or customer-controlled forwarding. Use Beacon Cloud when you need centralized review across a fleet or organization.
## Read next
diff --git a/docs/docs.json b/docs/docs.json
index 6ae65841..ff22ae74 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -10,7 +10,7 @@
"fonts": {
"family": "Familjen Grotesk"
},
- "favicon": "/images/beacon-favicon.svg",
+ "favicon": "/logo/favicon.svg",
"navigation": {
"style": "sidebar",
"global": {
@@ -57,10 +57,7 @@
"pages": [
"deployment/hosting-options",
"deployment/open-source",
- {
- "group": "Beacon Managed",
- "root": "deployment/managed"
- }
+ "deployment/managed"
]
},
{
@@ -442,7 +439,7 @@
"pages": [
"log-forwarding/ci-telemetry-exports",
{
- "group": "Beacon Managed",
+ "group": "Beacon Cloud",
"expanded": true,
"pages": [
"log-forwarding/asymptote"
diff --git a/docs/get-started/overview.mdx b/docs/get-started/overview.mdx
index 84c1e599..b9c9e8cb 100644
--- a/docs/get-started/overview.mdx
+++ b/docs/get-started/overview.mdx
@@ -5,7 +5,7 @@ description: "Beacon is the open-source trace and reviewed-memory layer for AI a
Beacon captures activity across agent harnesses and turns it into a shared history you can search, debug, analyze, and learn from.
-Run Beacon locally with full control of your data, or use Beacon Managed for hosted storage, search, analytics, and unlimited retention.
+Run Beacon locally with full control of your data, or use Beacon Cloud for hosted storage, search, analytics, and unlimited retention.
## Why Beacon
@@ -31,7 +31,7 @@ Beacon captures that history so it can be reused across future runs and across d
Every run can add to the local trace history. Reusable project memory is created
only when you explicitly evaluate traces and approve candidates.
-| Capability | Local | Beacon Managed |
+| Capability | Local | Beacon Cloud |
| --- | --- | --- |
| Cross-harness agent telemetry | ✓ | ✓ |
| Local, CI & cloud collection | ✓ | ✓ |
@@ -87,7 +87,7 @@ Additional references: [Core Concepts](/concepts/core-concepts), [Command refere
<Card title="Beacon" icon="download" href="/deployment/open-source">
Install the open-source CLI and configure Agent Beacon telemetry.
</Card>
- <Card title="Beacon Managed" icon="key" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="key" href="/deployment/managed">
Review managed visibility, investigations, and rollout support.
</Card>
<Card title="Hosting Options" icon="cloud" href="/deployment/hosting-options">
diff --git a/docs/get-started/quickstart.mdx b/docs/get-started/quickstart.mdx
index 9fc4ce5e..314a2dd0 100644
--- a/docs/get-started/quickstart.mdx
+++ b/docs/get-started/quickstart.mdx
@@ -48,7 +48,7 @@ Keep your agent history on your machine.
Beacon writes telemetry locally and gives you a local dashboard. Nothing is forwarded unless you explicitly configure it.
-### Beacon Managed
+### Beacon Cloud
Send your Beacon telemetry to the hosted service for:
@@ -58,7 +58,7 @@ Send your Beacon telemetry to the hosted service for:
- analytics
- access from anywhere
-Interactive installation signs in, preselects Managed, and asks you to review the
+Interactive installation signs in, preselects Beacon Cloud, and asks you to review the
privacy choice. Confirming installs Beacon and connects this endpoint in the same
command, using the signed-in CLI account to authorize a separate device ingest key
with no second browser approval.
@@ -89,7 +89,7 @@ For the local dashboard:
beacon endpoint dashboard --open
```
-If you're using Beacon Managed, your sessions will also appear in the hosted dashboard.
+If you're using Beacon Cloud, your sessions will also appear in the hosted dashboard.
## Check your setup
@@ -97,7 +97,7 @@ If you're using Beacon Managed, your sessions will also appear in the hosted das
beacon endpoint status
```
-This shows which harnesses are connected, whether the collector is running, and whether Beacon Managed is enabled.
+This shows which harnesses are connected, whether the collector is running, and whether Beacon Cloud is enabled.
## Useful commands
@@ -105,7 +105,7 @@ This shows which harnesses are connected, whether the collector is running, and
| --- | --- |
| Check status | `beacon endpoint status` |
| Open local dashboard | `beacon endpoint dashboard --open` |
-| Connect to Beacon Managed | `beacon endpoint connect` |
-| Disconnect from Managed | `beacon endpoint disconnect` |
+| Connect to Beacon Cloud | `beacon endpoint connect` |
+| Disconnect from Beacon Cloud | `beacon endpoint disconnect` |
| Upgrade | `brew upgrade beacon` |
| Uninstall | `beacon endpoint uninstall --keep-logs` |
diff --git a/docs/guides/fleet-s3-mdm.mdx b/docs/guides/fleet-s3-mdm.mdx
index dfc7663a..5910095e 100644
--- a/docs/guides/fleet-s3-mdm.mdx
+++ b/docs/guides/fleet-s3-mdm.mdx
@@ -322,7 +322,7 @@ Harness: Codex CLI <version> telemetry=enabled
Last event: present
```
-`running=true` and `telemetry=enabled` are the lines that matter. A line reading `Beacon Managed: not connected` is expected: Beacon's hosted service isn't used in this setup.
+`running=true` and `telemetry=enabled` are the lines that matter. A line reading `Beacon Cloud: not connected` is expected: Beacon's hosted service isn't used in this setup.
<Note>
The package configures the agents of whoever is logged in at the Mac when it installs. If nobody was logged in, for example during Setup Assistant, run this after someone logs in, either as a Fleet script or on the Mac:
diff --git a/docs/index.mdx b/docs/index.mdx
index ab950219..42fe0648 100644
--- a/docs/index.mdx
+++ b/docs/index.mdx
@@ -59,7 +59,7 @@ Start collecting agent traces in minutes, then use Beacon to explore sessions, u
<Card title="Beacon Overview" icon="rocket" href="/get-started/overview">
Understand the problem Beacon solves and when to use open-source, managed, or private deployments.
</Card>
- <Card title="Managed Beacon" icon="key" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="key" href="/deployment/managed">
Review managed platform options for hosted agent runtime visibility, governance, and enterprise rollout support.
</Card>
</CardGroup>
diff --git a/docs/log-forwarding/asymptote.mdx b/docs/log-forwarding/asymptote.mdx
index 870bf7ac..79a29c3c 100644
--- a/docs/log-forwarding/asymptote.mdx
+++ b/docs/log-forwarding/asymptote.mdx
@@ -1,11 +1,11 @@
---
-title: "Beacon Managed"
+title: "Beacon Cloud"
description: "Forward Beacon endpoint events to Beacon's managed ingest service and see them on the Beacon dashboard."
---
## Forwarding overview
-Beacon Managed is the forwarding path that lands Beacon endpoint events on the Beacon dashboard without any customer-run infrastructure. Beacon stays the local JSONL producer. A Vector forwarder on the endpoint tails the [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log) and the inventory log and POSTs gzip-compressed NDJSON batches over HTTPS to Beacon's ingest service, authenticated with a key issued to that one device.
+Beacon Cloud is the forwarding path that lands Beacon endpoint events on the Beacon dashboard without any customer-run infrastructure. Beacon stays the local JSONL producer. A Vector forwarder on the endpoint tails the [runtime JSONL log](/concepts/core-concepts#runtime-jsonl-log) and the inventory log and POSTs gzip-compressed NDJSON batches over HTTPS to Beacon's ingest service, authenticated with a key issued to that one device.
This is the only Beacon destination that sends telemetry to a Beacon-run endpoint. It is preselected during interactive onboarding, and confirming it mints a device key and starts the forwarder in the same command, once the local install has succeeded. Signing in alone forwards nothing. Choosing Local explicitly opts out. Revoking the device from the dashboard's Beacon Endpoints page stops ingestion within about a minute.
diff --git a/docs/log-forwarding/index.mdx b/docs/log-forwarding/index.mdx
index 8c8619f4..f5e3487a 100644
--- a/docs/log-forwarding/index.mdx
+++ b/docs/log-forwarding/index.mdx
@@ -7,7 +7,7 @@ description: "Forward Beacon endpoint events from local JSONL into SIEMs, log ag
Beacon writes normalized [endpoint events](/concepts/core-concepts#endpoint-event) as JSONL. The active [runtime log](/concepts/core-concepts#runtime-jsonl-log) is the handoff point for local review, [customer-managed log pipelines](/concepts/core-concepts#customer-managed-forwarding), log aggregators, object storage exporters, and most SIEM content packs. Beacon can also enable optional collector exporters for [Splunk HTTP Event Collector (HEC)](/concepts/core-concepts#splunk-hec) and [CrowdStrike Falcon LogScale HEC](/concepts/core-concepts#falcon-logscale-hec) during endpoint install or repair.
-Use the subpages below by destination category. Beacon Managed is the one path that sends events to a Beacon-run service; it is opt-in per device and revocable from the Beacon dashboard. SIEM pages are for destinations that become investigation or detection systems. Log aggregation pages are for customer-owned pipelines and observability stores that tail local JSONL. Object storage pages are for archival or data lake export. Local pages cover the default runtime log and dashboard source.
+Use the subpages below by destination category. Beacon Cloud is the one path that sends events to a Beacon-run service; it is opt-in per device and revocable from the Beacon dashboard. SIEM pages are for destinations that become investigation or detection systems. Log aggregation pages are for customer-owned pipelines and observability stores that tail local JSONL. Object storage pages are for archival or data lake export. Local pages cover the default runtime log and dashboard source.
For [ephemeral CI jobs](/concepts/core-concepts#ci-telemetry), see [CI Telemetry Exports](/log-forwarding/ci-telemetry-exports) for workflow artifacts, S3/GCS upload, and downstream handoff patterns over the completed CI `runtime.jsonl` file.
@@ -29,7 +29,7 @@ Use system mode for MDM deployments so endpoint events land in the shared system
## Destination categories
-### Beacon Managed
+### Beacon Cloud
Use this path when Beacon events should appear on the Beacon dashboard. In user
mode, the signed-in CLI account authorizes a device key without another browser
@@ -37,7 +37,7 @@ approval. System mode uses browser approval. Revoking the device stops ingestion
within a minute.
<Columns cols={2}>
- <Card title="Beacon Managed" icon="tower-broadcast" href="/log-forwarding/asymptote">
+ <Card title="Beacon Cloud" icon="tower-broadcast" href="/log-forwarding/asymptote">
Vector `http` forwarder over local JSONL with a per-device key; what leaves the machine, the wire contract, and revocation.
</Card>
<Card title="beacon endpoint asymptote" icon="terminal" href="/cli/asymptote">
@@ -266,7 +266,7 @@ See [macOS System-Mode Object Storage Forwarding](/guides/macos-object-storage-s
for bucket creation, IAM, Vector `0.56` authentication limits, safe credential
delivery and rotation, and validation.
-### Beacon Managed
+### Beacon Cloud
For the Beacon dashboard, generate the Beacon pack and run Vector with the device key and ingest URL issued by enrollment. `beacon endpoint connect` does this for you as a managed service.
@@ -276,7 +276,7 @@ beacon endpoint asymptote install-pack --system --output ./beacon-asymptote-pack
The generated pack includes setup guidance, a Vector `http` sink template that reads the device key from a `0600` secrets file through Vector's secret backend, a one-shot credential and upload smoke-test script, and sample events. Only the runtime and inventory JSONL lines leave the machine; the ingest service stamps organization and device identity server-side.
-See [Beacon Managed](/log-forwarding/asymptote) for the wire contract, revocation, and offline behavior.
+See [Beacon Cloud](/log-forwarding/asymptote) for the wire contract, revocation, and offline behavior.
### Vector log forwarding
diff --git a/docs/logo/apple-touch-icon.png b/docs/logo/apple-touch-icon.png
new file mode 100644
index 00000000..eab2766a
Binary files /dev/null and b/docs/logo/apple-touch-icon.png differ
diff --git a/docs/logo/beacon-lockup-dark.svg b/docs/logo/beacon-lockup-dark.svg
index 81b608ce..12507093 100644
--- a/docs/logo/beacon-lockup-dark.svg
+++ b/docs/logo/beacon-lockup-dark.svg
@@ -1,8 +1,6 @@
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1200 420" role="img" aria-label="Beacon logo">
- <g transform="translate(22 43) scale(.55)">
- <path fill="#FF6A00" d="M256 52C210 91 122 157 82 212c-26 36-39 74-34 111 8 62 49 103 111 125 31 11 57 30 79 56V288h-29v-85a48 48 0 1 1 94 0v85h-29v216c22-26 48-45 79-56 62-22 103-63 111-125 5-37-8-75-34-111-40-55-128-121-174-160Z"/>
- <circle cx="256" cy="191" r="39" fill="#FFFFFF"/>
- <rect x="238" y="225" width="36" height="239" fill="#FFFFFF"/>
+ <g transform="translate(28 30) scale(1.99) translate(-60 -30)">
+ <path fill="#FF5400" d="M182.194 156.596C152.215 156.596 127.94 180.244 127.939 210.23V210.525H114.234V210.23H114.257C114.257 180.244 89.9597 156.596 60.0029 156.596V126.709C89.9595 126.709 114.256 150.357 114.257 180.343H114.234V180.639H127.939V180.343C127.94 150.357 152.215 126.709 182.194 126.709V156.596ZM127.96 30.2949H127.938C127.938 60.281 152.235 83.9295 182.191 83.9297V113.816C152.235 113.816 127.938 90.1685 127.938 60.1826H127.96V59.8867H114.255V60.1826C114.255 90.1687 89.9796 113.816 60 113.816V83.9297C89.9797 83.9297 114.255 60.2812 114.255 30.2949V30H127.96V30.2949Z"/>
</g>
- <text x="320" y="292" font-family="Inter, Arial, sans-serif" font-size="260" font-weight="700" letter-spacing="-11" fill="#FFFFFF">Beacon</text>
+ <text x="310" y="294" font-family="Familjen Grotesk, Inter, Arial, sans-serif" font-size="250" font-weight="600" letter-spacing="-8" fill="#FFFFFF">Beacon</text>
</svg>
diff --git a/docs/logo/beacon-lockup-light.svg b/docs/logo/beacon-lockup-light.svg
index 99dd7c0f..f5900b30 100644
--- a/docs/logo/beacon-lockup-light.svg
+++ b/docs/logo/beacon-lockup-light.svg
@@ -1,8 +1,6 @@
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1200 420" role="img" aria-label="Beacon logo">
- <g transform="translate(22 43) scale(.55)">
- <path fill="#FF6A00" d="M256 52C210 91 122 157 82 212c-26 36-39 74-34 111 8 62 49 103 111 125 31 11 57 30 79 56V288h-29v-85a48 48 0 1 1 94 0v85h-29v216c22-26 48-45 79-56 62-22 103-63 111-125 5-37-8-75-34-111-40-55-128-121-174-160Z"/>
- <circle cx="256" cy="191" r="39" fill="#FFFFFF"/>
- <rect x="238" y="225" width="36" height="239" fill="#FFFFFF"/>
+ <g transform="translate(28 30) scale(1.99) translate(-60 -30)">
+ <path fill="#FF5400" d="M182.194 156.596C152.215 156.596 127.94 180.244 127.939 210.23V210.525H114.234V210.23H114.257C114.257 180.244 89.9597 156.596 60.0029 156.596V126.709C89.9595 126.709 114.256 150.357 114.257 180.343H114.234V180.639H127.939V180.343C127.94 150.357 152.215 126.709 182.194 126.709V156.596ZM127.96 30.2949H127.938C127.938 60.281 152.235 83.9295 182.191 83.9297V113.816C152.235 113.816 127.938 90.1685 127.938 60.1826H127.96V59.8867H114.255V60.1826C114.255 90.1687 89.9796 113.816 60 113.816V83.9297C89.9797 83.9297 114.255 60.2812 114.255 30.2949V30H127.96V30.2949Z"/>
</g>
- <text x="320" y="292" font-family="Inter, Arial, sans-serif" font-size="260" font-weight="700" letter-spacing="-11" fill="#2B1007">Beacon</text>
+ <text x="310" y="294" font-family="Familjen Grotesk, Inter, Arial, sans-serif" font-size="250" font-weight="600" letter-spacing="-8" fill="#1B1B1B">Beacon</text>
</svg>
diff --git a/docs/logo/favicon-16.png b/docs/logo/favicon-16.png
new file mode 100644
index 00000000..53e3a69c
Binary files /dev/null and b/docs/logo/favicon-16.png differ
diff --git a/docs/logo/favicon-32.png b/docs/logo/favicon-32.png
new file mode 100644
index 00000000..bda4b076
Binary files /dev/null and b/docs/logo/favicon-32.png differ
diff --git a/docs/logo/favicon.svg b/docs/logo/favicon.svg
new file mode 100644
index 00000000..1ff7fbc5
--- /dev/null
+++ b/docs/logo/favicon.svg
@@ -0,0 +1,3 @@
+<svg width="200" height="200" viewBox="21 20 200 200" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M182.194 156.596C152.215 156.596 127.94 180.244 127.939 210.23V210.525H114.234V210.23H114.257C114.257 180.244 89.9597 156.596 60.0029 156.596V126.709C89.9595 126.709 114.256 150.357 114.257 180.343H114.234V180.639H127.939V180.343C127.94 150.357 152.215 126.709 182.194 126.709V156.596ZM127.96 30.2949H127.938C127.938 60.281 152.235 83.9295 182.191 83.9297V113.816C152.235 113.816 127.938 90.1685 127.938 60.1826H127.96V59.8867H114.255V60.1826C114.255 90.1687 89.9796 113.816 60 113.816V83.9297C89.9797 83.9297 114.255 60.2812 114.255 30.2949V30H127.96V30.2949Z" fill="#FF5400"></path>
+</svg>
diff --git a/docs/logo/logo_with_text.png b/docs/logo/logo_with_text.png
index 5c62ae6e..0879d509 100644
Binary files a/docs/logo/logo_with_text.png and b/docs/logo/logo_with_text.png differ
diff --git a/docs/logo/logo_with_text_dark.png b/docs/logo/logo_with_text_dark.png
index 54e31806..f67364f4 100644
Binary files a/docs/logo/logo_with_text_dark.png and b/docs/logo/logo_with_text_dark.png differ
diff --git a/docs/logo/logomark-blue.svg b/docs/logo/logomark-blue.svg
new file mode 100644
index 00000000..1b669d3c
--- /dev/null
+++ b/docs/logo/logomark-blue.svg
@@ -0,0 +1,3 @@
+<svg width="123" height="181" viewBox="60 30 123 181" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M182.194 156.596C152.215 156.596 127.94 180.244 127.939 210.23V210.525H114.234V210.23H114.257C114.257 180.244 89.9597 156.596 60.0029 156.596V126.709C89.9595 126.709 114.256 150.357 114.257 180.343H114.234V180.639H127.939V180.343C127.94 150.357 152.215 126.709 182.194 126.709V156.596ZM127.96 30.2949H127.938C127.938 60.281 152.235 83.9295 182.191 83.9297V113.816C152.235 113.816 127.938 90.1685 127.938 60.1826H127.96V59.8867H114.255V60.1826C114.255 90.1687 89.9796 113.816 60 113.816V83.9297C89.9797 83.9297 114.255 60.2812 114.255 30.2949V30H127.96V30.2949Z" fill="#006CFF"></path>
+</svg>
\ No newline at end of file
diff --git a/docs/logo/logomark-orange.svg b/docs/logo/logomark-orange.svg
new file mode 100644
index 00000000..529fdeb8
--- /dev/null
+++ b/docs/logo/logomark-orange.svg
@@ -0,0 +1,3 @@
+<svg width="123" height="181" viewBox="60 30 123 181" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M182.194 156.596C152.215 156.596 127.94 180.244 127.939 210.23V210.525H114.234V210.23H114.257C114.257 180.244 89.9597 156.596 60.0029 156.596V126.709C89.9595 126.709 114.256 150.357 114.257 180.343H114.234V180.639H127.939V180.343C127.94 150.357 152.215 126.709 182.194 126.709V156.596ZM127.96 30.2949H127.938C127.938 60.281 152.235 83.9295 182.191 83.9297V113.816C152.235 113.816 127.938 90.1685 127.938 60.1826H127.96V59.8867H114.255V60.1826C114.255 90.1687 89.9796 113.816 60 113.816V83.9297C89.9797 83.9297 114.255 60.2812 114.255 30.2949V30H127.96V30.2949Z" fill="#FF5400"></path>
+</svg>
\ No newline at end of file
diff --git a/docs/manage/configure-s3-data-connector.mdx b/docs/manage/configure-s3-data-connector.mdx
index f451cb5b..46d705a5 100644
--- a/docs/manage/configure-s3-data-connector.mdx
+++ b/docs/manage/configure-s3-data-connector.mdx
@@ -115,7 +115,7 @@ Share a representative sample file before production ingestion. The sample shoul
## Related
<Columns cols={2}>
- <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="cloud" href="/deployment/managed">
Review managed visibility, governance, and investigation workflows.
</Card>
<Card title="Endpoint Event Schema" icon="code" href="/telemetry-schema/event-schema">
diff --git a/docs/manage/onboarding.mdx b/docs/manage/onboarding.mdx
index 91327b28..187769b1 100644
--- a/docs/manage/onboarding.mdx
+++ b/docs/manage/onboarding.mdx
@@ -1,6 +1,6 @@
---
title: "Onboarding"
-description: "Onboarding guides for Beacon managed connectors."
+description: "Onboarding guides for Beacon Cloud connectors."
tag: "Enterprise"
---
diff --git a/docs/mdm/index.mdx b/docs/mdm/index.mdx
index b45156e6..e6f9e889 100644
--- a/docs/mdm/index.mdx
+++ b/docs/mdm/index.mdx
@@ -59,7 +59,7 @@ off by default.
</Step>
</Steps>
-Connecting packaged endpoints to Beacon Managed is a separate, interactive step today: an admin runs `sudo /opt/beacon/bin/beacon endpoint connect --system --dashboard-url https://beacon.sh` on the machine and the approval page opens in the console user's browser. The package never enrolls a device on its own, and there is no headless enrollment for MDM fleets yet; it is a planned follow-up. See [`beacon endpoint connect`](/cli/endpoint-connect).
+Connecting packaged endpoints to Beacon Cloud is a separate, interactive step today: an admin runs `sudo /opt/beacon/bin/beacon endpoint connect --system --dashboard-url https://beacon.sh` on the machine and the approval page opens in the console user's browser. The package never enrolls a device on its own, and there is no headless enrollment for MDM fleets yet; it is a planned follow-up. See [`beacon endpoint connect`](/cli/endpoint-connect).
Environment variables take precedence over MDM script parameters:
diff --git a/docs/platforms/linux-deployment-profile.mdx b/docs/platforms/linux-deployment-profile.mdx
index 23e029ca..906114a6 100644
--- a/docs/platforms/linux-deployment-profile.mdx
+++ b/docs/platforms/linux-deployment-profile.mdx
@@ -96,8 +96,8 @@ The only outbound connections Beacon ever makes, for an egress allowlist:
| Host | When | Suppress with |
|---|---|---|
| `auth.asymptotelabs.ai` | Once per machine, interactive install only | `BEACON_ONBOARDING=0` (already skipped for `--system` and package installs) |
-| `beacon.sh` | Interactive install only: browser sign-in, and the device enrollment that follows when Beacon Managed is confirmed | `BEACON_MANAGED_INGEST=0` hides the managed answer; `BEACON_ONBOARDING=0` skips the wizard entirely |
-| Your ingest host | Continuously, only on an endpoint connected to Beacon Managed | `beacon endpoint disconnect`, or never connecting |
+| `beacon.sh` | Interactive install only: browser sign-in, and the device enrollment that follows when Beacon Cloud is confirmed | `BEACON_MANAGED_INGEST=0` hides the managed answer; `BEACON_ONBOARDING=0` skips the wizard entirely |
+| Your ingest host | Continuously, only on an endpoint connected to Beacon Cloud | `beacon endpoint disconnect`, or never connecting |
| `api.github.com`, `github.com` | Version check and self-update | Off by default; leave it off and deploy through your config management |
A forwarding destination you set up yourself, such as Splunk HEC, or Microsoft Sentinel through Vector, connects to that destination's hosts. Nothing does until you configure one.
diff --git a/docs/platforms/linux.mdx b/docs/platforms/linux.mdx
index a9c694aa..17fc98c5 100644
--- a/docs/platforms/linux.mdx
+++ b/docs/platforms/linux.mdx
@@ -100,11 +100,11 @@ Collector: grpc=true http=true
Service: loaded=true running=true
Harness: Claude Code telemetry=enabled
Last event: present
-Beacon Managed: not connected (run `beacon endpoint connect`)
+Beacon Cloud: not connected (run `beacon endpoint connect`)
Inventory heartbeat: scheduled every 6h0m0s; job loaded=true running=true; last emitted never
```
-`running=true` and `telemetry=enabled` are the lines that matter. Then run your agent as usual (see [Using it](#using-it)) and its events land in the runtime log. `Beacon Managed: not connected` is expected, because a package install keeps everything on this machine.
+`running=true` and `telemetry=enabled` are the lines that matter. Then run your agent as usual (see [Using it](#using-it)) and its events land in the runtime log. `Beacon Cloud: not connected` is expected, because a package install keeps everything on this machine.
### If something looks wrong
@@ -162,7 +162,7 @@ A new install is local-only. Nothing leaves the machine until you set up a desti
| [Elastic](/log-forwarding/elastic), [Datadog](/log-forwarding/datadog), [Wazuh](/log-forwarding/wazuh) | That product's own agent, tailing the log |
| [Microsoft Sentinel](/log-forwarding/microsoft-sentinel) | Vector, through the Logs Ingestion API. Or Azure Monitor Agent, which outside Azure needs Azure Arc first |
| [S3](/log-forwarding#aws-s3), [GCS](/log-forwarding#google-cloud-storage), [CloudWatch](/log-forwarding/cloudwatch), [Sumo Logic](/log-forwarding/sumo), [Rapid7](/log-forwarding/rapid7), [CrowdStrike Falcon](/log-forwarding/falcon) | Vector |
-| [Beacon Managed](/log-forwarding/asymptote) | Vector, set up by `beacon endpoint connect` |
+| [Beacon Cloud](/log-forwarding/asymptote) | Vector, set up by `beacon endpoint connect` |
Vector comes with Beacon. The `.deb` and `.rpm` install it at `/opt/beacon/bin/vector`, and the tarball carries it as `beacon-vector`. Neither is on PATH by default, and neither runs until a destination needs it. `beacon endpoint connect` finds it on its own. For the other Vector destinations, run the generated `vector.toml` with `/opt/beacon/bin/vector`, or with your own Vector 0.50 or newer.
diff --git a/docs/runtimes/claude-code-cloud-agents.mdx b/docs/runtimes/claude-code-cloud-agents.mdx
index 8fb4d76c..20e7de5e 100644
--- a/docs/runtimes/claude-code-cloud-agents.mdx
+++ b/docs/runtimes/claude-code-cloud-agents.mdx
@@ -1,12 +1,12 @@
---
title: "Claude Code Cloud Agents"
-description: "Capture Claude Code cloud agent telemetry and send each session log to Beacon Managed or to object storage you own"
+description: "Capture Claude Code cloud agent telemetry and send each session log to Beacon Cloud or to object storage you own"
---
## Overview
Use this integration to capture Claude Code cloud-agent activity and send each
-session log to one of three places: [Beacon Managed](/deployment/managed),
+session log to one of three places: [Beacon Cloud](/deployment/managed),
where it appears in your dashboard next to your laptops' sessions, or a Google
Cloud Storage or Amazon S3 bucket you own.
@@ -21,7 +21,7 @@ Claude Code Cloud Agents run in Anthropic's cloud environment, so Beacon cannot
use the long-running endpoint agent that local installs use. Instead, the setup
script installs Beacon hooks inside the sandbox. During a cloud-agent session,
those hooks write `/tmp/beacon/runtime.jsonl`. When the agent stops, Beacon
-ships that file: to Beacon Managed it posts the new lines to the same ingest
+ships that file: to Beacon Cloud it posts the new lines to the same ingest
endpoint the laptop forwarder uses, so the session shows up in the dashboard a
minute or two later; to a bucket it uploads the whole file as one object.
@@ -29,7 +29,7 @@ minute or two later; to a bucket it uploads the whole file as one object.
flowchart LR
ClaudeWeb["Claude Code Cloud Agents"] --> Hooks["Beacon hooks in sandbox"]
Hooks --> RuntimeLog["/tmp/beacon/runtime.jsonl"]
- RuntimeLog --> Managed["Beacon Managed ingest → dashboard"]
+ RuntimeLog --> Managed["Beacon Cloud ingest → dashboard"]
RuntimeLog --> Storage["Your GCS or S3 bucket"]
```
@@ -39,7 +39,7 @@ The setup has three parts:
2. Add Beacon cloud telemetry environment variables to the Claude Code cloud environment.
3. Paste a Beacon-generated setup script into the Claude cloud environment.
-With Beacon Managed, the sessions land in the same per-organization tables as
+With Beacon Cloud, the sessions land in the same per-organization tables as
your endpoints' telemetry, attributed to the device you created for the cloud
environment. With a bucket, each Claude Code cloud agent session writes one
readable JSONL object:
@@ -63,7 +63,7 @@ s3://<bucket>/<prefix>/runtime/date=YYYY-MM-DD/<timestamp>-claude_code_web-<clau
create buckets, IAM users, inline IAM policies, and access keys.
- Claude Code cloud agent access for the repository you want to test.
- A Claude cloud environment with outbound access to:
- - For Beacon Managed: the ingest host from your device key hand-off
+ - For Beacon Cloud: the ingest host from your device key hand-off
(currently `beacon-ingest-gulcylfs4a-uw.a.run.app`)
- For GCS: `oauth2.googleapis.com` and `storage.googleapis.com`
- For S3: `s3.<region>.amazonaws.com`
@@ -95,9 +95,9 @@ aws sts get-caller-identity
## 1. Create the upload path
-Choose Beacon Managed, GCS, or S3 for the cloud-agent session logs.
+Choose Beacon Cloud, GCS, or S3 for the cloud-agent session logs.
-### Beacon Managed
+### Beacon Cloud
A cloud sandbox has no browser and no Vector, so it cannot run
[`beacon endpoint connect`](/cli/endpoint-connect). Instead it authenticates with
@@ -226,7 +226,7 @@ BEACON_RUN_EPHEMERAL=true
BEACON_CLOUD_USER_ID_HASH=<stable-user-or-test-id>
```
-For Beacon Managed, add:
+For Beacon Cloud, add:
```bash
BEACON_CLOUD_UPLOAD=asymptote
@@ -295,7 +295,7 @@ Read the README, run pwd && ls, create a tiny temporary markdown note under /tmp
## 5. Verify upload
-For Beacon Managed, open the dashboard: under **Devices** the cloud
+For Beacon Cloud, open the dashboard: under **Devices** the cloud
environment shows a fresh **last seen** time as soon as the first batch is
accepted, and the session appears under **Sessions** within a couple of minutes,
with `run.provider=claude_code_web` and the Claude session id as the run id.
@@ -355,7 +355,7 @@ run.run_id=cse_...
## Security note
-The Beacon Managed flow puts a per-device key in the Claude Code environment.
+The Beacon Cloud flow puts a per-device key in the Claude Code environment.
It can only append telemetry to your organization's ingest stream; it reads
nothing and grants no dashboard access, and revoking the device under
**Devices** stops it within a minute. This is the one place a Beacon
@@ -418,7 +418,7 @@ sandbox-specific configuration and should stay out of commits.
<Card title="Log forwarding" icon="database" href="/log-forwarding">
Review local endpoint S3 forwarding for persistent endpoint deployments.
</Card>
- <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="cloud" href="/deployment/managed">
Use managed secure ingest for production enterprise cloud-agent telemetry.
</Card>
<Card title="Agent Beacon on GitHub" icon="github" href="https://github.com/asymptote-labs/agent-beacon">
diff --git a/docs/runtimes/claude-code.mdx b/docs/runtimes/claude-code.mdx
index 80c246a0..b9e056e3 100644
--- a/docs/runtimes/claude-code.mdx
+++ b/docs/runtimes/claude-code.mdx
@@ -50,12 +50,12 @@ Claude cloud sandbox, writes `/tmp/beacon/runtime.jsonl`, and uploads the
session log to customer-managed Google Cloud Storage.
Start with [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents) when you want to
-test Claude Code cloud agent telemetry without deploying Beacon Managed.
+test Claude Code cloud agent telemetry without deploying Beacon Cloud.
<Warning>
The self-serve GCS path passes a scoped service-account credential to the
Claude Code cloud environment. Use it for evaluation and prototypes. For
- production enterprise deployments, use [Beacon Managed](/deployment/managed)
+ production enterprise deployments, use [Beacon Cloud](/deployment/managed)
or contact Beacon about secure forwarding in your own customer-managed
infrastructure.
</Warning>
diff --git a/docs/runtimes/cursor-cloud-agents.mdx b/docs/runtimes/cursor-cloud-agents.mdx
index 6477e65f..5dc7d6ce 100644
--- a/docs/runtimes/cursor-cloud-agents.mdx
+++ b/docs/runtimes/cursor-cloud-agents.mdx
@@ -16,7 +16,7 @@ binaries in the Cursor cloud sandbox.
<Info>
If you're interested in leveraging this telemetry ingest across your
- enterprise, [Beacon Managed](/deployment/managed) is designed for
+ enterprise, [Beacon Cloud](/deployment/managed) is designed for
production cloud-agent telemetry ingest at scale.
</Info>
@@ -445,7 +445,7 @@ git diff -- .cursor/hooks.json
<Card title="Log forwarding" icon="database" href="/log-forwarding">
Compare direct cloud-agent uploads with local endpoint object-storage forwarding.
</Card>
- <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="cloud" href="/deployment/managed">
Use managed secure ingest for production enterprise cloud-agent telemetry.
</Card>
<Card title="Agent Beacon on GitHub" icon="github" href="https://github.com/asymptote-labs/agent-beacon">
diff --git a/docs/runtimes/devin-cloud-agents.mdx b/docs/runtimes/devin-cloud-agents.mdx
index 761c819e..f023d3f9 100644
--- a/docs/runtimes/devin-cloud-agents.mdx
+++ b/docs/runtimes/devin-cloud-agents.mdx
@@ -15,7 +15,7 @@ hook engine. Beacon instead pulls session activity from the Devin
<Info>
If you're interested in leveraging this telemetry ingest across your
- enterprise, [Beacon Managed](/deployment/managed) is designed for
+ enterprise, [Beacon Cloud](/deployment/managed) is designed for
production cloud-agent telemetry ingest at scale.
</Info>
@@ -236,7 +236,7 @@ in-progress session shows `session.started`, `prompt.submitted`, and
<Card title="Google Cloud Storage forwarding" icon="database" href="/siem-forwarding-gcs">
Review local endpoint GCS forwarding for persistent deployments.
</Card>
- <Card title="Beacon Managed" icon="cloud" href="/deployment/managed">
+ <Card title="Beacon Cloud" icon="cloud" href="/deployment/managed">
Use managed secure ingest for production enterprise cloud-agent telemetry.
</Card>
</Columns>
diff --git a/docs/runtimes/index.mdx b/docs/runtimes/index.mdx
index a45ffe07..94043947 100644
--- a/docs/runtimes/index.mdx
+++ b/docs/runtimes/index.mdx
@@ -5,7 +5,7 @@ description: "Beacon agent harness support overview and runtime-specific pages"
## Overview
-Beacon supports multiple [runtime surfaces](/concepts/core-concepts#runtime-surface) because each [agent harness](/concepts/core-concepts#agent-harness) exposes telemetry differently. Beacon collects and normalizes supported local, CI, and cloud-agent telemetry, while Beacon Managed adds hosted ingest, visibility, and governance on top of the same surfaces.
+Beacon supports multiple [runtime surfaces](/concepts/core-concepts#runtime-surface) because each [agent harness](/concepts/core-concepts#agent-harness) exposes telemetry differently. Beacon collects and normalizes supported local, CI, and cloud-agent telemetry, while Beacon Cloud adds hosted ingest, visibility, and governance on top of the same surfaces.
These integrations are grouped by where the agent runs and how telemetry is collected:
diff --git a/docs/sdk/index.mdx b/docs/sdk/index.mdx
index 6281393e..9c922e10 100644
--- a/docs/sdk/index.mdx
+++ b/docs/sdk/index.mdx
@@ -7,13 +7,13 @@ description: "Instrument cloud-hosted agent applications with Beacon-compatible
Beacon Observe instruments cloud-hosted agent applications and exports OpenTelemetry traces that remain compatible with Beacon's normalized endpoint event model. Use it for servers, serverless functions, workers, and hosted agent platforms where installing the local Beacon endpoint agent is not the right fit.
-Hosted Observe ingest is available through Beacon Managed. To get an `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact).
+Hosted Observe ingest is available through Beacon Cloud. To get an `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact).
The open-source `agent-beacon` repository currently includes the TypeScript package `@asymptote/sdk`. It provides the `Observe` module for OpenTelemetry setup, common AI SDK instrumentation, manual span wrappers, lifecycle helpers, and Beacon compatibility attributes.
## What Beacon captures
-Beacon Observe is OpenTelemetry-first. It records supported model calls, agent turns, tool calls, custom orchestration steps, errors, and Beacon compatibility attributes as spans that can be sent to Beacon Managed hosted Observe or a customer-managed OTLP collector.
+Beacon Observe is OpenTelemetry-first. It records supported model calls, agent turns, tool calls, custom orchestration steps, errors, and Beacon compatibility attributes as spans that can be sent to Beacon Cloud hosted Observe or a customer-managed OTLP collector.
Supported cloud SDK paths:
@@ -68,4 +68,4 @@ The SDK and Beacon endpoint telemetry share an event contract, but they target d
| Beacon CI | Ephemeral CI telemetry captured for a single job |
| Beacon JSONL schema | Normalized event model used by local logs, dashboards, and downstream security pipelines |
-Cloud SDK spans set `beacon.origin=cloud` and can include Beacon compatibility attributes such as `beacon.harness.name`, `beacon.event.action`, `beacon.tool.name`, and `beacon.prompt.text`. The same attributes can be consumed by Beacon-compatible collectors or Beacon Managed Observe ingest.
+Cloud SDK spans set `beacon.origin=cloud` and can include Beacon compatibility attributes such as `beacon.harness.name`, `beacon.event.action`, `beacon.tool.name`, and `beacon.prompt.text`. The same attributes can be consumed by Beacon-compatible collectors or Beacon Cloud Observe ingest.
diff --git a/docs/sdk/instrumentation.mdx b/docs/sdk/instrumentation.mdx
index 5607d5c4..7fef18bd 100644
--- a/docs/sdk/instrumentation.mdx
+++ b/docs/sdk/instrumentation.mdx
@@ -23,8 +23,8 @@ By default, the SDK creates OpenAI and Anthropic OpenLLMetry instrumentations wh
| Option | Purpose |
| --- | --- |
-| `apiKey` | Beacon Managed hosted Observe API key. Defaults to `ASYMPTOTE_API_KEY` |
-| `baseUrl` | Beacon Managed hosted Observe base URL. Defaults to `ASYMPTOTE_BASE_URL` or `https://api.asymptotelabs.ai` |
+| `apiKey` | Beacon Cloud hosted Observe API key. Defaults to `ASYMPTOTE_API_KEY` |
+| `baseUrl` | Beacon Cloud hosted Observe base URL. Defaults to `ASYMPTOTE_BASE_URL` or `https://api.asymptotelabs.ai` |
| `otlpEndpoint` | Explicit OTLP/HTTP endpoint. Defaults to `OTEL_EXPORTER_OTLP_ENDPOINT` |
| `headers` | Additional exporter headers |
| `serviceName` | OpenTelemetry service name. Defaults to `OTEL_SERVICE_NAME` or `asymptote-app` |
diff --git a/docs/sdk/integrations-anthropic.mdx b/docs/sdk/integrations-anthropic.mdx
index 2929871a..67d017e1 100644
--- a/docs/sdk/integrations-anthropic.mdx
+++ b/docs/sdk/integrations-anthropic.mdx
@@ -25,7 +25,7 @@ Using Claude Agent SDK instead of the direct provider SDK? See [Claude Agent SDK
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- `@anthropic-ai/sdk` installed.
-- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Cloud hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Cloud API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and Anthropic client"
npm install @asymptote/sdk @anthropic-ai/sdk
@@ -33,7 +33,7 @@ npm install @asymptote/sdk @anthropic-ai/sdk
Set environment variables:
-```bash title="Set Beacon Managed and Anthropic environment variables"
+```bash title="Set Beacon Cloud and Anthropic environment variables"
export ASYMPTOTE_API_KEY=...
export ANTHROPIC_API_KEY=...
```
diff --git a/docs/sdk/integrations-claude-agent-sdk.mdx b/docs/sdk/integrations-claude-agent-sdk.mdx
index 72b27c65..c7f64078 100644
--- a/docs/sdk/integrations-claude-agent-sdk.mdx
+++ b/docs/sdk/integrations-claude-agent-sdk.mdx
@@ -26,7 +26,7 @@ For direct Anthropic API calls through `@anthropic-ai/sdk`, use [Anthropic](/sdk
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- `@anthropic-ai/claude-agent-sdk` installed.
-- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Cloud hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Cloud API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and Claude Agent SDK"
npm install @asymptote/sdk @anthropic-ai/claude-agent-sdk
@@ -34,7 +34,7 @@ npm install @asymptote/sdk @anthropic-ai/claude-agent-sdk
Set environment variables:
-```bash title="Set the Beacon Managed API key"
+```bash title="Set the Beacon Cloud API key"
export ASYMPTOTE_API_KEY=...
```
diff --git a/docs/sdk/integrations-custom-agent-steps.mdx b/docs/sdk/integrations-custom-agent-steps.mdx
index 82c7ac63..5ac4545c 100644
--- a/docs/sdk/integrations-custom-agent-steps.mdx
+++ b/docs/sdk/integrations-custom-agent-steps.mdx
@@ -23,7 +23,7 @@ Custom agent steps are the fallback integration path for frameworks, internal to
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- The agent framework, tool client, or internal orchestration code you want to wrap.
-- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Cloud hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Cloud API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK"
npm install @asymptote/sdk
@@ -31,7 +31,7 @@ npm install @asymptote/sdk
Set an export destination:
-```bash title="Set the Beacon Managed API key"
+```bash title="Set the Beacon Cloud API key"
export ASYMPTOTE_API_KEY=...
```
diff --git a/docs/sdk/integrations-nextjs-serverless.mdx b/docs/sdk/integrations-nextjs-serverless.mdx
index 15a5a75b..360eab3c 100644
--- a/docs/sdk/integrations-nextjs-serverless.mdx
+++ b/docs/sdk/integrations-nextjs-serverless.mdx
@@ -13,7 +13,7 @@ Initialize `Observe` once in the earliest Node-only entrypoint. In Next.js, use
- A Next.js app or another serverless Node.js runtime.
- `@asymptote/sdk` installed.
- Any agent SDKs used by your route handlers, such as Vercel AI SDK.
-- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Cloud hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Cloud API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and Vercel AI SDK"
npm install @asymptote/sdk ai @ai-sdk/openai
@@ -65,7 +65,7 @@ If the runtime owns a long-lived process, reserve `Observe.shutdown()` for grace
## Customer-managed OTLP
-Serverless and preview environments can send to a customer-managed collector by setting `OTEL_EXPORTER_OTLP_ENDPOINT` instead of Beacon Managed hosted Observe credentials.
+Serverless and preview environments can send to a customer-managed collector by setting `OTEL_EXPORTER_OTLP_ENDPOINT` instead of Beacon Cloud hosted Observe credentials.
```bash title="Set the OTLP endpoint"
export OTEL_EXPORTER_OTLP_ENDPOINT=https://otel.example.com
@@ -79,4 +79,4 @@ Observe.initialize({
});
```
-Explicit OTLP export does not require a Beacon Managed `ASYMPTOTE_API_KEY`.
+Explicit OTLP export does not require a Beacon Cloud `ASYMPTOTE_API_KEY`.
diff --git a/docs/sdk/integrations-openai.mdx b/docs/sdk/integrations-openai.mdx
index f1b47788..b986356e 100644
--- a/docs/sdk/integrations-openai.mdx
+++ b/docs/sdk/integrations-openai.mdx
@@ -23,7 +23,7 @@ Initialize Beacon Observe before creating the OpenAI client when possible. The i
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- `openai` installed.
-- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Cloud hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Cloud API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and OpenAI client"
npm install @asymptote/sdk openai
@@ -31,7 +31,7 @@ npm install @asymptote/sdk openai
Set environment variables:
-```bash title="Set Beacon Managed and OpenAI environment variables"
+```bash title="Set Beacon Cloud and OpenAI environment variables"
export ASYMPTOTE_API_KEY=...
export OPENAI_API_KEY=...
```
diff --git a/docs/sdk/integrations-vercel-ai-sdk.mdx b/docs/sdk/integrations-vercel-ai-sdk.mdx
index d497c79d..2849e923 100644
--- a/docs/sdk/integrations-vercel-ai-sdk.mdx
+++ b/docs/sdk/integrations-vercel-ai-sdk.mdx
@@ -26,7 +26,7 @@ This page covers Node.js usage. For framework placement and serverless flushing,
- Node.js 20 or newer.
- `@asymptote/sdk` installed.
- `ai` and an AI SDK model provider package installed.
-- `ASYMPTOTE_API_KEY` set for Beacon Managed hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Managed API key, [reach out for a demo](https://asymptotelabs.ai/contact).
+- `ASYMPTOTE_API_KEY` set for Beacon Cloud hosted Observe, or `OTEL_EXPORTER_OTLP_ENDPOINT` set for customer-managed OTLP export. To get a Beacon Cloud API key, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK and Vercel AI SDK"
npm install @asymptote/sdk ai @ai-sdk/openai
@@ -34,7 +34,7 @@ npm install @asymptote/sdk ai @ai-sdk/openai
Set environment variables for Beacon and your provider:
-```bash title="Set Beacon Managed and OpenAI environment variables"
+```bash title="Set Beacon Cloud and OpenAI environment variables"
export ASYMPTOTE_API_KEY=...
export OPENAI_API_KEY=...
```
diff --git a/docs/sdk/integrations.mdx b/docs/sdk/integrations.mdx
index 8018a376..bce6c6e5 100644
--- a/docs/sdk/integrations.mdx
+++ b/docs/sdk/integrations.mdx
@@ -5,7 +5,7 @@ description: "Choose a Beacon Observe integration path for AI SDKs and agent orc
## Integration overview
-Beacon Observe traces supported LLM providers, agent SDKs, and orchestration code through OpenTelemetry. Initialize `Observe`, configure the integration path for the SDK you use, and your model calls or agent turns can flow to Beacon Managed hosted Observe or a customer-managed OTLP collector.
+Beacon Observe traces supported LLM providers, agent SDKs, and orchestration code through OpenTelemetry. Initialize `Observe`, configure the integration path for the SDK you use, and your model calls or agent turns can flow to Beacon Cloud hosted Observe or a customer-managed OTLP collector.
Browse the integrations below to see setup instructions, what is captured, and troubleshooting guidance.
@@ -34,7 +34,7 @@ Browse the integrations below to see setup instructions, what is captured, and t
All integration paths start by installing and initializing the SDK:
-Hosted Observe export requires a Beacon Managed API key. To get `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact).
+Hosted Observe export requires a Beacon Cloud API key. To get `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact).
```bash title="Install the SDK"
npm install @asymptote/sdk
@@ -48,7 +48,7 @@ Observe.initialize({
});
```
-See the [SDK quickstart](/sdk/quickstart) for Beacon Managed hosted Observe, customer-managed OTLP, custom exporter, and shutdown options.
+See the [SDK quickstart](/sdk/quickstart) for Beacon Cloud hosted Observe, customer-managed OTLP, custom exporter, and shutdown options.
## Not supported yet
diff --git a/docs/sdk/quickstart.mdx b/docs/sdk/quickstart.mdx
index 58c18af4..e75bbadb 100644
--- a/docs/sdk/quickstart.mdx
+++ b/docs/sdk/quickstart.mdx
@@ -17,13 +17,13 @@ The package requires Node.js 20 or newer.
## 2. Configure export
-Choose Beacon Managed hosted Observe or a customer-managed OTLP endpoint.
+Choose Beacon Cloud hosted Observe or a customer-managed OTLP endpoint.
### Hosted Observe
-Hosted Observe requires a Beacon Managed account. To get an `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact), then initialize `Observe` as early as possible in your application startup:
+Hosted Observe requires a Beacon Cloud account. To get an `ASYMPTOTE_API_KEY`, [reach out for a demo](https://asymptotelabs.ai/contact), then initialize `Observe` as early as possible in your application startup:
-```bash title="Set the Beacon Managed API key"
+```bash title="Set the Beacon Cloud API key"
export ASYMPTOTE_API_KEY=...
```
@@ -49,7 +49,7 @@ The SDK appends `/v1/observe` when the configured base URL or endpoint does not
### Customer-managed OTLP
-Use an explicit OTLP endpoint when traces should go to a local or customer-managed collector instead of Beacon Managed hosted Observe:
+Use an explicit OTLP endpoint when traces should go to a local or customer-managed collector instead of Beacon Cloud hosted Observe:
```bash title="Set the OTLP endpoint"
export OTEL_EXPORTER_OTLP_ENDPOINT=http://127.0.0.1:4318
@@ -63,7 +63,7 @@ Observe.initialize({
});
```
-Explicit OTLP export does not require a Beacon Managed API key.
+Explicit OTLP export does not require a Beacon Cloud API key.
## 3. Create a first trace
@@ -103,7 +103,7 @@ await Observe.flush();
| --- | --- |
| 1 | `initialize({ otlpEndpoint })` |
| 2 | `OTEL_EXPORTER_OTLP_ENDPOINT` |
-| 3 | Beacon Managed hosted `baseUrl` when `apiKey` or `ASYMPTOTE_API_KEY` is present |
+| 3 | Beacon Cloud hosted `baseUrl` when `apiKey` or `ASYMPTOTE_API_KEY` is present |
If neither hosted credentials nor an explicit OTLP endpoint is configured, use a custom exporter or disable the default exporter.
diff --git a/docs/sdk/reference.mdx b/docs/sdk/reference.mdx
index 7d037582..53c5f666 100644
--- a/docs/sdk/reference.mdx
+++ b/docs/sdk/reference.mdx
@@ -28,8 +28,8 @@ Function exports are also available for the same operations, including `initiali
| Option | Purpose |
| --- | --- |
-| `apiKey` | Beacon Managed hosted Observe API key. Defaults to `ASYMPTOTE_API_KEY` |
-| `baseUrl` | Beacon Managed hosted Observe base URL. Defaults to `ASYMPTOTE_BASE_URL` or `https://api.asymptotelabs.ai` |
+| `apiKey` | Beacon Cloud hosted Observe API key. Defaults to `ASYMPTOTE_API_KEY` |
+| `baseUrl` | Beacon Cloud hosted Observe base URL. Defaults to `ASYMPTOTE_BASE_URL` or `https://api.asymptotelabs.ai` |
| `otlpEndpoint` | Explicit OTLP/HTTP endpoint. Defaults to `OTEL_EXPORTER_OTLP_ENDPOINT` |
| `headers` | Additional exporter headers |
| `serviceName` | OpenTelemetry service name. Defaults to `OTEL_SERVICE_NAME` or `asymptote-app` |
@@ -60,7 +60,7 @@ Function exports are also available for the same operations, including `initiali
| Mode | How it is selected |
| --- | --- |
-| `hosted` | Beacon Managed `apiKey` or `ASYMPTOTE_API_KEY` is present and no explicit OTLP endpoint is configured |
+| `hosted` | Beacon Cloud `apiKey` or `ASYMPTOTE_API_KEY` is present and no explicit OTLP endpoint is configured |
| `otlp` | `otlpEndpoint` or `OTEL_EXPORTER_OTLP_ENDPOINT` is present |
| `custom` | Default exporter is disabled or a custom span exporter is provided |
diff --git a/docs/security/data-flow-threat-model.mdx b/docs/security/data-flow-threat-model.mdx
index 44b8f515..a42cfb6b 100644
--- a/docs/security/data-flow-threat-model.mdx
+++ b/docs/security/data-flow-threat-model.mdx
@@ -28,13 +28,13 @@ flowchart LR
| Local storage | Beacon writes one JSON object per line to `runtime.jsonl` | Filesystem permissions and log ownership |
| Local inspection | The dashboard reads the runtime log over a loopback-only service | Local browser to local dashboard service |
| Optional forwarding | Wazuh, Elastic/Filebeat, Datadog Agent, Sumo Logic, Rapid7, Microsoft Sentinel, AWS S3, Google Cloud Storage, Splunk HEC, Falcon LogScale HEC, or customer-managed shippers read or receive events | Customer-managed network and SIEM boundary |
-| Beacon Managed forwarding | After an explicit connect, Vector posts Standard or locally transformed metadata-only runtime/inventory NDJSON over HTTPS with a per-device key | Endpoint to Beacon-run service; identity derived from the device key, revocable from the dashboard |
+| Beacon Cloud forwarding | After an explicit connect, Vector posts Standard or locally transformed metadata-only runtime/inventory NDJSON over HTTPS with a per-device key | Endpoint to Beacon-run service; identity derived from the device key, revocable from the dashboard |
## Threat model
| Risk | Design response |
|------|-----------------|
-| Unintended hosted telemetry | Account sign-in forwards nothing. Managed is preselected, and confirming it starts forwarding within the same command, which the confirm screen states before the choice is accepted, naming what the selected privacy mode sends. Choosing Local forwards nothing, and `beacon endpoint disconnect` stops a connected endpoint. Runtime forwarding starts at the end of the existing log; inventory starts at the beginning so the service receives the endpoint's current inventory baseline. The active privacy mode is recorded, and forwarding stops within a minute of revocation |
+| Unintended hosted telemetry | Account sign-in forwards nothing. Beacon Cloud is preselected, and confirming it starts forwarding within the same command, which the confirm screen states before the choice is accepted, naming what the selected privacy mode sends. Choosing Local forwards nothing, and `beacon endpoint disconnect` stops a connected endpoint. Runtime forwarding starts at the end of the existing log; inventory starts at the beginning so the service receives the endpoint's current inventory baseline. The active privacy mode is recorded, and forwarding stops within a minute of revocation |
| Network exposure of collectors | Default OTLP receivers bind to `127.0.0.1` rather than an externally reachable interface |
| Over-collection of prompt or diff content | Standard applies local sanitization and size controls. Metadata-only additionally strips retained prompts, responses, reasoning, tool arguments/results, command output, raw fields, diffs, inventory content, and MCP definitions in Vector before buffering or upload |
| Secret leakage in retained content | Beacon applies redaction, sanitization, truncation, and event-size limits before writing supported content fields |
diff --git a/docs/security/endpoint-operations.mdx b/docs/security/endpoint-operations.mdx
index 0469f16d..f313df60 100644
--- a/docs/security/endpoint-operations.mdx
+++ b/docs/security/endpoint-operations.mdx
@@ -82,7 +82,7 @@ Optional network behavior is customer configured:
| Falcon LogScale HEC | Optional collector exporter sends events to the configured Falcon LogScale HEC endpoint |
| Endpoint self-update | Optional updater mode fetches the release manifest and signed package assets when manually invoked or explicitly enabled |
| Customer-managed forwarding | Customer shipper, agent, or SIEM pipeline reads local JSONL |
-| Beacon managed ingest (opt-in) | In user mode, `beacon endpoint connect` uses the signed-in CLI account to authorize a separate per-device key; system mode uses browser approval. A Vector forwarder posts runtime and inventory JSONL over HTTPS to Beacon's ingest service; the device is revocable from the dashboard, effective within about a minute |
+| Beacon Cloud ingest (opt-in) | In user mode, `beacon endpoint connect` uses the signed-in CLI account to authorize a separate per-device key; system mode uses browser approval. A Vector forwarder posts runtime and inventory JSONL over HTTPS to Beacon's ingest service; the device is revocable from the dashboard, effective within about a minute |
Beacon itself does not store Elastic cluster URLs or credentials, Datadog API keys or site configuration, Sumo Source URLs, tokens, collector configuration, or Rapid7 webhook URLs. Splunk HEC and Falcon LogScale HEC tokens are stored only in local collector configuration when those optional destinations are enabled. The Beacon device key is stored only in `asymptote/vector-secrets.json` (mode `0600`, inside a `0700` directory) under the endpoint base directory, read by Vector through its secret backend; `config.json` holds only the non-secret device and organization ids, and the key is never printed by any command.
diff --git a/docs/security/index.mdx b/docs/security/index.mdx
index 04dfc9b3..42093820 100644
--- a/docs/security/index.mdx
+++ b/docs/security/index.mdx
@@ -5,7 +5,7 @@ description: "Deploy Beacon endpoint telemetry and forward events into security
Beacon gives Security and IT teams local endpoint visibility into supported [agent harnesses](/runtimes). It captures supported activity, normalizes it into a stable endpoint event schema, and writes JSONL for local inspection or customer-managed forwarding.
-Beacon is local-only by default. The endpoint agent does not require a Beacon-hosted account, remote policy fetch, or external network dependency during normal collection. Use [Beacon Managed](/deployment/managed) when you need centralized retention, search, governance, investigations, access control, or rollout support.
+Beacon is local-only by default. The endpoint agent does not require a Beacon-hosted account, remote policy fetch, or external network dependency during normal collection. Use [Beacon Cloud](/deployment/managed) when you need centralized retention, search, governance, investigations, access control, or rollout support.
## Rollout path
@@ -77,14 +77,14 @@ Also review [Agent harness integrations](/runtimes) to confirm supported runtime
## When to move to managed
-Open Source works well when your team wants local endpoint telemetry and controls the downstream destination. Consider [Beacon Managed](/deployment/managed) when you need:
+Open Source works well when your team wants local endpoint telemetry and controls the downstream destination. Consider [Beacon Cloud](/deployment/managed) when you need:
- centralized ingest, retention, search, and detections
- fleet-wide visibility across endpoints, users, and teams
- identity mapping, approval visibility, and investigation workflows
- SSO, RBAC, audit trails, onboarding, and rollout support
-For dedicated infrastructure, stricter data boundaries, or residency requirements, ask about Private Deployment. [Contact us](https://asymptotelabs.ai/contact) to discuss Managed or Private Deployment.
+For dedicated infrastructure, stricter data boundaries, or residency requirements, ask about Private Deployment. [Contact us](https://asymptotelabs.ai/contact) to discuss Beacon Cloud or Private Deployment.
## Boundaries
diff --git a/docs/security/retention-redaction.mdx b/docs/security/retention-redaction.mdx
index 53511e47..ccf4faed 100644
--- a/docs/security/retention-redaction.mdx
+++ b/docs/security/retention-redaction.mdx
@@ -75,19 +75,19 @@ and customer-managed shippers read the resulting local JSONL. Supported cloud
agents upload a compressed snapshot of their sandbox-local JSONL directly to
customer-managed GCS or S3. Splunk HEC and Falcon LogScale HEC forwarding
receive the same normalized collector output according to the configured
-endpoint pipeline. Beacon Managed Standard mode forwards new runtime and
+endpoint pipeline. Beacon Cloud Standard mode forwards new runtime and
inventory lines as stored locally. Metadata-only mode adds a local Vector
transform that removes retained text, tool arguments/results, command output,
raw fields, diffs, inventory content, and MCP definitions before buffering or
upload while preserving stable metadata, hashes, counts, and token usage.
-The per-string limit also bounds what Beacon Managed MCP can search. Each retained
+The per-string limit also bounds what Beacon Cloud MCP can search. Each retained
string is capped at 4 KB (`DefaultStringLimit` in `pkg/asymptoteobserve/privacy.go`)
before it is written, so text past that point in a long tool output, command output,
-or diff is never forwarded and Beacon Managed grep cannot match it; the event carries
+or diff is never forwarded and Beacon Cloud grep cannot match it; the event carries
`field_truncated` and `content.truncated` instead. The limit is intentional and is
not raised for search. Metadata-only forwarding removes the content that Beacon
-Managed grep searches, so for those endpoints its grep and read return little. See
+Cloud grep searches, so for those endpoints its grep and read return little. See
[Downstream consumers](/telemetry-schema/normalization#downstream-consumers).
Review runtime scope, artifact access, destination permissions, and downstream retention before rollout so retained content matches your approved telemetry policy.
diff --git a/docs/telemetry-schema/normalization.mdx b/docs/telemetry-schema/normalization.mdx
index a125102b..b8396915 100644
--- a/docs/telemetry-schema/normalization.mdx
+++ b/docs/telemetry-schema/normalization.mdx
@@ -234,36 +234,36 @@ approval-shaped detections have something to match. Nothing was gated there, so
## Downstream consumers
-Beacon Managed MCP searches and reads the session history an endpoint forwards to Beacon Managed,
-and it works from this normalized schema. A schema change can therefore change what Beacon Managed
+Beacon Cloud MCP searches and reads the session history an endpoint forwards to Beacon Cloud,
+and it works from this normalized schema. A schema change can therefore change what Beacon Cloud
search finds, in three ways:
-1. **Searchable fields.** Beacon Managed grep searches these fields: `prompt`, `message`,
+1. **Searchable fields.** Beacon Cloud grep searches these fields: `prompt`, `message`,
`gen_ai.{input,output,system_instructions,tool,retrieval}`, `tool`, `command`, `file`, `mcp`,
`approval`, `policy`, `error`, and `health`. Content in a new field is forwarded and stored, but
- grep does not find it until Beacon Managed searches that field too.
-2. **Event types and message shapes.** Beacon Managed presents events the way the local trace view
+ grep does not find it until Beacon Cloud searches that field too.
+2. **Event types and message shapes.** Beacon Cloud presents events the way the local trace view
(`internal/endpoint/dashboard/traces.go`) does. A new event type or message shape appears there
- as a generic event until Beacon Managed supports it.
-3. **Harness names.** Beacon Managed groups sessions by the canonical names `NormalizeHarnessName`
+ as a generic event until Beacon Cloud supports it.
+3. **Harness names.** Beacon Cloud groups sessions by the canonical names `NormalizeHarnessName`
in `pkg/asymptoteobserve/harness.go` produces. A new harness or spelling is grouped correctly in
- Beacon Managed only once Beacon Managed knows it too.
+ Beacon Cloud only once Beacon Cloud knows it too.
-Release a change to any of these together with the matching Beacon Managed change.
+Release a change to any of these together with the matching Beacon Cloud change.
-### What Beacon Managed grep cannot see
+### What Beacon Cloud grep cannot see
-Two limits on what Beacon Managed grep and read return come from the endpoint, and both are intended:
+Two limits on what Beacon Cloud grep and read return come from the endpoint, and both are intended:
- **Per-string limit.** `DefaultStringLimit = 4096` in `pkg/asymptoteobserve/privacy.go` caps each
retained string before it is written. Text past the first 4 KB of a long tool output, command
- output, or diff is never written locally, so it is never forwarded and Beacon Managed grep cannot
+ output, or diff is never written locally, so it is never forwarded and Beacon Cloud grep cannot
match it. The event records the cut with `field_truncated` and `content.truncated`. This trades
completeness for privacy and a bounded event size; see
[Redaction and size limits](/security/retention-redaction).
-- **Metadata-only forwarding.** An endpoint connected to Beacon Managed in Metadata-only mode
+- **Metadata-only forwarding.** An endpoint connected to Beacon Cloud in Metadata-only mode
removes prompts, responses, reasoning, tool arguments and results, command output, and diffs
- before upload. Those are the fields grep searches, so for such endpoints Beacon Managed grep and
+ before upload. Those are the fields grep searches, so for such endpoints Beacon Cloud grep and
read return little beyond identifiers, counts, and token usage.
## Related
diff --git a/packaging/linux/fetch-vector.sh b/packaging/linux/fetch-vector.sh
index c5d12850..326f1cab 100755
--- a/packaging/linux/fetch-vector.sh
+++ b/packaging/linux/fetch-vector.sh
@@ -17,7 +17,7 @@
# against the result before shipping it. 0.56.0 matches the signed macOS package. Newer releases
# break the generated packs, which take destinations and credentials from ${VAR}: 0.57 stops
# expanding the ${VAR:-default} form, and 0.58 stops expanding ${VAR} at all unless Vector runs
-# with --dangerously-allow-env-var-interpolation. (Beacon Managed's connect is unaffected because
+# with --dangerously-allow-env-var-interpolation. (Beacon Cloud's connect is unaffected because
# it writes literal values.)
set -eu
diff --git a/pkg/asymptoteobserve/harness.go b/pkg/asymptoteobserve/harness.go
index 9f5f8eee..9f39b153 100644
--- a/pkg/asymptoteobserve/harness.go
+++ b/pkg/asymptoteobserve/harness.go
@@ -22,8 +22,8 @@ import "strings"
// Ordering matters. The browser-chat cases must precede the generic "claude" rule, which would
// otherwise coerce claude_web into claude_code.
//
-// Beacon Managed groups forwarded sessions by these canonical names, so a new harness or spelling
-// here needs a matching Beacon Managed change in the same release; see "Downstream consumers" in
+// Beacon Cloud groups forwarded sessions by these canonical names, so a new harness or spelling
+// here needs a matching Beacon Cloud change in the same release; see "Downstream consumers" in
// docs/telemetry-schema/normalization.mdx.
func NormalizeHarnessName(name string) string {
lower := strings.ToLower(strings.TrimSpace(name))