Licensing
Octet issues you two keys — a license key the edge presents, and a partner key your backend uses to read verdicts; richer activation is on the roadmap.
Today
Two credentials, both issued by Octet, gate the two channels that reach Octet:
| Key | Used by | How it's sent | Gates |
|---|---|---|---|
| License key | The edge | LICENSE env → x-octet-license header | The edge → Octet signal channel. |
| Partner key | Your backend | x-octet-partner-key header | The backend → Octet verdict-fetch channel. |
The license key acts as a kill-switch and attestation for the edge: it identifies your deployment and can be revoked. The partner key authorises your backend to read verdicts. Keep both secret and out of any browser-delivered code — neither ever belongs in the page.
See Deploy the Edge for where the license key goes, and Fetch the Verdict for the partner key.
On the roadmap
Today these are keys Octet issues you directly. Richer license activation and management — self-service issuance, rotation, and lifecycle — is planned, delivered through Octet's license service. When it lands, the way you obtain and manage keys will improve; the way you use them in the edge and your backend will stay the same, so nothing in your integration needs to change ahead of time.
Details of how keys are formatted, signed, validated, or rate-limited are internal to Octet and are not part of your integration. You receive keys and present them as shown above.
Where to go next
- What Octet Provides. The full list of what Octet issues you.
- Deploy the Edge · Fetch the Verdict.