Usage & Cost
Lattis attributes every request and tracks token usage broken down by app, model, project, and conversation. For paid cloud models it also estimates the dollar cost from the provider’s reported token counts.
What’s tracked
Section titled “What’s tracked”- Per-app — which client/tool made the request.
- Per-model — local or cloud model id used.
- Per-project — work attributed to a project context, and per branch within it.
- Per-conversation — spend on each conversation in Lattis’s own chat.
Token counts come from the local inference engine or the provider’s reported usage fields, so the breakdown reflects the usage information available for each request. Within a project branch, spend is further broken down per model, when the provider supplies the required data.
Persistence
Section titled “Persistence”Usage is recorded to an on-disk store (telemetry.db in the data directory) and
rehydrated when the daemon restarts, so your totals survive restarts. Costs are
priced at the moment a request is made and stored as recorded, so historical
figures don’t shift when the price table changes. Live-only state — active
connections and the current tokens/second — resets with the daemon.
The web app: spend & activity across machines
Section titled “The web app: spend & activity across machines”Usage is tracked locally by default. If you connect the optional web app, selected usage and cost data is uploaded for its dashboard. The Lattis web app at app.getlattis.ai can aggregate that data across connected machines and your team.
Sign in with GitHub, Google, or a magic link — signing in for the first time creates your account and a personal organization automatically (there is no separate signup). Once you connect your desktop app, you get:
- Overview — spend, cache savings, active users, LLM calls, latency, and error rate in one overview.
- Spend — dollar spend over time, broken down by project and model.
- Traces & Sessions — drill into individual calls and whole sessions, with per-request cost, latency, and tool failures.
- Models — spend and cost-effectiveness per model, so you can decide what runs where.
- Team & Members — invite people, set roles, and see an org-wide leaderboard.
Lattis stays fully local by default; the web app is opt-in, and nothing is sent unless you connect an account.
Connecting your desktop app
Section titled “Connecting your desktop app”In the desktop app, choose Connect account. Your browser opens the web app’s
/desktop/connect handoff; once you’re signed in it hands a one-time code back
to the app over a local loopback callback. The code is returned through that
redirect and is not displayed or logged. Activity from the connected desktop then
appears in the dashboard.
The web app is currently free during the public beta; see Pricing for the current plan details.
Cost estimation
Section titled “Cost estimation”Cloud providers report token counts, not dollars. Lattis multiplies those counts by a per-model price table (split by billing category — standard input, output, cached-input reads, and cache writes) to produce an estimate. Local models are free, so no cost is shown for them.
Because pricing is an estimate derived from a built-in table, treat the numbers as a close guide rather than an invoice.
Why it matters
Section titled “Why it matters”A single endpoint serving multiple models and providers can make it difficult to track where tokens and money go. Per-project attribution shows the available cost for a project, and the per-model breakdown lets you compare local and cloud use.
See Cloud Providers to connect a paid provider, and the Control API for the daemon snapshot that surfaces these figures.