Get Started
Start here for the shortest working setup: bring up the CPA gateway runtime, bring up CPAMP, then confirm that request monitoring can receive data. If CPA is already running, jump to Deploy CPAMP Only.
Recommended Deployment
For a first deployment, use Docker Compose. It creates persistent volumes for both CPA and CPAMP:
services:
cli-proxy-api:
image: eceasy/cli-proxy-api:latest
restart: unless-stopped
ports:
- "8317:8317"
volumes:
- cpa-data:/app/data
cpa-manager-plus:
image: seakee/cpa-manager-plus:latest
restart: unless-stopped
ports:
- "18317:18317"
volumes:
- cpa-manager-plus-data:/data
volumes:
cpa-data:
cpa-manager-plus-data:Start the services:
docker compose up -dOpen the management panel:
http://<host>:18317/management.htmlThe first login requires the CPAMP Admin Key. If you did not set one explicitly, Manager Server prints it once in the startup logs:
docker compose logs cpa-manager-plusFirst Configuration
In setup, enter these values in order:
- CPAMP Admin Key.
- CPA URL, for example
http://cli-proxy-api:8317. - CPA Management Key.
- Request monitoring mode. For a new deployment, keep the default
automode.
Recommended CPA version: v7.1.39+. The HTTP usage queue needs v6.10.8+.
What Should Work After Setup
- Dashboard opens and shows Manager Server / CPA connection state.
- Monitoring shows realtime rows after real requests pass through CPA.
- Usage Analytics breaks down cost and tokens by model, account, project, and time range.
- Codex Inspection shows quota, reset time, credential state, and account health.
If the panel opens but monitoring stays empty, start with Request Monitoring Troubleshooting. The usual causes are usage publishing, CPA URL, queue retention, or collector path.
Next Steps
- To choose the right mode, read Runtime Model.
- To configure providers or clients, read Gateway Configuration.
- To learn each panel page, start with Dashboard.
- To use native packages, read Native Packages.
- To migrate from the old project, read Migrate From CPA-Manager.