Model migration and routing review

What it is for

Changing models is now routine: a cheaper model for one task, an open-weight model on your own hardware for another, a router in front of several. Each change can alter security behaviour, data handling and your legal position. AG11 checks before you switch.

What we look at

• Evaluation parity: your security and quality scenarios run against the old and the new model, so the change is measured, not assumed.
• Data: for each provider, where prompts and outputs are processed and stored, how long they are kept, and what abuse monitoring retains. Providers differ, and their terms change.
• Licences: open-weight licences range from Apache 2.0 to provider-specific licences; for example, Mistral publishes some models under Apache 2.0 and its largest under its own open-weight licence,^⁠[1] and AI21 publishes Jamba weights under the Jamba Open Model License.^⁠[2] Some licences carry attribution or usage conditions that apply when you deploy.
• Failover: what your system does when a provider is down, slow or changes a model under you.

Every provider we work with is listed, in plain text, on the platforms page.

What you receive

Parity results, a residency and retention matrix, a licence and attribution check, and a failover plan.