Model lifecycle policy

Each model on the Mistral Serverless API moves through a defined lifecycle, from initial release to retirement. Use these stages to choose the right model for production and plan migrations before a model is retired.

Labs models are experimental releases intended to collect feedback before we commit to a production model. They:

• Are identified by a labs- prefix, for example labs-mistral-model-x-y.
• Are free of charge.
• Allow silent updates at any time.
• Don't support data collection opt-out.
• Aren't recommended for production use.

Public Preview is the stage for general public launches that aren't final yet. These models are actively promoted, but may receive updates before reaching General Availability. They:

• Are priced at the same rate as General Availability models.
• Allow silent updates.
• Have no guaranteed path to General Availability, and may be retired before reaching it.

General Availability models are production-ready and stable. They:

• Receive no silent updates.
• Are the only models eligible for aliases -latest and -major. See model naming convention.
• Are supported until retirement.

Model identifiers use a model-name-major-minor format, for example mistral-medium-3-5.

General Availability models support three aliases:

Labs models are always prefixed with labs-. Public Preview models use the major-minor format but aren't eligible for a -latest or -major alias.

Deprecation is announced as soon as a replacement model is available. The replacement can be in General Availability or Public Preview.

During the deprecation period, the model remains accessible. Once retired, requests to its identifiers fail with a 404 error.