Field noteOct 23, 20261 min read1 source

Designing Kolibri: Architecture Trade-Offs from First Principles

In one minute

Aleph Alpha published a technical note on the architecture choices behind Kolibri, alongside an interactive explorer for comparing model configurations.

What changed: Rather than announcing Kolibri or detailing its release, the post analyzes architecture trade-offs in training and deployment costs and offers a tool to compare model configurations.

The post is dated 7 October 2026 and is authored by Pit Neitemeier and Alessio Serra.

The explorer lists Kolibri at 78.1B total parameters and 3.5B active parameters per token, or 4.4% active. At a 16K context it lists 28.3G FLOPs per token and 189M sequence-mixer state elements. Its displayed configuration includes 50 decoder layers, 384 routed experts, six routed experts active per token, four KV heads, and 40 sliding-window-attention layers with a window of 512.

For Kolibri Origin, the post lists 30.6B total and 3.3B active parameters. At one million tokens, it estimates 10.8B sequence-mixer state elements per Kolibri sequence, versus 53.7B for Origin. The article says Kolibri was recently released under Apache 2.0 and derives parameter, FLOP, and state calculations for MoE decoders.

The source does not establish model-quality gains, benchmark superiority, actual serving prices, or deployment performance for a particular hardware setup.

Evidence / sources

  1. 1aleph-alpha.com/en/blog/designing-kolibri-architecture-trade-offs-from-first-principles
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicModelsExplore the models topic hub.
  2. 02topicInferenceExplore the inference topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract