Kolibri gives teams another open-weight AI option. Here’s what it takes to run it.

Another choice for teams

Aleph Alpha has released Kolibri 1, a model designed for German- and English-language tasks, including document analysis, question answering and tool use. Its weights are available on Hugging Face under Apache 2.0 terms. A team with the right infrastructure can download the model and run it on systems it controls rather than relying only on a hosted model service.

That choice matters for organizations working with internal documents or building German-language tools. They can test Kolibri on their own questions, decide where the model runs and adapt the released weights to a specific workflow. Those are practical options created by the release itself. Whether Kolibri is the best choice for a particular workload will take testing beyond the launch materials.

Small active count, substantial hardware

Kolibri uses a mixture-of-experts design. It has about 78 billion parameters in total, but uses roughly 3.46 billion for each token it processes. Think of it as calling on a small group of specialists for each step rather than asking every specialist to work every time. That can reduce computation per token. The other specialists do not disappear from memory: the full model still has to be stored while it runs.

That is the first practical limit to understand. The model card lists a memory footprint of about 78 GB for its FP8 weights. Its official minimum hardware examples include two 80 GB A100 GPUs, two H100 SXM5 GPUs, or one H200, B200 or B300. Memory for the weights is only part of a deployment; serving longer documents or multiple users adds further demands. This is an option for teams able to provision serious GPU capacity, not a promise that the full release will run well on an ordinary laptop.

A context ceiling with a qualification

The company also says Kolibri can support up to 1,048,576 tokens of context. That is a potentially useful ceiling for long documents, but it needs a qualifier: Kolibri’s final long-context training went to 262,144 tokens, and Aleph Alpha recommends staying at or below that length for serving efficiency and complex tasks. The million-token figure is the company’s validation claim, not a guarantee that every question over a very long input will be answered reliably.

What is open, and what is not

The word “open” has a boundary here too. Kolibri’s model card says its Apache 2.0 license covers the weights and configuration files in the repository. Aleph Alpha has also released a separate Apache-licensed inference plugin and a detailed technical report. But the model card explicitly excludes other artifacts, including underlying code and training methods, from the model-repository license. It provides a summary of training-data sources, not the complete training corpus. “Open-weight” is the precise description; a downloadable model is not automatically a fully reproducible open-source AI system. Bright’s open-model guide explains that distinction in more detail.

The questions that make the release useful

Aleph Alpha reports strong results in its own benchmark comparisons and positions Kolibri as a “sovereign” model for organizations that want more control over deployment. Those are the company’s claims, not independently reproduced performance or a blanket legal-compliance guarantee. The model card itself calls for people to review outputs before consequential actions.

The useful news is concrete: there is now another English-German checkpoint that qualified teams can download, inspect and test on their own workloads. The next questions are equally concrete. Does it answer their documents accurately, at an acceptable speed and cost, on hardware they can actually use? The release makes those questions testable. It does not answer them for every team.