Use this command to install CPA Manager Plus with WinGet:
winget install --id=seakee.CPAManagerPlus -e
A self-hosted CPA / CLIProxyAPI management panel and AI gateway observability dashboard for requests, usage, cost, quota, failures, and account health.
What Can CPAMP Help You Answer?
- Why are requests failing? Inspect failure rates, status codes, affected models/accounts, and redacted evidence in persistent request history.
- Where is the cost going? Break down tokens and estimated cost by model, provider, account, API key, project, channel, and time range.
- Are accounts and quotas healthy? Review credential state, quota windows, reset evidence, and controlled automation for Codex and xAI accounts.
Core Capabilities
CPA Gateway Management
- Manage CPA provider configurations, including Gemini, Codex, Claude, Vertex, xAI, and OpenAI-compatible providers.
- Maintain auth files, OAuth logins, API keys, model aliases, priorities, plugins, logs, and system settings.
- Import official Sub2API OpenAI OAuth exports and split multiple accounts into separate CPA Codex auth files.
Request Monitoring And Failure Diagnosis
- Persist requests from the CPA usage queue in local SQLite and search account, client API key, and realtime request views.
- Inspect status, latency, token, cache, trace, and redacted failure evidence without exposing raw failure bodies.
- Export or import request history as JSONL.
- Open the Monitoring Demo.
Cost And Usage Analytics
- Break down calls, tokens, cost, latency, and failures by model, provider, account, credential, API key, project, channel, and time range.
- Track input, output, reasoning, cache, service tier, and long-context pricing semantics.
- Sync model prices from models.dev first, with LiteLLM and OpenRouter fallbacks plus local overrides for aliases or internal models.
- Open the Usage Analytics Demo.
Account Health, Quota, And Automation
- Inspect Codex and xAI accounts locally or on a Manager Server schedule.
- Read quota windows, reset evidence, credential state, workspace state, and provider-specific health signals when available.
- Apply controlled quota cooldowns and route credential failures into an account action queue for review and recovery.
- Open the unified Accounts Demo.
Production Operations
- Run CPAMP Full Mode as one Docker container or a native Linux, macOS, or Windows package for amd64/arm64; the full stack can run alongside CPA.
- Keep request history, Manager configuration, automation state, and model prices in local files with no account registration or telemetry SDK.
- Back up SQLite files together with data.key to preserve encrypted CPA Management Keys.
Want to preview the interface first? Open the Live Demo. The demo uses fictional data only. It is not a deployment or runtime mode and cannot connect to, manage, or monitor a real CPA instance.
CPAMP manages and observes traffic through CPA / CLIProxyAPI. It is not a replacement proxy and does not forward model traffic by itself.
Data, Privacy, And Security
- CPAMP does not phone home, include analytics SDKs, or require account registration.
- External calls are limited to the CPA gateway and integrations you explicitly configure or trigger, such as OAuth, provider checks, plugin releases, and model price sync.
- Request history, configuration, model prices, inspection history, and automation state stay in local files.
- CPA Management Keys are encrypted before SQLite persistence; backups require the SQLite files and data.key.
- Normal APIs and JSONL exports expose redacted failure summaries, never raw failure bodies or stored raw JSON.
- CPAMP is intended for traffic and credentials you are authorized to operate.
README
CPA Manager Plus
A self-hosted CPA / CLIProxyAPI management panel and AI gateway observability dashboard for requests, usage, cost, quota, failures, and account health.
Operate providers, credentials, OAuth, plugins, and configuration while keeping persistent request history, cost analytics, and account automation in local storage.
Why are requests failing? Inspect failure rates, status codes, affected models/accounts, and redacted evidence in persistent request history.
Where is the cost going? Break down tokens and estimated cost by model, provider, account, API key, project, channel, and time range.
Are accounts and quotas healthy? Review credential state, quota windows, reset evidence, and controlled automation for Codex and xAI accounts.
Screenshots
<strong>Dashboard</strong>
<img src="img/dashboard.png" alt="CPA CLIProxyAPI management and observability dashboard" width="420" />
<strong>Request Monitoring</strong>
<img src="img/monitoring.png" alt="CPA request monitoring and failure diagnosis dashboard" width="420" />
<strong>Usage Analytics</strong>
<img src="img/usage-analytics.png" alt="CPA usage and cost analytics by model and account" width="420" />
<strong>Credential List</strong>
<img src="img/credential-table.png" alt="CPA credential list with availability, usage, quota, and actions" width="420" />
<strong>Credential Cards</strong>
<img src="img/credential-card.png" alt="CPA credential cards with health, usage, quota, and actions" width="420" />
<strong>Credential Detail</strong>
<img src="img/credential-detail.png" alt="CPA credential detail with availability, quota, status, and request activity" width="420" />
<strong>Credential Health Inspection</strong>
<img src="img/credential-health.png" alt="CPA credential health inspection status, history, and results" width="420" />
<strong>Credential Quota</strong>
<img src="img/credential-quota.png" alt="CPA credential quota windows, usage, forecasts, and reset evidence" width="420" />
Which Panel Should You Choose?
CPA / CLIProxyAPI can serve either the official Management Center or the CPAMP Lightweight Panel directly on :8317. The lightweight panel replaces the official UI without adding another service. Deploy CPAMP Full Mode when you also need persistent observability and long-running operations.
Manage CPA provider configurations, including Gemini, Codex, Claude, Vertex, xAI, Devin, Muse / Meta, and OpenAI-compatible providers.
Maintain auth files, OAuth logins, API keys, model aliases, priorities, plugins, logs, and system settings. Muse / Meta supports Device Flow credentials separately from meta-api-key inference providers.
Import official Sub2API OpenAI OAuth exports and split multiple accounts into separate CPA Codex auth files.
Request Monitoring And Failure Diagnosis
Persist requests from the CPA usage queue in local SQLite and search account, client API key, and realtime request views.
Inspect status, latency, token, cache, trace, and redacted failure evidence without exposing raw failure bodies.
Run CPAMP Full Mode as one Docker container or a native Linux, macOS, or Windows package for amd64/arm64; the full stack can run alongside CPA.
Keep request history, Manager configuration, automation state, and model prices in local files with no account registration or telemetry SDK.
Back up SQLite files together with data.key to preserve encrypted CPA Management Keys.
If you harden the runtime with a read-only root filesystem or a non-root user, give SQLite a writable temporary directory and a writable database file; see Read-Only Root Filesystem.
Want to preview the interface first? Open the Live Demo. The demo uses fictional data only. It is not a deployment or runtime mode and cannot connect to, manage, or monitor a real CPA instance.
CPAMP manages and observes traffic through CPA / CLIProxyAPI. It is not a replacement proxy and does not forward model traffic by itself.
Open http://:18317/management.html, retrieve the CPAMP Admin Key from the Manager Server log, then enter the CPA URL and CPA Management Key during setup.
CPAMP does not phone home, include analytics SDKs, or require account registration.
External calls are limited to the CPA gateway and integrations you explicitly configure or trigger, such as OAuth, provider checks, plugin releases, and model price sync.
Request history, configuration, model prices, inspection history, and automation state stay in local files.
CPA Management Keys are encrypted before SQLite persistence; backups require the SQLite files and data.key.
Normal APIs and JSONL exports expose redacted failure summaries, never raw failure bodies or stored raw JSON.
CPAMP is intended for traffic and credentials you are authorized to operate.
Development
npm install
npm run dev
npm run type-check
npm run lint
npm run test
npm run build
npm run docs:build
Manager Server:
cd apps/manager-server
go test ./...
go test -race ./...
go vet ./...
go run ./cmd/cpa-manager-plus
Build the Docker stack locally:
docker compose -f docker-compose.manager.yml up --build
Release
npm run build creates a single-file apps/web/dist/index.html.
bin/release/package-native.sh embeds the panel into native packages.
Create release notes through release/ -> dev -> main, then push a
strict vX.Y.Z or prerelease tag from the verified main promotion merge.
npm run release:validate -- --tag --content-only checks the three
required release files before a tag is created.
.github/workflows/release.yml offers a workflow_dispatch dry-run from
main; it validates and builds without publishing a GitHub Release,
container image, or Telegram message.
Release assets include management.html, native packages, and Docker images for linux/amd64 and linux/arm64.
Release publishing is serialized and has no automatic commit-log fallback;
missing or mismatched notes fail closed. See docs/release.md
for recovery and required repository protections.
