Skip to content
nikcli

Data

What nikcli actually runs on

Two telemetry sources, kept apart because they measure different things: what installs report about the models they run on their own provider keys, and what the hosted gateway billed. Every card says which one it is drawing. Adoption, at the end, comes from a third — the public release log. Nothing is modelled, smoothed or back-filled.

No gateway usage published yet

The inference gateway has recorded no completions in the last 30 days, or this deployment cannot reach the usage feed. Rather than draw an empty axis, this page shows the sections it can measure. Adoption, below, comes from the release log and is always current.

Release log

Adoption

Cumulative installs since May 27, recorded by the release workflow in STATS.md. Plotted on a real time axis — the log is written on release days, not daily.

85,373 total

0 20K 40K 60K 80K 100K May 27 Jun 27 Jul 29 Aug 29 Sep 30

The 8 most recent of 66 readings, split by source. Readings are taken on release days, so the dates are not consecutive.

Recorded download totals, newest first
Recorded npm GitHub Total
Sep 30 80,476 4,897 85,373
Sep 29 80,118 4,857 84,975
Sep 28 77,035 4,853 81,888
Sep 27 76,004 4,806 80,810
Sep 26 74,847 4,738 79,585
Sep 25 72,634 4,683 77,317
Sep 24 72,634 4,641 77,275
Sep 23 72,634 4,640 77,274

Edge counter

Where downloads come from

Downloads that passed nikcli-ai.dev/releases/download — the URL the install scripts fetch from — resolved to a country at the edge and then handed to GitHub, which serves the file and counts it as it always has. GitHub and npm publish a download total with no geography attached, so this is measured here rather than derived from either, and it counts only from the day the route shipped: the 85,373 in the release log above have no country and never will.

Italy — 87 downloads Netherlands — 2 downloads
  • 01 Italy 87 98%
  • 02 Netherlands 2 2%
2 countries over the last 90 days · counting since 2026-08-23

How this is measured

Sources
Gateway figures are one row per served completion, written to the same table billing reads. Community figures are what installs report about the models they run themselves. Adoption comes from STATS.md in the repository.
Time windows
Headline figures and the leaderboard cover 30 days; the charts cover 60. Change compares consecutive 30-day windows.
Privacy
Only aggregates are queried. No account, key or request identifier is read, so nothing here can be traced to a user. Prompt content is never stored in the first place. Community reporting is off unless you turn it on, and the identifier an install sends is random, local, and never published.
Freshness
Rendered Oct 30, 2026, 12:55 AM UTC and cached at the edge for 15 minutes.