AI Model Portfolio Update
To keep the PHOENIQS AI Model Service current and to provide customers with access to the latest model capabilities, we are updating the model portfolio as part of our regular lifecycle management process.
Over the next 20 business days, selected models will be retired from service, with newer recommended alternatives identified to provide stronger capability coverage, improved performance, and better long-term support. This update is intended to ensure that customers continue to benefit from a service that remains aligned with the rapidly evolving model landscape.
As part of this refresh, we are pleased to introduce Kimi K2.6 and Gemma 4.1. Additional models are also planned for release on a rolling basis, including:
Qwen 3.5 35B-A3B
GLM-5
Quest Coder V1 7B Instruct
Voxtral 4B TTS
FLUX.2 [klein] 4B
Qwen-Image-2512
Qwen-Image-Edit-2511
Recommended replacement models have been identified to support a smooth transition based on workload type and capability profile. Because behavior may vary across models, customers should validate prompts, tool behavior, output formats, latency, and response quality before migration.
This portfolio update reflects our continued investment in keeping the service up to date and expanding customer access to new model capabilities as they become available.
If short-term continued access to a retiring model is required for transition planning, customers may submit a service desk ticket outlining the use case, expected business impact, and requested timeframe. Requests will be reviewed in accordance with the standard decommissioning process; however, continued availability cannot be guaranteed. Further model additions will be communicated as they are released into service.
Recommended replacements
What this means for you
If you are currently using any of the affected models, please plan to migrate applications, prompts, and API calls to the recommended alternatives within the next 20 business days, based on the Basel, Switzerland business calendar.
Because output characteristics and tool behavior may vary by model, we recommend validating prompt compatibility, structured outputs, latency, and overall response quality before cutover.
Recommended next steps
- Identify applications and workflows currently using the affected models.
- Update model references to the recommended replacement models.
- Test prompt compatibility, latency, output quality, and downstream integrations.
- Complete migration before the communicated decommissioning date.
Support
Please contact your account team or support representative if you would like assistance selecting or validating the most appropriate replacement for a specific workload.