Will it last?
This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Common problems & fixes
Common pitfalls, not an exhaustive catalogue:
- Garbled or over-verbose Instruct output: the chat template is most likely not applied. Use
apply_chat_templateand do not prompt a base checkpoint as a chat model. - Truncated or silently dropped context: the window is only 4k, so long inputs overflow. Chunk or retrieve, and budget the 4k across system prompt, input and output.
- Weak output in a specific language: per-language quality is uneven across the 35 languages. Evaluate the target language and consider a light fine-tune for lower-resource ones.
- Non-reproducible results or silent updates: a deployment floating on
mainchanges under you. Pin an exact HF revision (e.g. a dated-2512snapshot) and verify checksums.
Versions, changelog & cadence
Releases follow a generational cadence of 1.7B → 9B → 22B, with dated snapshot revisions (e.g.
EuroLLM-9B-Instruct-2512) published on the utter-project org, each with base and Instruct
checkpoints. Versions are tracked as immutable Hugging Face revisions, so the revision hash is
the changelog anchor: pin it and diff against a newer revision when upgrading. The EuroLLM-9B
technical report accompanies the release and documents what changed.
Community & support channels
Announcements and docs come from the EuroLLM project site (eurollm.io, ev-eurollm-site).
Usage questions go to the model discussion tabs on the utter-project Hugging Face org
(ev-hf-9b-instruct). There is no paid support tier; support is community and consortium based,
around an EU-funded open project.
Tracked known issues
These come from technical-report caveats and third-party reviews, not a formal issue tracker, so coverage is partial.
- The context window is only 4k, a real constraint for document workloads.
- Per-language quality is uneven; lower-resource EU languages trail the majors.
- Raw reasoning is in-class, not frontier.
- Base checkpoints are untuned research artifacts and must not be deployed as assistants.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
TransparencyDo you know what it is: weights, training, behaviour, and legible terms?
ModerateOpen-weights-plus-recipe with only partial data openness. The technical report documents the tokenizer, architecture, data mixture and training procedure, and the released SFT dataset (EuroBlocks-SFT-2512) and the EuroFilter artifact make the recipe inspectable. For the tracked 9B and 1.7B line the ~4T-token pre-training corpus is described, not published as one dataset. Transparency is stronger than for weights-only releases and weaker than for a fully-open model (cf. OLMo), and the model cannot be reproduced from a released corpus. The later 2512 generation released a web pre-training corpus and its training and evaluation code; it is a separate entity and is not scored here.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.