Give each team member their own API key on a shared CLIProxyAPI instance.
Track token usage and estimated cost separately for every user.
Let an admin monitor global traffic and filter logs by user, model, or failures.
Maintain a pricing catalog so cost estimates stay accurate as providers change prices.
| walkingddd/cpa-helper | sliverkiss/mimocode2api | tj/go-gracefully | |
|---|---|---|---|
| Stars | 63 | 65 | 66 |
| Language | Go | Go | Go |
| Last pushed | — | — | 2014-12-27 |
| Maintenance | — | — | Dormant |
| Setup difficulty | moderate | easy | easy |
| Complexity | 3/5 | 2/5 | 2/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Documented primarily in Chinese, requires a running CLIProxyAPI instance.
CPA-Helper is a self-hosted multi-user management dashboard for CLIProxyAPI (also known as CPA), a service that acts as a proxy for AI model APIs. The dashboard provides a web interface for tracking usage, managing API keys, and monitoring requests across multiple users who share the same CPA service, useful for a small team or group sharing AI API access. Each user can create and manage their own API keys independently, and their usage data (number of requests, tokens consumed, and estimated costs) is tracked separately from other users. An administrator can create or disable user accounts, view all global traffic across every user, filter request logs by time, user, model, and failure status, and maintain the pricing catalog for each AI model so that cost estimates remain accurate as provider prices change. There is also a Codex account monitoring feature that can run on a schedule to check and maintain Codex authentication files. The project is built with a Go backend (using SQLite as the local database), a Vue 3 front-end (using Vite, Naive UI, and ECharts for charts), and supports Docker deployment for easy setup. It is documented primarily in Chinese, though an English README is also available. You would use this if you run a shared CPA instance for yourself or a small team and want visibility into who is using which models, how much it costs, and centralized control over API keys without each person having direct access to the underlying service credentials.
A self-hosted dashboard for managing multiple users sharing one CLIProxyAPI service, tracking usage, keys, and costs per person.
Mainly Go. The stack also includes Go, Vue, SQLite.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.