AI/TLDR

K2 Horizon 32B

The largest dense model in IFM's fully open K2 Horizon fleet, released September 2026 — 32B parameters and a 512K context, sized for a local workstation.

K2 HorizonOpen weightsGenerally available — the published checkpoint is the stage-1 model; IFM says stage-2 results will follow.
Released
3 Sep 2026
Context
512K
Parameters
32B
License
Apache-2.0

Overview

K2 Horizon 32B is the largest dense model in K2 Horizon, the six-model fleet the Institute of Foundation Models released on 3 September 2026 alongside the 0.9B, 3.7B, 7B, 36B-A4B and 375B-A23B sizes. It is a 32-billion-parameter decoder-only model with a native 524,288-token context window carried from the midtraining stages onward, and IFM places it — together with the sparse 36B-A4B — in the fleet's local-deployment sweet spot: strong enough for demanding reasoning, coding and agentic work, small enough for a workstation.

One caveat is stated plainly on the model card: the checkpoint published as IFM/K2-Horizon-32B is K2-Horizon-32B-Stage1, the first stage of the final model's training. IFM says the final checkpoint and stage-2 results will follow, so every number below describes the stage-1 model rather than the finished one.

On IFM's published stage-1 table the model scores 82.3 on GPQA Diamond, 65.3 on AA-LCR long-context reasoning, 36.6 on Terminal-Bench 2.1, 30.2 on SciCode, 22.8 on Humanity's Last Exam without tools and 22.5 on tau3-Banking. IFM compares it against three dense open-weight peers of similar size — Qwen3.8-27B, Muse Glimmer-30B and IBM Granite 4.2 30B — where it leads Granite 4.2 30B on seven of the nine benchmark rows and trails Qwen3.8-27B on all but one. IFM's own framing on the launch post is that the 32B ranks among the top dense models below 40 billion parameters.

IFM pairs the dense 32B with the sparse 36B-A4B deliberately: the two were trained under the same conditions on the same data so that dense and sparse architectures can be compared directly, and IFM reports that the sparse model comes close to the dense one while activating roughly 4 billion parameters per token instead of 32 billion.

The weights are Apache-2.0, and IFM publishes the training lifecycle around them — training data or detailed construction recipes, training code, model configurations, intermediate checkpoints, fine-grained logs and evaluation results. Serving recipes are published for vLLM and SGLang, the latter validated on 2× H200, both using the `k2_horizon` reasoning and tool-call parsers with `reasoning_effort="high"`, `temperature=1.0` and `top_p=0.95`. IFM is a research institute the Mohamed bin Zayed University of Artificial Intelligence launched in May 2025.

Released2026-09-03
LicenseApache-2.0
WeightsOpen weights
Parameters32B
Context512K
ArchitectureDense decoder-only transformer — every parameter runs for every token, with no expert routing. It shares core architecture, vocabulary, training methodology, interfaces, evaluation infrastructure and deployment tooling with the rest of the six-model Horizon fleet, and was trained on the same token budget as the 3.7B, 7B and 36B-A4B models.
ModalitiesText
StatusGenerally available — the published checkpoint is the stage-1 model; IFM says stage-2 results will follow.

Benchmarks

IFM's published comparison against dense open-weight models, transcribed from the model card. Scores are percentages and describe the stage-1 checkpoint; baseline figures come from Artificial Analysis, with Muse Glimmer-30B at high reasoning effort.

BenchmarkK2-Horizon-32B-Stage1Qwen3.8-27BMuse Glimmer-30BIBM Granite 4.2 30B
Total parameters32B27B30B30B
ArchitectureDenseDenseDenseDense
tau3-Banking (agentic tool use)22.5%48%23.5%14.4%
Terminal-Bench 2.1 (agentic terminal use)36.6%79.8%51.7%26.6%
SciCode (scientific coding)30.2%44.7%43.6%36.6%
Humanity's Last Exam (without tools)22.8%33.9%22%11.2%
GPQA Diamond (graduate-level science QA)82.3%90.5%83.5%64.4%
CritPt (frontier physics reasoning)1.4%5.4%2.6%0.3%
AA-LCR (long-context reasoning)65.3%77.3%80%46.7%
AA-Omniscience Accuracy16.8%15.6%27%10.1%
AA-Omniscience Non-Hallucination58.3%69.7%18.1%74.4%

Comparison source ↗

