59 providers from one engine
Quota, spend, reset windows, token totals, request totals, and local-model server state share one Rust provider core.
LLM Status keeps rate limits, balances, spend, token totals, request totals, and local-model server state visible across 59 provider integrations on Windows, macOS, Android, and iOS.
Private test builds only. Read platform-specific install notes.
Quota, spend, reset windows, token totals, request totals, and local-model server state share one Rust provider core.
Every account keeps its own credentials, history, and alert state, so two Claude, Codex, or Copilot plans never blur together.
Android home-screen widgets and iOS WidgetKit previews keep critical providers visible between app opens.
Tray and menu-bar status, usage history, threshold alerts, a GitHub developer dashboard, and optional InfluxDB-compatible metrics export.
One device shows a six-digit code and the other finds it on your own network. Both prove they know the code, and every later transfer is encrypted end to end.
Credentials stay in platform secure storage. There is no product telemetry, and this site runs no analytics or tracking cookies.
Windows and Android carry the current test packages. Every client shares the same Rust engine, so provider coverage does not depend on which screen you open.
Tray flyout, dashboard, usage history, alerts, backup and import, credential scan, device pairing, and optional metrics export.
Menu-bar app on the same Rust engine with Keychain storage and a template icon. Apple packaging is gated on Apple build capacity, with production trust gated on Developer ID signing and notarization.
Native Compose test client with encrypted credentials, account slots, alerts, history sparklines, home-screen widget, WorkManager refresh, and PIN-protected config transfer.
SwiftUI Simulator preview with Keychain storage, multiple accounts, history sparklines, local alerts, WidgetKit widgets, secure OAuth refresh, and PIN-protected config transfer.
Reuse supported sessions and keys, connect with OAuth/device flows, paste API credentials, or monitor local Ollama, LM Studio, and llama.cpp servers.
LLM Status uses secure operating-system storage, talks directly to the providers you configure, and does not collect product telemetry.
DPAPI, Keychain, Android encrypted preferences, and iOS Keychain keep secrets off the marketing site.
Credentials are used only to request usage information from the providers you connect, and they are not forwarded to a different origin.
Review the MIT-licensed source, architecture, provider fact sheets, and release gates in the repository once you have access. View source.
Under Settings, one device shows a six-digit code and the other finds it on the local network. No account, relay, or cloud service sits between them.
Each side proves it holds the six-digit code with SPAKE2, so a device sitting in the middle cannot join the pairing.
The listener starts only when you begin pairing, accepts local-network addresses only, stops after ten idle minutes, and five wrong codes end the attempt.
A paired device can send or fetch a configuration with or without API keys, and only after the other device's owner accepts the request.
Pairing is implemented source work in the desktop, Android, and iOS clients; testing between two physical devices is still pending.
Recent changes focus on encrypted transfer, archive ownership, truthful provider data, and credential handling.
Exporting a configuration asks for a 4-6 digit PIN and encrypts the file with it (Argon2id plus ChaCha20-Poly1305). Desktop exports open on phones, and the reverse.
Usage history is kept in a local archive (the on-screen chart keeps up to 288 samples per account), exportable as credential-free JSONL and CSV, with a desktop JSONL restore preview.
Provider credentials are no longer forwarded when a request redirects to a different origin, and the build carries current advisory fixes for its TLS and ZIP dependencies.
Providers without a verified read-only usage API report Unsupported instead of a fabricated zero, and fixture checks fail closed when a metric-bearing payload loses a required field.
The current build spans 59 providers, adds llama.cpp alongside Ollama and LM Studio, pairs nearby devices without a server, and encrypts exported configurations with a PIN. The signing and store gates below still stand between this build and a public distribution.
The current test build ships Windows 10 1809+/11 and Android 8+ packages. A macOS 11+ menu-bar client and an iOS 16+ Simulator preview are built from the same source, with Apple packaging gated on Apple build capacity.
Credentials use secure operating-system storage and are sent only to the provider APIs you configure. LLM Status does not collect product telemetry.
No. Test builds are shared privately with repository members. When paid early access is offered, it is a one-time $1.99 purchase through Stripe.
No. Version 0.4.32 is a test build. Windows installers are unsigned, Android packages are debug-signed, and Apple packages are gated on Apple build capacity.
llama.cpp joins Ollama and LM Studio as a local-server provider for 59 providers in total, nearby devices pair with a six-digit code and no server, exported configurations are PIN-encrypted, usage archives restore from JSONL, and desktop gains a GitHub developer dashboard.
Test builds are staged in the private repository rather than published as public downloads, so installers are shared with repository members. Request access before following the platform install notes.
59 providers, native desktop and mobile clients, device pairing, widgets, alerts, local servers, and MIT-licensed release notes.
View release notes and builds