Skip to main content

Edge Binary

In one sentence

octet-edge is a small static Linux binary you run at your edge — use the prebuilt release, or build it from the source Octet provides.

The edge is a logic-free harvester + connector: it observes a few connection-level signals and forwards the bundle to Octet. It holds no rules, tables, or thresholds.

Option A — Use the prebuilt binary​

Octet provides octet-edge as a static linux/amd64 binary (a few MB, no runtime dependencies). Place it on your edge host and make it executable:

chmod +x octet-edge-linux-amd64
./octet-edge-linux-amd64   # see Deploy the Edge for the env it needs

Option B — Build from source​

If you'd rather build it yourself (it's a single Go module), produce the static Linux binary with:

cd apps/edge
GOOS=linux GOARCH=amd64 CGO_ENABLED=0 \
  go build -trimpath -ldflags="-s -w" -o octet-edge-linux-amd64 .

You can also build a local binary for development on macOS or Linux (go build -o octet-edge .), but note that the connection-level timing signal is Linux-only — a non-Linux build runs for testing but won't produce that signal.

Requirements​

  • Linux (x86-64). The binary is built for linux/amd64.
  • The host must terminate the browser's TCP connection — the one hard rule. See Deploy the Edge.
  • Outbound HTTPS to Octet's API. (Mutual TLS is planned hardening — see Edge Configuration.)

Where to go next​