Should we migrate all traffic at once?

No. Start with a low-risk internal or batch workload, compare outputs and logs, then move higher-risk chat or agent traffic after the fallback paths are tested.

Migrate from Merge Gateway to Concentrate

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

Keep one API

Reach current models across providers through one endpoint.

Add management

Get spend, request logs, API keys, and fallbacks.

Migration basics

Frequently asked questions

When should a team move from Merge Gateway to Concentrate?

Move when model access is no longer the only need. Teams usually switch when they want spend by team or key, request logs, provider fallbacks, API keys, redaction, and audit logs in one managed request path.

What changes in code during the migration?

LLM Gateway

Teams

Integrations

Platform

Legal