This model's scores

  1. GPQA Diamond (graduate-level science QA)82.3%
  2. AA-LCR (long-context reasoning)65.3%
  3. AA-Omniscience Non-Hallucination58.3%
  4. Terminal-Bench 2.1 (agentic terminal use)36.6%
  5. SciCode (scientific coding)30.2%
  6. Humanity's Last Exam (without tools)22.8%
  7. tau3-Banking (agentic tool use)22.5%
  8. AA-Omniscience Accuracy (factual accuracy)16.8%
  9. CritPt (frontier physics reasoning)1.4%

Scores on a 0–100 scale (25-point gridlines); higher is better. Each benchmark links to its published source.

Strengths

  • 32B dense weights under Apache-2.0, sized for a single workstation or a 2-GPU server
  • 512K-token native context window
  • 82.3 on GPQA Diamond and 65.3 on AA-LCR long-context reasoning
  • Published with training data recipes, training code, intermediate checkpoints and fine-grained logs
  • A controlled dense counterpart to the sparse 36B-A4B, trained on the same data under the same conditions
  • Shares vocabulary, interfaces and deployment tooling with the other five Horizon sizes

Best for

  • Reach for it when you want a dense open-weight model you can fine-tune and self-host without expert-routing complexity
  • Reach for it for local-workstation reasoning, coding and agentic work
  • Reach for it for long-document and repo-scale tasks that need the 512K-token window
  • Reach for it for dense-versus-sparse research against the matched 36B-A4B
  • Wait for the final checkpoint if you need settled numbers — the published weights are a stage-1 model

How to access

ProviderModel ID
Self-hosted (vLLM) ↗IFM/K2-Horizon-32B
Self-hosted (SGLang) ↗IFM/K2-Horizon-32B

K2 Horizon — every version

The full lineage of the K2 Horizon line, newest first. Every version has its own page — click any to compare specs, benchmarks and pricing.

VersionReleasedContextLicense
K2 Horizon 375B-A23Bcurrent2026-09-03512KApache-2.0
K2 Horizon MoVA 36B-A4B2026-09-03512KApache-2.0
K2 Horizon 32B2026-09-03512KApache-2.0
K2 Horizon 7B2026-09-03512KApache-2.0

FAQ

What is K2 Horizon 32B?

It is the largest dense model in K2 Horizon, the six-model fleet the Institute of Foundation Models released on 3 September 2026. It has 32 billion parameters, a native 524,288-token context window and Apache-2.0 weights, and IFM aims it at local workstations and efficient serving.

Is the published checkpoint the final model?

No. The model card names the released checkpoint K2-Horizon-32B-Stage1 and states that the final checkpoint is still to come, with stage-2 results following. Every benchmark IFM reports for the 32B describes this stage-1 checkpoint.

How does K2 Horizon 32B compare with other dense models its size?

IFM's table sets it against Qwen3.8-27B, Muse Glimmer-30B and IBM Granite 4.2 30B. The stage-1 checkpoint leads Granite 4.2 30B on most rows — 82.3 versus 64.4 on GPQA Diamond, 36.6 versus 26.6 on Terminal-Bench 2.1 — sits below Muse Glimmer-30B on the coding and long-context rows, and trails Qwen3.8-27B everywhere except AA-Omniscience Accuracy (16.8 versus 15.6).

Should I use the dense 32B or the sparse 36B-A4B?

IFM trained both under the same conditions so they can be compared. The 36B-A4B activates roughly 4 billion parameters per token instead of 32 billion, so it is far cheaper to serve, and IFM reports it comes close to the dense model overall — on the published tables it is ahead of the stage-1 32B on Terminal-Bench 2.1, SciCode, tau3-Banking and Humanity's Last Exam, and behind on GPQA Diamond. The dense 32B is the simpler thing to fine-tune and deploy.

How do I run K2 Horizon 32B?

The Apache-2.0 weights are on Hugging Face. IFM publishes a vLLM recipe and an SGLang recipe validated on 2× H200, both BF16 with tensor parallelism of 2 and the k2_horizon reasoning and tool-call parsers. IFM asks for reasoning_effort="high", temperature=1.0 and top_p=0.95, the settings behind its reported results.

What else is in the K2 Horizon fleet?

Six sizes share the same architecture, vocabulary and training methodology: 0.9B for constrained devices such as watches and glasses, 3.7B and 7B for phones and on-device apps, this dense 32B and the sparse 36B-A4B for local workstations, and a 375B-A23B for enterprise deployments.