Analysis updated 2026-05-18
Track how much each developer on your team is spending on AI coding tools across multiple providers in one dashboard.
Set monthly budget caps per team and receive Slack or email alerts before the budget runs out.
Measure whether AI coding tools have lasting adoption by seeing weekly active rates and retention over time.
| 0xkaz/llm-governance-dashboard | 0-bingwu-0/live-interpreter | ahsinmemon/asn-face-attendence-system | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Python | Python | Python |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a Google Cloud project with BigQuery enabled and a service account JSON key outside the repo.
This is a self-hostable dashboard for teams that have deployed AI coding tools like Claude Code, Codex, or Cursor and now need visibility into how much money is being spent and whether the tools are actually being used. The system works by placing a proxy gateway in front of every AI provider your team uses. Instead of developers calling OpenAI or Anthropic directly, they point their tools at this local proxy using a per-user API key. Every request passes through LiteLLM, a library that handles routing to the right upstream provider, and each call is recorded as a row in a BigQuery table with details like the user, team, model, tokens used, cost in dollars, and response latency. No personal data is stored, only anonymized identifiers. A FastAPI dashboard turns that log data into two things: cost governance and adoption tracking. The cost side shows spending per user and team, tracks each group against a monthly budget, and sends Slack or email alerts when a team hits 80 or 100 percent of its limit. Virtual API keys can be issued and revoked from the dashboard. The adoption side shows whether people are actually returning to use the tools each week, how many different tools each person uses, and trend charts for daily active usage. It distinguishes between a productivity claim and a simple activation signal. The whole stack runs locally via Docker. You configure a BigQuery project, run a setup command to create the table, then bring up the proxy with Docker Compose. Adding a new provider requires only an entry in a YAML config file and the provider API key. The dashboard is available in English and Japanese. The project is described as a demo and reference implementation, not a production-hardened system.
A self-hostable dashboard that puts a proxy in front of AI coding tools, logs every request to BigQuery, and shows teams their AI spending and adoption metrics.
Mainly Python. The stack also includes Python, FastAPI, LiteLLM.
Use freely for any purpose including commercial, as long as you keep the copyright notice.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.