Migration
Migrate from Helicone to Concentrate
Keep the request logging and monitoring you rely on, and add model access across providers, API keys, spend limits, fallbacks, and redaction in the same request path.
Code change
Base URL + key
Keep your SDK, prompts, and parsing in place.
Rollout
By workload
Compare logs and latency, then move traffic gradually.
Testing
Compare first
Check output, tokens, and error paths before cutover.
New capabilities
What your team gains with Concentrate
01
Keep observability
See model, cost, tokens, and latency on every request.
02
Add model access
Reach current models across providers through one API and key.
03
Add controls
Get API keys, spend limits, fallbacks, redaction, and audit logs.
Migration basics
Frequently asked questions
When should a team move from Helicone to Concentrate?
Move when you need more than observability. If you also want model access across providers, API keys, spend limits, fallbacks, redaction, and team controls in the same request path, Concentrate covers logging and the gateway together.
What changes in code during the migration?
Most teams change the base URL, API key, and model route, then check response shape, latency, token counts, and error behavior. App logic and prompts usually stay in place.
What happens to our existing logs?
Existing history stays in Helicone. New traffic through Concentrate is logged with model, cost, tokens, and latency from the cutover point. See the migration guide for the full detail.