Packages Overview
In one sentence
You ship two artifacts — the browser collector and the edge binary; the inference API is Octet's, and there is nothing for you to install for it.
The artifacts
| Artifact | What it is | Where it runs | You install it? |
|---|---|---|---|
Collector — @octetproof/collector | A small browser package (ESM + <script>). Reads signals and posts them. | The end-user's browser, served from your origin | Yes — from GitHub Packages |
Edge — octet-edge | A small static Linux binary. Observes connection-level signals and forwards. | Your network edge (Linux, connection-terminating) | Yes — a release binary |
| Inference API | Where signals become a verdict. | Octet's servers only | No — nothing to install |
Both things you ship are logic-free: they collect and forward, nothing more. All reasoning lives behind the inference API, which is Octet's and is never distributed.
How they fit together
The collector posts to your edge; the edge forwards to Octet; your backend reads the verdict server-to-server. See How It Works for the full picture.
Get each one
- Collector (browser) — install from GitHub Packages, or drop in a
<script>tag. - Edge Binary — obtain the prebuilt binary or build from source.
Then follow the Integration Guide to wire them up.