Migration
Migrate from Portkey to Concentrate
Keep gateway features like routing and fallbacks, and access all models through Concentrate with spend views, request logs, redaction, and team controls in one managed request path.
Code change
Base URL + key
Keep your SDK, prompts, and parsing in place.
Rollout
By workload
Move low-risk traffic first, then the rest.
Testing
Compare first
Check output, latency, tokens, and fallback paths before cutover.
New capabilities
What your team gains with Concentrate
01
Keep routing
Choose model routes, provider paths, and fallbacks.
02
Add management
Get spend by team and key, request logs, and API keys.
03
Keep review ready
Use redaction, SSO, RBAC, and audit logs.
Migration basics
Frequently asked questions
When should a team move from Portkey to Concentrate?
Move when you want model access, routing, spend views, request logs, API keys, redaction, and audit logs from one managed request path instead of stitching them together.
Do we lose routing control in the move?
No. You can still choose model routes, provider paths, fallbacks, API keys, spend limits, and security settings. See the migration guide for the mapping.
How should we test the migration?
Replay known requests through both gateways and compare outputs, latency, token counts, errors, and fallback behavior. Move traffic by workload instead of flipping every app in one deploy.