tret

Open data

Self-hosted tret instances can opt in to send a small, anonymous weekly report. This page shows the combined totals across everyone who has.

These figures cover only self-hosted instances whose admin opted in — they exclude Tret Cloud entirely.

They are self-reported by each instance and unaudited. Small numbers here are expected early on and will grow as more instances opt in. Reporting has no authentication, so treat these figures as directional, not verified.

The numbers

Live figures load here.

What is collected

Every report is built field by field from a fixed allowlist — nothing is ever serialized wholesale. In plain language, a report includes:

  • A random id for the instance, not tied to any account — deleted the moment telemetry is turned off
  • The reporting window (start and end date)
  • tret's version, how it's deployed (docker / fly / render / bare), and the database engine (postgres or sqlite, major version only)
  • Rough size bands for users, workspaces, and runs — e.g. "2–5" or "101–1000" — never exact counts
  • Token counts for the window, rounded to two significant figures
  • Energy (Wh) and CO₂e (g) accounted for the window, rounded
  • Which providers, model families, task types, and run outcomes were used, as shares of the window's runs — never a specific custom model name
  • Which carbon-factor tier was used to estimate emissions (e.g. provider-reported, regional grid default) — never the specific grid zone
  • Which optional features are switched on (packs, connections, delegation, local models) — true / false only

Never sent: prompts, outputs, transcripts or any free text; emails or display names; workspace, project, harness, or pack names; hostnames or URLs; API keys; custom or private model names; exact counts of users, workspaces, or runs; the grid zone or region used for carbon accounting; cost in dollars.

Every request does carry a fixed tret-telemetry/1 User-Agent, and — like any HTTPS request — the sending instance's IP address reaches Cloudflare's network edge as part of the connection. The receiving service stores neither the IP address nor the User-Agent, nor any other request header.

Field-by-field documentation: docs/telemetry.md. Worker source: telemetry-ingest.

How to opt in / opt out

Off by default. An admin can turn it on from Settings → Anonymous usage statistics, or an operator can set the environment variable TRET_TELEMETRY=on before the instance starts — useful for headless installs.

Turn it off any time from Settings, or with tret telemetry disable at the CLI — either way, the instance's random id is deleted immediately. An operator can also lock telemetry off with TRET_TELEMETRY=off or DO_NOT_TRACK=1, which overrides everything else; since that only takes effect on restart, the id is deleted at that restart rather than the instant the variable is set. Nothing further is sent until telemetry is turned back on, which mints a new id with nothing in the payload connecting it to the old one.