Model catalogue · Mistral AI
Codestral
Vendor version: codestral-2508 (as of 29 August 2026)
The code tier from the European vendor Mistral AI for programming and automation work. For work on client, patient or personnel files it is not a tool; it is in the catalogue because firms build their own reports, macros and interfaces, and real data can end up in examples and error messages while doing so. That is exactly what is clarified here: via Google Vertex AI the contractual chain is closed, because the confidentiality agreement under section 203 of the German Criminal Code signed there is service-bound and expressly applies to third-party models on this platform as well. A US group remains in the chain as platform operator; production data does not belong in development inputs in any case.
Everything section 203 requires is settled, including the provider's confidentiality undertaking. You do not have to clarify anything further.
What it is good for
- Code and automation work inside the same platform and contractual chain - no further service provider for development data
- Processing committed to the EU and to the Netherlands, European model vendor
- Covered by the platform operator's service-bound section 203 agreement
Where it stops
- None of the seven task classes in this catalogue - the entry documents the coverage position for development work, it is not a recommendation for client matters
- The platform operator is a US group - CLOUD Act exposure remains despite the European model vendor
- Production data does not belong in development prompts - use synthetic material for examples
- The reach of the logging exception for third-party models cannot be evidenced from publicly available documents (as of 2026-08-17)
- The platform's global endpoint gives no residency guarantee - the same models can be called there as well. Binding to the EU is therefore a configuration requirement: the global endpoint is blocked by organisational policy, otherwise the EU commitment is a settings question rather than a property.
Routes examined
The same model, procured differently, is a different legal position. What is examined per route is the contract chain, not the model.
| Route | Section 203 status | Version on this route |
|---|---|---|
| Google EU platform (Gemini Enterprise, formerly Vertex AI) | covered | - |
The conditions behind a conditional status - which piece is open on which route and who closes it - are set out in the full matrix in the German catalogue, and we go through them in the conversation. The German page for Codestral carries the sources with their retrieval dates.
Is Codestral the right fit?
We go through your tasks and the route that carries them - and say plainly where it does not.
Arrange a conversation