Skip to main content

​
Choose your platform

This page installs the CLI. Setting up the endpoint agent, the local collector that captures agent activity, differs by operating system, so start with your platform:

macOS

Homebrew for your own machine, or the signed .pkg for a managed fleet. launchd.

Linux

A .deb or .rpm that installs and starts the endpoint for you. systemd.

​
Homebrew

Install the Beacon CLI with Homebrew:
Install Beacon
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 Asymptote Managed forwarder; 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.
beacon version output

​
Other install methods

Beacon releases publish macOS and Linux archives for amd64 and arm64 alongside Homebrew builds. For archive-based installs or source builds, see Manual CLI Installation. Releases also attach native endpoint packages, which install the CLI, the collector, and the service together rather than leaving you a second step:

​
Next steps

After installing Beacon, configure the workflow you need:

Endpoint telemetry

Configure local agent harness telemetry.

Cloud agent telemetry

Configure provider-managed cloud agent telemetry setup helpers.

CI telemetry

Run ephemeral AI runtime telemetry collection in CI.

Upgrade Beacon

Keep the Beacon CLI up to date.