Add analytics to your dev tool Dev tools.

# from your CLI or SDK, on key moments (opt-in telemetry):
curl -X POST https://YOUR-INSTANCE/v1/events \
  -H "Authorization: Bearer WRITE_KEY" \
  -d '{"name":"cli_run","distinct_id":"anon_or_project_id","properties":{"cmd":"build","ok":true,"version":"1.4.0"}}'

<!-- docs site head, to see docs-to-install: -->
<script src="https://YOUR-INSTANCE/sdk.js"></script>
<script>smolanalytics.init("WRITE_KEY", { host: "https://YOUR-INSTANCE" });</script>

There is no browser SDK for a CLI: POST batched events to /v1/events on install, first run, and errors. Put the script snippet on the docs site so you can join docs reads to actual installs.

Measure the developer activation path: docs visit, install, first run, first successful run, then repeat use across days. The signal that predicts retention is first successful run, so tag whether each invocation succeeded and which command it was, plus tool version so you can see adoption of new releases and where old versions get stuck. Errors are product feedback here: send failed runs with a reason and you get a ranked list of what breaks people on day one.

The fit is that dev tools emit events from everywhere except a browser, and this is a single endpoint that takes JSON from any language, batched up to 10k to save calls. Keep telemetry opt-in and PII-free with an anonymous or project-level distinct_id. Best part for a builder: you ask usage questions in plain English from your editor over MCP, so checking whether the new release lifted successful-run rate never leaves your terminal, and the answer is a deterministic report, not a guess.

Honest pricing: 14-day full trial, no credit card. Then Solo $29/mo, never metered on seats or sites. Overage is $5/million with an emailed receipt, the dashboard never locks, and self-hosting the single Go binary is free forever (MIT).

questions