> ## Documentation Index
> Fetch the complete documentation index at: https://docs.d0pam1ne.blackhatethicalhacking.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy a beacon

> Enrol the agent on a machine inside the client network with one command.

Open a project, then **Internal Pentest, Deploy**.

**1. Name it and pick the site**

Give the beacon a name you will recognise (for example the office or the host it runs on) and a **site** or segment. Every asset it finds is filed under that site, so a client with several offices gets one beacon per site and a report per site if they want one.

**2. Pick the platform**

macOS (Apple Silicon or Intel), Linux (x86\_64 or arm64) or Windows (x86\_64). The binaries ship pre-built with Pro, and the installer downloads the matching one from your own console.

**3. Run the installer**

Copy the one-line command and run it on the machine inside the client network. It enrols the agent and installs it as a service: a machine-wide LaunchDaemon on macOS (installed with `sudo`), a system service on Linux, and a logon task on Windows. When your console uses a self-signed certificate, turn on the self-signed toggle so the command trusts it.

**4. Watch it check in**

The beacon card turns from **Awaiting first check-in** to **Online** within seconds. It then checks in on a fixed interval; a beacon that stops checking in shows **Offline**, and the Command Center lists it under Needs you now.

## Beacon cards

Each card shows the beacon's site, host, platform and version, when it last checked in, how many assets it has found, and whether its **pivot** and **monitoring** are on.

* **Pivot**: turn it on to let the console reach deeper through the beacon for [Internal Recon](https://docs.d0pam1ne.blackhatethicalhacking.com/beacon/internal-recon.md) and [Internal Attacks](https://docs.d0pam1ne.blackhatethicalhacking.com/beacon/internal-attacks.md). Discovery sweeps do not need it.
* **Monitoring**: keeps the inventory fresh between assessments by re-checking known assets on a cadence, which is what keeps their **Seen** dots green.
* **Kill switch**: revokes the beacon. On its next check-in it uninstalls itself. Removing a beacon clears its record; the assets it found stay in the project.

## Versions

The Deploy page compares the agent version in the source with the published binaries. When they differ it asks for a rebuild, and updating Pro does not replace an agent that is already enrolled: redeploy it to pick up agent-side improvements.

## Checking a macOS beacon

If a Mac beacon is online but finds nothing, check the service and its network access on that Mac:

```bash theme={null}
sudo launchctl print system/sh.d0p.beacon
sudo /usr/local/bin/d0pam1ne-beacon arpdump   # compare with: arp -a
```

Then test one known open internal host and port before a whole subnet. A code signature on its own does not prove the service can reach the local network.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.