Telemetry

Exactly what leaves your box.

No trackers, no analytics beacons, no silent exfiltration. Here is the complete list of what a self-hosted Okapi sends us — and what it never does.

The check-in sends

instanceId: a random instance id (not tied to you personally)

version: the build you're running

os and arch: operating system and CPU architecture, unless telemetry is disabled

licenseKey: your license key, only when a license is activated

It never sends

Your events, stack traces, or log contents

Your users' data, IPs, or PII

Project names, DSNs, or source code

One thing that is in neither list: like any HTTP server, we see the IP address a request arrives from, and we record it on license requests — activation and check-in. That is connection metadata, not a field your instance sends.

A licensed check-in with telemetry enabled, every few hours:

Unlicensed instances send the same check-in without licenseKey. With telemetry disabled, os and arch are omitted; an unlicensed instance sends only GET /v1/latest instead. Safe mode suppresses both requests.

POST /v1/checkin

{

"instanceId": "0199c3e2-…",

"version": "0.8.0",

"os": "linux",

"arch": "amd64",

"licenseKey": "OKAPI-XXXX-…"

}

Start catching errors before your users do.

One binary and Postgres, on your own infrastructure. A 14-day trial is built in — no signup, no key. MCP on every plan, and a price that never moves.

Start self-hosting See pricing →

14-day trial · Sentry-SDK compatible · Runs on your own infrastructure