Cloud & team dashboard

tok0 cloud is an opt-in commercial feature. It exposes a team-level dashboard at tok0.dev/team/<your-org> showing aggregated savings across every developer who has logged in with the same team token. It is gated behind a build flag — the default open-source binary does not include it.

If you don’t need team-wide rollups, ignore this page.

When to enable it

Use cloud features when:

• You want a single dashboard rolling up token savings across an engineering org.
• You want to attach a cost number ($) to those savings using your real provider rates.
• You want to share a custom rule pack with your team and have everyone auto-update it.

Skip cloud features when:

• You’re a single user. tok0 stats already shows everything you need locally.
• Your org has policies against shipping any usage telemetry. The free tok0 binary is a complete, isolated tool — keep it that way.

Installing the cloud-enabled binary

cargo install tok0 --features cloud

Or, for the official prebuilt:

curl -fsSL https://tok0.dev/install.sh | sh -s -- --features cloud

Verify:

tok0 --version
# tok0 0.4.x (cloud)

The (cloud) suffix indicates --features cloud was compiled in.

Logging in

tok0 auth login

A browser opens to tok0.dev/auth/cli. Log in with your team SSO; tok0 receives a token via local-loopback callback and writes it to your OS keychain (Keychain / Credential Manager / libsecret).

Or non-interactively:

tok0 auth login --token <api-token>

Useful for CI agents.

tok0 auth status     # whoami + which org
tok0 auth logout     # revokes the local token

What gets uploaded

When cloud is enabled and you’re logged in, the same payload telemetry sends — version, OS, daily event count, tokens saved, list of compressors used — is associated with your org for the dashboard rollup. Specifically:

{
  "instance_id": "f1c2…",
  "tok0_version": "0.4.2 (cloud)",
  "os": "darwin",
  "arch": "aarch64",
  "events_today": 142,
  "tokens_saved_today": 18402,
  "compressors_used": ["git", "cargo", "npm"],
  "org_id": "acme-corp"     // ← only field that differs from anonymous telemetry
}

There is no field for command args, output content, paths, or developer identifiers. The instance_id ties events to a machine; the org_id ties machines to your organization. Neither ties events to a person.

Team dashboard

Once logged in:

tok0 cloud team        # opens tok0.dev/team/<your-org> in browser
tok0 cloud team --json # machine-readable export (last 30 days)

The dashboard shows:

• Total tokens saved across the org, by day.
• Top compressors by savings.
• Per-developer rollup (opt-in by each developer).
• A cost estimate using rates you configure.

Dashboards refresh on the next telemetry ping (typically within 24 h of new activity).

Configuring provider rates

# ~/.config/tok0/config.toml
[cloud.rates]
default_per_million_input  = 3.00     # USD per 1M input tokens
default_per_million_output = 15.00    # USD per 1M output tokens

[[cloud.rates.override]]
match = "claude-3-5-sonnet"
per_million_input  = 3.00
per_million_output = 15.00

[[cloud.rates.override]]
match = "gpt-4-turbo"
per_million_input  = 10.00
per_million_output = 30.00

Rates are applied client-side — you ship token counts, the dashboard computes dollars from your config. Rates never travel.

Self-hosting the cloud backend

The cloud backend is open-source at apps/api/ in the monorepo. It’s a Cloudflare Workers + D1 + KV stack you can deploy to your own account in ~10 minutes:

git clone https://github.com/prxm-labs/tok0
cd tok0/apps/api
pnpm install
pnpm wrangler deploy

Then point your binary at it:

# ~/.config/tok0/config.toml
[cloud]
api_url = "https://api.acme-corp.dev"

Self-hosting gives you 100% data residency. The binary doesn’t care; it just speaks HTTPS to whatever URL you configure.

Pricing

Free for teams under 10 developers. Beyond that:

• Team — $19 / dev / month — dashboard, rollups, cost tracking.
• Enterprise — custom — SSO, audit logs, self-hosted backend support, SLA.

The CLI itself is and will always remain MIT-licensed and free.

Removing cloud

tok0 auth logout
brew install tok0   # or whichever installer — the default binary has no cloud subcommands

After this, tok0 auth, tok0 cloud team, and the org-tagged telemetry are all gone. Local stats continue working as before.